Hello!!

I'm experiencing intermittent issues with SSH connections to my deployed services and would like to understand if this is expected behavior or a known issue.

Issue Details:

• Error Message: "Failed to establish connection after 3 attempts: deadline has elapsed"

• Frequency: Intermittent - sometimes SSH works, other times it fails completely

• Service Status: The service is actively running and responding to HTTP requests (curl to /api/health works fine)

• Network Configuration:

  • WebSocket connectivity confirmed working (tested with wscat to wss://echo.websocket.org), not behind corporate firewall/VPN, serverless mode is disabled, service has been "awake" when attempting connection

What I've Tried:

1. Updated Railway CLI to latest version

2. Re-authenticated with railway logout and railway login

3. Verified service is responding to HTTP requests before attempting SSH

4. Tested WebSocket connectivity independently (working fine)

5. Waited 5-10 seconds after making HTTP requests to ensure container is active

6. Tried both railway ssh and explicit commands like railway ssh --service <name> --environment <env>

Environment:

• Platform: macOS

• Railway CLI Version: latest

• Service Type: NestJS backend with Dockerfile

• Region: europe-west4

Questions:

1. Is intermittent SSH connectivity a known issue within the Railway ecosystem?

2. Are there any service-level configurations or requirements I might be missing?

3. Is there a way to check SSH service health status on Railway's end?

4. Should I expect SSH to work 100% of the time when the service is active, or is some degree of intermittency normal?

5. Could this be related to my home network configuration? I've read in some threads that switching to mobile data sometimes resolves SSH connection issues - is this a known network compatibility problem?

The service itself is working perfectly fine for HTTP requests - this issue only affects SSH connectivity, which makes debugging and running administrative tasks challenging