#tonidigital_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ 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/1304455548166475856
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- tonidigital_webhooks, 3 hours ago, 8 messages
hi! there's unfortuantely very little we can say here since we don't see much of anything on our end.
I'd start by making sure you/your hosting provider don't block our IPs, at least. https://docs.stripe.com/ips#webhook-notifications
Ok, I need to check that with our infrastructure guy. Anything else that I can check?
the other thing would be to ask your hosting provider if they have other reports of issues with Stripe webhooks, or packet loss.
you can also check things like maybe your hosting provider detaches network access/spins down a server after inactivity and it has to wake up
if you think it's packet loss/network issues our support team can give you an MTR from our servers that your provider might be able to use
but it might be as simple as you have some default firewall setting to "block bots" that blocks a range of Amazon AWS IPs that includes the ones we send webhooks from.