venerios

[sage mesa]

Are you able to make a POST request to your localhost address from machine? Is the webhook server running?

[kindred geyser]

Yes, I regularly send post requests from the front-end of my site, no problem

How can I check that the webhook server is running? apart from on the dashboard?

[sage mesa]

Try making a POST request to localhost:3001/backend/webhook manually via your front-end or using a tool like POSTMAN

[kindred geyser]

I've just tried it with post man and I've received the request on my back-end and received this response: Webhook Error: No stripe-signature header value was provided. which is normal.

[sage mesa]

Gotcha. So that means that the server is running.

If you don't use --forward-to when running stripe listen are you seeing any logs in your console?

[kindred geyser]

I try this :

`stripe listen` does not take any positional arguments. See `stripe listen --help` for supported flags and usage```

[sage mesa]

no, just try stripe listen

[kindred geyser]

Okay, I got this:

stripe listen Ready! You are using Stripe API Version [2022-11-15]. Your webhook signing secret is whsec_e61893e4f6e59597f619fac43495dfcb5d0ce51018d97088f7c04341b6dee98b

and I tried the trigger again

But still nothing in log

[sage mesa]

Interesting, that's quite weird.
Can you try loging into Stripe CLI again?

stripe login

[kindred geyser]

No problem, I guess:

Could it be the anti-virus?

[sage mesa]

It could be, yes. The firewall might be blocking incoming requests

[kindred geyser]

What is the protocol and port number of stripe ?

[sage mesa]

Not sure I follow, the webhook events are delivered using a POST HTTP request.
It should come from one of the IPs listed here
https://stripe.com/docs/ips#webhook-notifications

I'd recommend disabling the firewall to check if the issue resolves itself first

[kindred geyser]

Ok I'll look at it tomorrow, I've finished my day for me, thank you