#mason-terry_webhook-delivery-issues-cli-forwarding
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/1341533726743724165
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi! How are you 'listening' locally? How are you providing a route from the wider internet to your 'local' listener?
Yes, using the stripe cli. stripe listen --forward-to http://localhost:7075/api/platform --forward-connect-to http://localhost:7075/api/connect
If you just do stripe listen do you see those events in the console?
> Ready! You are using Stripe API Version [2022-11-15]. Your webhook signing secret is whsec_38ceb4019de1037f790bcafff1dcb0774589cd1947bbfecb9b307cbbc9752c17 (^C to quit)``` This is what I see when I run `stripe listen`
Maybe that's not the question you were asking. I see this when I update the subscription in Stripe ```2025-02-18 16:08:59 --> customer.subscription.updated [evt_1QtyyNLxQmIisNhQtUuBsm7k]
2025-02-18 16:09:00 <-- [204] POST http://localhost:7075/api/platform [evt_1QtyyNLxQmIisNhQtUuBsm7k]
Perfect. So Stripe CLI sees it, and forwards it - so why is your app not accepting/handling it?
mason-terry_webhook-delivery-issues-cli-forwarding
That's what I'm not sure about. I remember a while back I started listening to a new webhook/event and I had to go into stripe and say that I was going to "listen" to it. And I thought I was something similar, but maybe I'm wrong. I don't see this option in the Stripe env that I'm in.
That would be for a 'regular webhook' (i.e., not dev/testing). With Stripe-CLI it gets all of them.
I also see that your app responded with a 204, so it's making it into your app somewhere/somehow.
Okay, I guess it's something on my side. I'll try to look more into it. Thanks