#_webhooks

1 messages ยท Page 1 of 1 (latest)

red brookBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1361683834550227137

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

lament ivy
#

Hi, let me help you with this.

#

Your own app responds with 400 error code. You should be able to find out why by looking at your backend logs.

honest whale
#

[2025-04-15 08:40:22] production.ERROR: Stripe signature missing in the request
[2025-04-15 08:59:14] production.ERROR: start

lament ivy
#

Probably, something in your app/server provider is erasing the Stripe signature header.

honest whale
#

i will check but this app works fine 3 years and i was change nothing even server provider is same

lament ivy
#

Can you check why Stripe signature missing in the request is printed?
Could you please share the webhook handler code?

honest whale
#

also sometimes

#

it dont have any problem for example

#

pi_3RD57ZIE2Q2VDUZM1k4x2EsQ

red brookBOT
honest whale
#

this is broken payment example

#

pi_3RE5npIE2Q2VDUZM0gu72whS

long oyster
#

Stepping in for vanya as they need to step away

honest whale
honest whale
long oyster
#

one of the following likely changed:
1/ You rolled your endpoint secret in your Dashboard or modified your environment so that STRIPE_WEBHOOK_SECRET no longer matches the expected value
2/ Something about your request handling changed such that $headers['Stripe-Signature'] is not getting the expected value

honest whale
honest whale
#

0 problems

long oyster
#

Ok, that's your local CLI endpoint though, not your hosted endpoint

honest whale
#

1 sec

#

i will put test key on production for sec

#

and i will test for u

#

on production also no problem

#

on test key

#

pi_3RE9WFIE2Q2VDUZM1sHMoZkg

long oyster
#

Well your test webhook endpoint is disabled

#

so i wouldnt expect any delivery issues, since there is no delivery

honest whale
#

1 sec i can change key

#

ok i see now get 400 as well

long oyster
#

Yes i see your test endpoint is enabled again now, and also encountering delivery failures