#si-webhook
urban pythonBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- sighv4, 1 hour ago, 10 messages
finite edge
Question isn't related! Just a coincidence I'm on here twice 🙂
This is the account: acct_1OSIZ4Q2S6lPR2P2
oh wait, I'm seeing pending webhook failures now, they just weren't red
celest cargo
Hi, it looks like you're seeing these failures now. Is there a question that is still pending an answer?
finite edge
Yeah, I'm not sure what these errors mean:
info: Receiving user account webhook {"service":"api"}
info⚠️ Webhook signature verification failed. No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?
infoLearn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing
infoinfo: Event for stripe account undefined {"service":"api"}
infoinfo: Unhandled Stripe event type function contentType(type) {
info var ct = type.indexOf('/') === -1
info ? mime.lookup(type)
info : type;
info
info return this.set('Content-Type', ct);
Other webhooks seem to deliver fine
celest cargo
That typically means that the webhook signature did not match, you can learn more about it here: https://support.stripe.com/questions/webhooks-what-to-do-when-the-http-status-code-starts-with-a-four-(4xx)-or-five-(5xx). The webhook signature must be the raw value
finite edge
Yeah, what's odd is that it's fine for other requests. and again, this is on the Connected account, but if I go to the parent account I see that webhooks for that event are going through properly:
In fact, it's the same event id
celest cargo
Can you share the event id, starts with evt_ on these above failed event with the signature verification error?
finite edge
Oh on closer inspection they're not the same. the first numbers/letters are the same "evt_1OUYDEQ2S6lPR2P21RWfSXhv" is the failed one
These look like they're done from a testing server (localhost:3000) in the success_url
I also don't actually do anything with that event type checkout.session.expired yet so I might remove it from the webhook
But it's unclear to me why this is being logged in the Connected account and not in the parent account
celest cargo
Let me look at the event
Upon looking at the event, it looks like the webhook signature is miscongifured on your end. There is not much we can do on our end and you would need to investigate this on your code.
urban pythonBOT
si-webhook
finite edge
Again, that seems weird to me cause it passes other webhook events fine :/
Would it be possible that it's attempting to return to a local cli listener that isn't listening anymore?
I'm running the local cli webhook intererception thing and I'll see what happens in 3 minutes when it tries to resend
celest cargo
Yeah, that is possible. I did not realize it was in test mode.
If you nolonger need this, you can just disabled this in test mode
finite edge
oh cool, yeah i see all the failed events in test mode for the parent account (so many places to check 😅 )