#Charmon
calm elk
Hi there
Sounds like an issue with your stripe-connect-webhooks endpoint on your local server
Have you added logs to ensure that endpoint is being hit?
crude delta
I don't think its being hit, I am receiving these errors:
API resolved without sending a response for /api/stripe-connect-webhooks, this may result in stalled requests.
why is it not being hit though?
if regular endpoint is being hit, but not stripe-connect-webhooks
crude delta
Yes, it's pretty much identical to my regular webhooks code:
calm elk
Where is your endpoint route defined?
I'm not super familiar with Next.js
But do you have a route set up for stripe-connect-webhooks?
Or is the route just based on the file?
crude delta
yes its based on the file
calm elk
Hmm do you have an Event ID that I can look at that you sent to this endpoint?
crude delta
yes - evt_3Mo5yvCFCmloVZkH1fYUrMxA
calm elk
Hmm that looks fine but yeah I actually can't see too much since you are forwarding via the CLI
If you try and do a simple POST request to your route do you see it?
Like I'd make sure that the route is accessible beyond the webhook
It does seem to be some issues with the route config afaict
dusk voidBOT
crude delta
is there any other configuration that I have to do to listen to connect webhooks instead of regular or is it just this command according to the docs:
For Connect webhooks, use --forward-connect-to with stripe listen and --stripe-account with stripe trigger.
Yeah if you are forwarding to local endpoint then that is all you should need.
Can you try specifying http://localhost:3000/api/stripe-connect-webhooks
Looks like you left off the http previously
Don't think that should matter but want to make sure
crude delta
Don't think that should matter but want to make sure
sorry, I was using regular webhook secret for stripe-connect-endpoint, I had to update the env variables
if someone happen to face something similar, this could be just simply forgetting to update env variables