#iondevx
dense shale
thick trench
So from above it looks like the delay is because your server is responding with the above error, so Stripe must retry sending the request. Is that correct? Can you share an event id?
wintry yoke
yes that's the case i believe. im sending the event id and payment intent id if it helps
thick trench
Yes both will help so I can take a look
wintry yoke
payment_intent.created "id": "pi_3Mme2iGU21CfxrOF3KW9K1zZ", this is payment intent id
thick trench
Cool thanks
I can get the event from that
So in the response from your server I see: {"message":"Unauthorized"}
So I recommend checking your server logs to debug why your server isn't returning a 200
Or if your logs aren't sufficient, you'll need to improve your logging to get to the root of what's going on
You can expand the webhook attempt from that above link to see how your server is responding
wintry yoke
yeah thats the problem we are returning Unauthorized because we cannot access to this file https://stripe.com/files/ips/ips_webhooks.json
and its weird that i can have access to this file from browser but not from the lambda function
thick trench
Ah yeah that's not meant to be accessed on the fly
It's meant to be downloaded and then the contents copied to wherever you filter ip's
So you get a 429 too many requests likely because you're trying to do this programatically
wintry yoke
hmm i understand, that's right we should download and process it locally. but right now in production we access it every time programatically and i didn't understand why it started to give error now (last 3 hours)
thick trench
429 means too many requests, so could be that ip has hit our server too much?
I'm not really certain. In any case, I can't recommend fetching that list programatically
wintry yoke
probably, if it's possible to put that ip into a whitelist?
thick trench
No unfortunately not