#dlindqu3
1 messages · Page 1 of 1 (latest)
What do you mean by "my step two"
Are you running stripe listen and seeing events?
that step 2
When I run the stripe listen, I get this:
But no green "completed" shows up on the screen after step 2 as expected
And the endpoint is still listed as disconnected:
I'm not sure what you mean by "green completed"
Those errors are coming from your local endpoint when the CLI tries to forward to them
I saw this in a youtube tutorial, the green highlighted "completed" should show up after a successful step 2 here
But I'm not getting that
Oh, i see
I'm not sure what drives that, but lets try and address the real issue of not getting events forwarded to your local server
cool
The listen output shows errors when you try to forward. What do you local dev server logs tell you?
Do you know where you're hitting errors?
do you mean the powershell logs?
I see this after running the "Forward events to your webhook" step: C:\Users\Dwight> stripe trigger payment_intent.succeeded
Setting up fixture for: payment_intent
Running fixture for: payment_intent
Trigger succeeded! Check dashboard for event details.
But don't see it in the dashboard
You showed logs here where stripe listen is trying to forward events, but the requests to your localhost server are returning errors
I mean, the logs for that localhost server. What is happening there? Where are these errors coming from?
I did those a few hours ago, I'm honestly not sure now
Trying to figure out what triggered them now
Sounds good -- yea you'll need to figure out why your server is returning errors to the listen forward requests
ok
I have these events, but cannot see them in the dashboard because the local endpoint is still disconnected
You should see them in the dashboard here: https://dashboard.stripe.com/test/events
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
They are real test mode events
That looks like you ran listen without forwarding
Ok I am going to keep trying to fix it, you can close the dialogue
I can keep it open here for a bit longer in case you hit something i can help with using our SDK/CLI