#mattb

1 messages · Page 1 of 1 (latest)

grave otterBOT
cold fox
#

Interesting, have you checked your network or server logs to see how far the unable to connect event gets?

#

Have not experienced this myself unfortunately

keen veldt
#

Hi Pompey - Thanks for helping out here - It actually doesn't reach deep enough to trigger a log at all. It's like the request isn't even attempted.

#

Any chance I can give you an event id or something? Our severs are not seeing these hooks at all.

cold fox
#

I can look, though we may not have much more info ourselves

#

Have you reached out to your hosting provider? Sometimes there is a block in their network config or in AWS or something and they can typically help with that

keen veldt
#

Also chatting to our provider - Just want to see how far the request is making it on Stripe's side. Event ID: evt_3O5U95K4LUEiuQoK0FF2cFZI

cold fox
#

I'm seeing a timeout but not much more info. Seeing if there is more I can look at with this

#

For context, do you know around when this started? And is it just this endpoint that is having issues?

keen veldt
#

We noticed this about an hour ago, yes it's only this webhook failing (we use the same endpoint for multiple hooks). Retrying a few times in the interface eventually gets it to succeed.

cold fox
#

Gotcha, seeing what I can find in our logs

keen veldt
#

Thank you so much!!

cold fox
#

Unfortunately not seeing much, it looks like we got two 502 responses from that server a bit ago and have not heard back since. It looks like we are still sending out these events the same way as best as I can tell
https://dashboard.stripe.com/events/evt_3O5Y1AK4LUEiuQoK0w8TyuCc
https://dashboard.stripe.com/events/evt_3O5Y0VK4LUEiuQoK02KmKVV0

#

I can try to send a test ping event to that URL if you want. It would have an empty request body and I believe it would have an event type that your code would likely error out on.

keen veldt
#

That would help a lot please

cold fox
#

I got a 500 response from the server with a generic something went wrong message. I think your hosting provider may be the one best suited to look in to this at the moment

grave otterBOT