#akkusomer1
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- akkusomer1, 5 hours ago, 11 messages
- akkusomer1, 23 hours ago, 10 messages
- akkusomer1, 5 days ago, 13 messages
- akkusomer-email-testmode, 5 days ago, 11 messages
- akkusomer1, 6 days ago, 17 messages
I added the web hook endpoint to my code and I can run it locally, there is no problem.
Then, when I deploy my application and move it to the server, I first add the webhook to the dashboard to the giidp strip and I want to trigger the webhook after paying with the webhook secret key I bought to use in live, but I encounter the 403 forbiden error.
I allowed it to request all IP addresses on my server, and I also allowed webhook stripe IP addresses.
I'm encountering this in my server log, I can't find where the problem is.
While the stripe dashboard is in test mode, I can add a webhook and trigger an endpoint in my live application, right?
Sorry I'm still trying to grasp how this is a stripe issue
This seems purely based on your server configuration, no?
You're seeing 403 on Stripe because that's what your server responded with. You would have access to your server side logs to look at what's going on there
Yes, I see 403 in stripe. The server must accept all ropes as open. Is stripe sending the request but the server rejects it or should I add something else to my code?
I don't think its code related
it's just when Stripe sends the events, it expects 200 status code as response.
your server is responding with 403, meaning its blocking the access and refusing the request from going through to your code
So it mostly likely relates to your server configuration
So what response does it return if it tries to be triggered with the wrong webhook secret key?
No idea, it depends on your code as to how you handle signature verification error.
That's why you'd need to check your server-side logs