Webhook signature not being parsed on live production server, 500 returned before reaching job #153
Unanswered
hondaman900
asked this question in
Q&A
Replies: 2 comments
-
Nevermind my questions about laravel-webhook-client. I since found it's a dependency of laravel-stripe-webhooks. Still have no idea as to how to proceed to resolve this - help! |
Beta Was this translation helpful? Give feedback.
0 replies
-
OMG!! I am such an idiot. I didn't change out the Stripe CLI secret key for the one provided in the Stripe dashboard for the specific webhook |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As far as I can determine, on my production server (Forge/DigitalOcean Droplet) the Stripe signature is not being parsed correctly before reaching the job to process the payload. Laravel is returning an invalid signature and a 500 error to Stripe (instead of 200) and the processing of the payload fails, resulting in successful payment but not being able to establish the customer's subscription.
From my earlier working on this app I have
laravel-webhook-client
and I'm wondering if this is somehow conflicting with (or intercepting) something as it seems to be involved in the stack trace below. Is there a safe way to remove this without breaking things more, or is it a dependency oflaravel-stripe-webhooks
?This is only not working on the production server, which should be identical to my local dev app which works fine. I can't see/find a difference between the live and dev versions that would account for this. The local dev version uses the webhook secret provided for Stripe CLI whereas the live version uses the webhook secret provided by the Stripe dashboard.
Here's the error and stack trace. I welcome any suggestions as to how to diagnose and/or resolve this, as I'm at a loss as to what to try next.
Beta Was this translation helpful? Give feedback.
All reactions