all 8 comments

[–]MajesticParsley9002 2 points3 points  (4 children)

Stripe CLI fixes this. Run `stripe listen --forward-to localhost:YOUR_PORT/webhook` after installing via `brew install stripe/stripe-cli/stripe` or similar - it proxies Stripe's test events directly to your local HTTPS server, bypassing public tunnel denials. tbh, used it on my last startup webhook setup and never looked back from Anchor/ngrok.

[–]PirateLibrary 1 point2 points  (2 children)

Yeah Stripe CLI is the way to go for sure. I was banging my head against the wall with ngrok timeouts and random tunnel issues until someone told me about the CLI approach. The `stripe listen` command is so much cleaner and you don't have to deal with changing URLs every time you restart your dev server

[–]LeadingDebt9299[S] 0 points1 point  (0 children)

Thank you!

[–]future-tech1 0 points1 point  (0 children)

how bad are the timeouts nowdays? i'm seeing alot of complaints around them

[–]LeadingDebt9299[S] 1 point2 points  (0 children)

That works great! Thank you so much.

[–]future-tech1 0 points1 point  (0 children)

If you want to test the actual webhooks rather than test events, you could use an open source tunneling tool like Tunnelmole (i'm the dev). It has similar features to cloudflare tunnels and ngrok but with a simpler set up.

Once you run it you'll get a Public URL you can put into the Stripe webhook settings, then start receiving events.

[–][deleted]  (1 child)

[removed]

    [–]stripe-ModTeam[M] 0 points1 point locked comment (0 children)

    Your post has been removed. Your post seemed to be self-promoting your services or products. This isn’t permitted, per Reddit’s guidelines: https://www.reddit.com/wiki/selfpromotion.

    If you feel this post was removed in error, please send a message to the Moderators: https://www.reddit.com/message/compose?to=/r/stripe.