#Att89-webhooks

1 messages · Page 1 of 1 (latest)

still sedge
#

Hi 👋 sorry to hear about that. Can you share some additional details about the behavior you're seeing? Are the events not being triggered in Stripe, or can you see the events being created but they aren't hitting your application?

sinful wraith
#

Hi! The events are triggered in Stripe, but they don't hit the application. On my dashboard in developer/webhooks I can also see a lot of failed events.

#

Like if our server would not running, but it does. Also if i am trying to test it locally, there are no events going through

still sedge
#

Gotcha, can you share your account ID or the ID of an event that isn't being delivered successfully?

sinful wraith
#

Our account ID is: acct_1JNcllFHLvSMgLRW

still sedge
#

Thanks, pulling that up on my side.

sinful wraith
#

Thank you

still sedge
#

I'm seeing that we received 404 responses for the events we're trying to send to your server, and when I attempted to emulate a request I got the same response.

sinful wraith
#

Yes, I can see them also, but I don't understand why. The endpoints are correct, the endpoint secrets also and I hadn't change anything on this part of the code.

still sedge
#

I don't think it's your event handling code, it seems like the endpoint itself is down.

sinful wraith
#

The only thing that could be a problem: a few days ago we implemented microsoft's azure service into the server. I am using maven for the external libraries and there were a lot of version problems with some sub-dependencies which are used by microsoft and some other libraries. Finally i could fix it, through excluding specific versions here and there. But actually there were no problems with the stripe library, if i can remember right.

#

Do you think, this could be the problem?

still sedge
#

Maybe, based on what I'm seeing I think the problem is somewhere in your ingress process though. I'm seeing successful TLS handshakes like we're able to communicate with your server, but then your server doesn't recognize the endpoint that we're trying to get to. I'd recommend making sure your ingress routes are still in place, and that there isn't anything blocking access to those routes.