6 hours ago
Hello Railway Support. On Railway Hobby, an interactive Railway CLI SSH session to a running PostgreSQL service closes before a shell opens. The same registered key previously worked for this service. Railway CLI 5.75.0 launches system OpenSSH and forwards the explicit identity file. In Windows Terminal, after the local key passphrase prompt, OpenSSH reports “Connection closed by 66.33.22.3 port 22”. Is there a supported way to recover administrative access to the current container without restarting or redeploying it, or to diagnose why the Railway SSH gateway closes the session? We need to preserve the running database and its private-only access. Please tell us how to provide service and deployment IDs privately if needed. Please do not restart or redeploy the service.
1 Reply
6 hours ago
Your workspace is active and your PostgreSQL services show successful, running deployments, so an SSH session that closes after your local key prompt points to your computer or network connection. Troubleshooting that local environment is outside what we support, and sending us service or deployment IDs won't change that.
Restarting or redeploying won't fix this kind of connection failure. The dashboard Console and Files, railway volume browse, and SCP/SFTP all use the same SSH connection, so they won't work around it.
Status changed to Awaiting User Response Railway • about 6 hours ago