2 months ago
I get this when I try to deploy with a private template, from the CLI:
% railway whoami
Logged in as XXX (YYY) 👋
% railway deploy --template ZZZ
Unauthorized. Please run railway login again.Re-logging and so on do not solve this.
Claude Code faces the same problem when using the MCP or the recommended railway plugin.
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey, apologies for the delay here.
A few questions to help narrow this down:
- Can you share the output of
railway status? I want to confirm which project/environment is linked. - Does deploying a public template (e.g.,
railway deploy --template postgres) work, or do you get the same error? - Is this a template you created yourself in your workspace?
That'll help us figure out where the auth check is failing.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
Hi,
I do not get this problem with the API, and I am now using it instead. I have found telling Claude to use it to be much more reliable than the CLI, MCP and plugin.
Cheers,
Gabe
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved h-galfour • about 2 months ago