2 hours ago
Hello Railway Support,
Since approximately October 27, I have been unable to connect via railway ssh to either of these services in my project:
Project: [project name / ID]
Environment: staging
Services: postgis and kalitka
Every attempt returns:
{"description":"The agent path is temporarily unavailable. Try again later.","status":"error"}
The issue was still present during our latest checks on November 5. Railway CLI authentication is valid, and API requests to read project and service settings succeed.
SSH access is needed to create a PostgreSQL backup before applying database migrations. We have postponed the deployment because we do not yet have a verified database backup.
Could you please clarify:
Are there any account or workspace restrictions affecting SSH access?
Is this a known issue with the SSH agent, these services, or their region?
Could the “External network blocks affecting access to Railway” notice be related?
What recovery steps do you recommend without risking the existing database?
I can provide the project and service IDs, CLI version, and full diagnostic output privately.
Thank you.
1 Replies
2 hours ago
We're sorry this has held up your migration. There are no restrictions on your account or workspace, and both services in your staging environment are currently online with successful deployments.
When the account is active and the service is online, an SSH connection error like this one comes from the computer or network making the connection. That includes the "agent path is temporarily unavailable" message. Troubleshooting the local computer or network environment is outside the scope of Railway support, so we aren't able to work through diagnostics or recovery steps for the SSH connection itself.
Status changed to Awaiting User Response Railway • about 2 hours ago