#fate_error

1 messages ¡ Page 1 of 1 (latest)

full dustBOT
#

👋 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/1263291695215284336

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

proven schoonerBOT
#

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.

crisp dome
#

Hi there, it's a common problem and usually it's caused by the incorrect webhook secret

#

If you are running the endpoint through stripe listen, use the webhook secret generated by Stripe CLI

cosmic glen
#

Im taking my secret from the CLI

#

The one i get after running this command
stripe listen --forward-to localhost:3000/webhook

crisp dome
#

OK, do you have any middleware that process the requests before sending it to /webhook handler?

cosmic glen
#

Yup, im using BodyParser.
Do you recommended me to make a new file just to have my listener there?

#

Away from any middleware that affect the request?

crisp dome
#

Can you disable BodyParser and try again?

cosmic glen
#

Sure, brb

#

And yes, that was the problem, now im getting another error but its mine xd

full dustBOT