8 days ago
Hello Railway Community,
I'm experiencing a persistent SSH connection issue with a Railway-hosted application and would appreciate help identifying the cause.
The application itself is running normally, but I cannot establish an SSH connection to its container.
What is working:
- Railway API and CLI authentication succeed.
- The correct project, environment and service are selected.
- The service shows Online.
- The public health endpoint returns HTTP 200.
- The application is functioning normally.
The problem:
When attempting to connect using Railway CLI SSH, the connection stalls after selecting the configured SSH key and attempting transport to ssh.railway.com.
No authentication response or remote command output is received.
The connection eventually times out.
Troubleshooting already completed:
- Verified Railway CLI authentication.
- Verified project, environment and service selection.
- Verified the CLI binary.
- Closed two stale local Railway SSH processes.
- Confirmed no orphaned SSH processes remained.
- Started a fresh CLI session.
- Attempted one minimal read-only SSH command with a 20-second timeout.
The fresh attempt failed in exactly the same way.
Last failed attempt: November 11, 2026, at approximately 8:30 AM Pacific.
No application deployments, restarts, credential changes or network configuration changes were made during troubleshooting.
My questions:
- Is there a known issue affecting Railway SSH connections to otherwise healthy services?
- Could this be related to Railway's SSH tunnel or authentication transport?
- Are there recommended diagnostics or network settings to check on Windows?
- Is there a supported method to restore SSH access without restarting or redeploying the application?
This is blocking an important configuration deployment for my business, so any guidance would be greatly appreciated.
Thank you!
1 Reply
8 days ago
There is an open incident where some network providers and security services are blocking Railway IP addresses, which can stop connections to Railway endpoints such as ssh.railway.com from affected networks while the services themselves keep running: External network blocks affecting access to Railway. A stall at the transport step before any authentication response fits that pattern, so trying the same command from a different network (for example a phone hotspot) is the quickest way to tell, and your network administrator or provider can use that notice to review any blocks on Railway IPs.
Your jenna-staging service in the staging environment is running on a successful deployment, and SSH does not require restarting or redeploying it. Use the service-level command without the -d / --deployment-instance flag, railway ssh --project <project-id> --service jenna-staging --environment staging.
If it still stalls from another network, please share the exact command you ran, your CLI version, and the verbose output of that attempt with any secrets redacted, along with the time in UTC.
Status changed to Awaiting User Response Railway • 8 days ago
a day ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 22 hours ago