2 months ago
write exactly what i need to write
Copy and paste this exactly into the support form at https://station.railway.com/questions:
Title: Project token rejected as "invalid or expired" — blocking production deployment
Description: Project: juma-bottle-tracker (ID: 4ebb299a-d3f2-43e1-8f07-92034ef4ed44) Environment: production
I created a new project token from Railway → Project Settings → Tokens → New Project Token. The token was created successfully and copied immediately. When attempting to use it for deployment authentication (setting RAILWAY_TOKEN environment variable in Replit), Railway rejects it with: "invalid or expired"
What I've tried:
Created project token from Project Settings (scoped to project, not account)
Deleted all old tokens first to avoid conflicts
Copied the token immediately after creation
Submitted via secure environment variable form in Replit
Attempted deployment with the token
Current status:
api-server is online and operational
Database is connected and responding
Code is ready to deploy (email system and nightly scheduler implemented)
Deployment is completely blocked because the token is rejected as invalid/expired
No database data has been changed
I need: A valid project token that Railway will accept for this project, or investigation into why newly created project tokens are being rejected as invalid/expired.
11 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
What is your project using with the token? Are you using the GraphQL API?
2 months ago
replit is trying to deploy a new code to railway using the new project token
0x5b62656e5d
Is it using the GraphQL API or the CLI?
2 months ago
its CLI
0x5b62656e5d
Have you tried deploying from a local environment?
a month ago
i only can use replit development to create the code and have them deploy it to railway servers to use. it was working fine before. but not sure why it wont accept our CLI project token from railway.
a month ago
Can railway provide a workaround token or check if this project has a validation issue on Railway's side?
a month ago
Every project token I create is immediately rejected as 'invalid or expired' by the CLI. This isn't a timing issue — the tokens are broken at creation. This is a Railway platform bug affecting my project. I need Railway's engineering team to investigate why my project tokens are being generated as expired.
a month ago
URGENT: Still blocked after 2-3 days. Every token rejected. Need engineering escalation NOW.
a month ago
"Confirmed: I upgraded/repaired the Railway CLI as instructed. The token still fails with 'Invalid RAILWAY_TOKEN' and 'Unauthorized'. This confirms the issue is on Railway's backend, not the CLI. Please escalate to engineering immediately to investigate why this project's tokens are being rejected."
a month ago
"Please escalate this to Railway's engineering team. This is a backend token validation bug."
"This is day 4 of being blocked from deployment. Urgent escalation needed."
"When can engineering start investigating this?"