9 months ago
I have a backend ts service that doesnt deploy, always fails at healthchecks and doesnt really have any error logs just "stopping container"
But when i make a new service and deploy the same exact codebase it works but this time it keeps throwing a 401
NOTE: i reverted all recent commits and changes i made
2 Replies
9 months ago
Check your deploy logs.
A 401 isn't an error Railway returns, so this is an issue with your application and we cannot help you with that sorry.
Status changed to Awaiting User Response Railway • 9 months ago
9 months ago
Noted with thanks, the deploy logs werent showing anything useful so i thought it might be a config error.
I will have a closer look, thank you very much for your help
Status changed to Awaiting Railway Response Railway • 9 months ago
Status changed to Solved ray-chen • 9 months ago