casey_webhooks

[honest turtle]

👋 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/1279144789366804531

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[ebon cradle]

Only thing that's changed since the last time I (successfully) used this setup, is a bump in Stripe API version and corresponding version bump on the Stripe package in my codebase.

But based on that error, it sounds like the call from Stripe is failing to even make a connection to my tunnel, which kinda feels too far upstream to be related to a version upgrade? I dunno. 🤷‍♂️

[lilac raven]

Taking a look at this event, I see 3 successful deliveries but I also see the failure.

Changing the API version should not have any impact on whether or not we can connect with your webhook endpoint. that would be a different error

This appears to be due to the reachability of your URL

[ebon cradle]

Yep, that's what I thought too.

But it is, as far as I can tell, reachable.

You should be able to hit it from Postman or similar app—post anything (or a blank request) here and you'll get an (expected) error about server origin. Which at least confirms a connection is made and we get a response via remote connection: https://twenty-for.share.cubitcreative.dev/webhooks/stripe

Also interesting that you see successful deliveries to that webhook somewhere in workbench? I only see failures under Delivery Attempts.

☝ And side note on that...not sure if this is a workbench bug or what, but when I load up the associated Event, it says No results found. Eg, just copy/pasting the Event URL into a new tab:

[lilac raven]

You should be able to hit it from Postman or similar app
Unfortunately that doesn't prove anything necessarily. If it wasn't reachable when the event payload was sent, that is what matters.

I'm not sure what you are displaying in workbench though. As for how workbench segregates event deliveries, we focus primarily on API integrations here.

[ebon cradle]

Unfortunately that doesn't prove anything necessarily. If it wasn't reachable when the event payload was sent, that is what matters.
Yeah, sure—but I've resent it (and have also triggered "new", subsequent API calls) since testing.

Like I triggered from Hoppscotch, request goes through/returns expected error code, then I replay from the Stripe dashboard and get the Timed out connecting to remote host error.

And also tried another test payment (ie, a new/fresh request) and same thing—Timed out connecting to remote host.

[lilac raven]

Have you tried generating a new event? Not using the dashboard?

[ebon cradle]

What do you mean by "generating a new event"?

You mean like a fresh request via the app itself? If so, yes 👇

And also tried another test payment (ie, a new/fresh request) and same thing—Timed out connecting to remote host.

I'm pretty sure there's just something funky happening with Stripe's request, here...

• Hoppscotch (remote API dev tool) can post to the URL as expected
• My command line for Expose (again, that's my Ngrok alternative for tunneling) doesn't show the request ever coming through from Stripe...but does show Hoppscotch request and other get requests from browser.

[lilac raven]

Unfortunately I don't think anything changed here. In fact, for the events you shared, I can see several successful deliveries to other webhook endpoints.

I think your tooling is doing something odd

[ebon cradle]

Right, yeah, and I totally get that possibility...but how do we explain the other services working correctly?

Nothing changes with my tunnel setup between the Hoppscotch request (which reaches the target fine) and the Stripe request (which "times out connecting to remote host").

Unless I shouldn't be taking that error message at face value, and/or there's some way to get more detail out of that failed response?

Ope, there it went!

[summer cloud]

Hi, stepping in and catching up

[ebon cradle]

Just retried that webhook again, and this time it worked. Only thing I can think of that would explain that is some sort of caching, presumably on Stripe's end?

I dunno, weird deal—but seems to be working now. Let me confirm with a fresh test payment real quick.

(and hi @summer cloud! 👋)

Yep, confirming—that went through as well.

Should be set—and yeah, caching is the only thing that would explain that randomly starting to work again, as I didn't change anything since the first successful Hoppscotch call. I dunno. 🤷‍♂️

Regardless, thank you for your help!!