#wess_webhooks

1 messages ¡ Page 1 of 1 (latest)

fiery warrenBOT
#

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

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

hidden anchorBOT
#

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.

deft dawn
#

Are you using the correct webhook secret? Your live and test mode webhook endpoints have different webhook secrets, so I just want to be sure you're not using the same one for both endpoints

stone spoke
#

yes sir

#

in vercel i have 2 different env vars

#

one for production (live) and for preview and developement i pasted the one i grabbed from test webhook

deft dawn
#

Ah, actually when I take a closer look at the response you sent back from your server, you're responding with 401 + authentication required. Do you have some kind of password protection or authentication enabled for your test endpoint?

stone spoke
#

hmm, not really, using the same code as in prod, where it was working

deft dawn
stone spoke
#

okay i might get back after some debugging

#

lets keep this chat open please

deft dawn
#

@stone spoke were you able to get it sorted out?