6 days ago
Since about 5 Nov, including on a brand-new project and service created today (no static IPs):
railway ssh -- ls /data prints “Sorry Railway TUI not currently available”, then “Connection to ssh.railway.com closed.”
railway volume files upload … fails with “Failed to initialize SFTP session: Timeout”.
CLI 5.49.6 and 5.74.0 behave the same. Tried a passphrase-free registered key. Region: Southeast Asia. Service deploys and runs normally.
Is SSH/SFTP currently degraded? Any workaround to upload a file to a volume?
1 Reply
6 days ago
We don't have a known SSH or SFTP degradation to point to for these errors. We understand how disruptive it is when you need to get a file onto a volume.
On the new project you created today, the latest deployment started about 10 minutes ago and is still waiting on its healthcheck, so it hasn't become a healthy running deployment. SSH, railway volume files and railway volume browse all need a healthy running instance of the attached service. Until that deployment passes its healthcheck, those commands aren't a supported way to reach that volume.
Your account is active and your other services have healthy deployments. For those, a connection failure like this comes from the local computer or network environment, and troubleshooting that environment is outside what Railway support covers. railway volume files upload runs over the same SSH/SFTP connection, so it isn't a separate route around this failure.
Status changed to Awaiting User Response Railway • 6 days ago