#thomas-k-_webhooks
mild vineBOT
👋 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/1310926039563763733
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
serene cradle
This is related to our last thread from yesterday #dev-help message
lunar hound
I don't know that, you would need to check your logs to understand what is happening on your end.
on Stripe's end, all we see is that we sent you the event, waited 20 seconds, and never received a response, so we timed out.
serene cradle
Our host is up on Heroku, and accessible by other API consumers and it seems to be related to Stripe/Heroku link. We did deploy a temporary proxy for further investigations.
- Without the temporary proxy :
Stripe -> Herokuis failing - With the proxy :
Stripe -> HTTP/1.1 Scaleway -> Herokuis working
Does Webhooks support HTTP/2 ?
lunar hound
maybe you need to whitelist the Stripe IP address? https://docs.stripe.com/ips#webhook-notifications
serene cradle
There is no IP filter on Heroku
The Webhook has worked perfectly during months/years. It fails since 2024-11-21
Heroku has add HTTP/2 support on that day
lunar hound
hum... looking into this
looks like we don't support HTTP/2 for webhooks
so that explains the issue then
serene cradle
Woow
mild vineBOT
serene cradle
HTTP/2 has been released in 2015. Is it planned for Stripe Webhooks ?