reid-webhook-localhost | Stripe Developers | Page 1

lost gateBOT Oct 18, 2023, 5:48 PM

#

jagged fog Oct 18, 2023, 5:48 PM

#

reid-webhook-localhost

#

👋 @narrow atlas nothing specific has changed that I can think of. The first step is to explain what the issue is

narrow atlas Oct 18, 2023, 5:49 PM

#

When I run the command stripe listen --forward-to http://localhost:3000/stripe
I get output saying that I am listening, but then I dont see any event details when I trigger an event.

jagged fog Oct 18, 2023, 5:50 PM

#

but then I dont see any event details when I trigger an event.
that could mean a slew of different things and I'm going to sadly need a lot more about what the issue is. Like does it work with just stripe listen?

narrow atlas Oct 18, 2023, 5:52 PM

#

I get the same output, and likewise no activity when I trigger an event.

#

I do see output about upgrading the CLI, to 1.18.0, maybe thats my issue?

#

I am on 1.14.7

jagged fog Oct 18, 2023, 5:53 PM

#

it wouldn't hurt to upgrade. You can also try stripe listen --log-level debug to see if anything obvious is explained

narrow atlas Oct 18, 2023, 5:55 PM

#

I see some output that looks normal, and then a series of ongoing ping pongs

#

Should the signing secret in the output match the signing secret of the webhook I am wanting to listen to? It is not the same.

jagged fog Oct 18, 2023, 5:56 PM

#

hum I worry we're talking about completely different things.
My understanding of your question is that you see nothing on the command line where you run stripe listen. Is that not your question?

narrow atlas Oct 18, 2023, 5:59 PM

#

when I run stripe listen, I get the following output:

stripe listen
A newer version of the Stripe CLI is available, please update to: v1.18.0

Ready! You are using Stripe API Version [2022-08-01]. Your webhook signing secret is whsec****
And then no activity beyond that when triggering events.

jagged fog Oct 18, 2023, 6:00 PM

#

Okay so right now you can ignore your code entirely

#

the first step is to figure out why stripe listen doesn't work

#

hence the --log-level debug option to see what happens when you do stripe trigger in another terminal

narrow atlas Oct 18, 2023, 6:02 PM

#

I don't see any additional output with the debug flag when triggering an event

#

just this over and over:
[Wed, 18 Oct 2023 11:02:26 PDT] DEBUG websocket.Client.writePump: Sending ping message
[Wed, 18 Oct 2023 11:02:26 PDT] DEBUG websocket.Client.readPump: Received pong message

jagged fog Oct 18, 2023, 6:02 PM

#

do you still have stripe listen running and you do stripe trigger in another separate terminal?

narrow atlas Oct 18, 2023, 6:03 PM

#

I was pressing the resent event button in the dashboard.

jagged fog Oct 18, 2023, 6:04 PM

#

yeah that won't work

#

use stripe trigger

narrow atlas Oct 18, 2023, 6:04 PM

#

triggering from the terminal does give activity though

jagged fog Oct 18, 2023, 6:04 PM

#

the resend is only resend to the endpoints that were listening for it at the time, not your new instance of stripe listen

#

so you either

Start stripe listen and use stripe trigger to trigger specific Events
Start stripe listen and then use your code to cause Events such as creating a Customer or a Refund

narrow atlas Oct 18, 2023, 6:06 PM

#

Gotcha! I was under the impression that it would listen to any and all events, including resends that were not listened for originally. Thank you for clearing this up for me.

#reid-webhook-localhost