-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Stripe webhook endpoint #979
Comments
On or about the time this behavior began, I also changed the case of the stripe config values since Shady's most recent PR indicated that was required (change from camelCase to PascalCase). Not sure if that is related. |
@ardalis |
I can't get into Azure to do anything and I think Stripe is still trying to
hit the old endpoints.
…On Mon, Dec 12, 2022 at 5:06 PM Shady Nagy ***@***.***> wrote:
@ardalis <https://github.com/ardalis>
I think it is the old endpoint, so we can remove it from the stripe, as we
should have already added the new hooks (endpoints) in the stripe.
—
Reply to this email directly, view it on GitHub
<#979 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF66L67VSVKYO4SAPI6O7LWM6OU7ANCNFSM6AAAAAAS4DSCFM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Steve Smith
http://ardalis.com | http://twitter.com/ardalis
|
I'm hoping this is fixed now - waiting to confirm |
Apparently it's 404ing, per this 8 Dec 2022 email:
Seems to have been introduced with deployment of #964 or #965.
The text was updated successfully, but these errors were encountered: