#stephy
brave bison
👋 how may I help?
signal plinth
i have issues in my webhooks.. i create endpoint in stripe dashboard and then i write code in backend also
brave bison
what's the issue?
brave bison
you don't have any logging, I can't really tell what's happening
brave bison
your webhook is redirecting to this URL https://phplaravel-813399-3371113.cloudwaysapps.com/frontend-login
signal plinth
brave bison
I think you have an Authentication guard
that requires anyone trying to POST to /stripe/webhook to be authenticated which you shouldn't do
signal plinth
so i have to written without gurud right?
brave bison
yes that's correct, the URL should be available for everyone
the way to secure the webhook is by using the webhook signatures https://stripe.com/docs/webhooks#secure-webhook
signal plinth
evt_1NvIPtEZ1Pyl4W3kHcksM4Bb
brave bison
there's no response body, I can't really tell what's happening there
actually why do you have 2 endpoints?
https://phplaravel-813399-3371113.cloudwaysapps.com/payment/success
https://phplaravel-813399-3371113.cloudwaysapps.com/stripe/webhook
it's on the same server
signal plinth
yes
brave bison
why then?
signal plinth
https://phplaravel-813399-3371113.cloudwaysapps.com/stripe/webhook
this is actually i want to use..other one is get method which is working
fast totemBOT
late portal
makes sense. You need to figure out what your server sends a 419 and fix that.
signal plinth
csrf issue that i fixed
late portal
if I Google "419 Lavarel" I see some results about it being because a CSRF token is needed, you need to disable that for something like a webhook, which doesn't come from a browser.
late portal
csrf issue that i fixed
great then what's the current problem?
If it relates to evt_1NvIPtEZ1Pyl4W3kHcksM4Bb, as my colleague said, we have no way to know. All we know is your code on your server returned a 400 HTTP status. As the developer of that code, you need to investigate your code and logs to see what happened.