#camsav_webhooks
spiral glacierBOT
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.
- camsav_webhooks, 3 days ago, 3 messages
dull bobcatBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1242155413831422054
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
formal spear
Currently looking over the failed request vs successful request and it seems when we have null for request.id and request.idemptotency_key as null it works which also doesn't make sense here
plain mulch
Hi 👋
it looks like your server is blocking these requests
You are returning a 403 status code with the following content:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: hxOi0ZIdTtd2oHvANdnbJgUGYaOLgi_Koyn22S48PKgmi0fKeZvN7A==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
Correct but I have done everything on the serverside I can to stop them from being blocked. Ive added all possible IP addresses from stripe. Make no sense why it would let the rest of the webhooks to make it through but not that one
additionally it seems some times they do make it through for some reason but most of the time they dont
plain mulch
Unfortunately I cannot look into this further since the logic that is causing these to be returned is not something on Stripe's end. We send the same POST requests to millions of webhook endpoints.
Given that some of these events to the same webhook are processed successfully, it strongly suggests something it your webhook handling code is rejecting these requests
formal spear
Okay I will take a look at it