vercel and secret string
# support
n
Hey everybody, has anybody had any luck with the server side example serverless vercel deployment I would greatly appreciate anyone that can help me troubleshoot a load of 401 errors
v
@NoDegeneratesNoRadicals Hello! I'd be happy to help you troubleshoot the 401 errors you're encountering with your serverless Vercel deployment. A 401 error typically indicates an authentication issue, which means there might be a problem with your API keys, tokens, or the way you're handling authentication in your application. To assist you better, could you provide me with more details about your setup? Specifically, I need to know how you're handling authentication and if you've checked that your API keys or tokens are correctly set in your environment variables. Additionally, it would be helpful to know if you've followed the documentation for authentication provided by Vercel and the specific service you're trying to authenticate with.
You can continue this conversation by mentioning me in the message.
n
Certainly well I can curl the Versailles server and get A 200 response. But everything to do with a web call from the dashboard just posts up as an unexpected server secret.. the same server secret
Massively quick off the mark very impressed
I did switch off authentication on the vercel server
As that was sending me to a 404 page
..... The logs in verscel say that it's receiving an unexpected secret and that the received secret is undefined
s
Can you provide me the reproducible link and your Vercel URL? Because I tried it and it was working fine.
2 Views