401 Unauthorized Error on Protected Endpoint Using THIRDWEB_API_SECRET_KEY in Railway Deployment
anons191
PROOP

a year ago

I'm deploying an app on Railway that needs to access a protected endpoint (/auth/permissions/get-all) using an Authorization header set with THIRDWEB_API_SECRET_KEY. This setup works perfectly on my local machine, but on Railway, the request returns a 401 Unauthorized error. I've ensured that THIRDWEB_API_SECRET_KEY is correctly set in Railway’s environment variables, and the Authorization header is included in my request code, but the error persists. I'm looking for insights on why this might be happening or any suggestions on Railway-specific configurations that could resolve the issue.

Solved

0 Replies

Status changed to Awaiting User Response Railway about 1 year ago


Railway
BOT

4 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 4 months ago


Loading...