Skip to content
SSH fails with HA Static Outbound IPs; worker-only test restores access
renzo444
OP

20 days ago

We reproduced an SSH/Console regression on October 31, 2026 using Railway CLI 5.71.0 on macOS.

Timeline (UTC):

  • 18:13: SSH to our production web service last worked.
  • 19:36–19:40: HA Static Outbound IPs were enabled on the production web (Virginia) and worker (California), taking effect on later redeployments.
  • After those redeployments, both SSH and dashboard Console failed. TCP to ssh.railway.com:22 works and public-key authentication succeeds; the connection then closes about nine seconds later with “An error occurred connecting to your service. Please try again.”
  • 22:14:58: a fresh worker SSH check still failed.
  • We disabled Static Outbound IPs on the worker only and redeployed its existing, unchanged image. Deployment succeeded at 22:15:28.
  • 22:15:32: the same worker SSH command returned “ok” with exit code 0.

The web service remains healthy with its existing deployment and Static Outbound IPs unchanged. External firewall allowlists depend on its fixed addresses, so we cannot disable them there. No SSH keys or application code were changed during this test.

This matches the acknowledged issue in https://station.railway.com/questions/cannot-connect-to-the-console-of-my-serv-60d55d58 . Please confirm the fix status and a supported way to retain static outbound IPs alongside Railway-managed SSH. We can provide service IDs privately if needed.

No credentials, environment-variable values, application data, or sample contents are included in this report.

Solved

2 Replies

Railway
BOT

20 days ago

We're sorry this has been blocking access to your production services. SSH and Static Outbound IPs are currently incompatible, so Railway SSH and the dashboard Console are unavailable on any service with Static Outbound IPs enabled, which matches what you saw on the worker before and after disabling it.

To keep the fixed addresses on the web service, the workaround is to deploy a separate small service without Static Outbound IPs in the same project to use as a jumpbox. We aim to resolve the incompatibility in the coming weeks, but we cannot give a concrete timeline yet.


Status changed to Awaiting User Response Railway • 20 days ago


16 days ago

SSH should now work with Static Outbound IPs enabled. Please try connecting again and let us know if you still run into any issues.

Thank you for your patience.


Railway
BOT

9 days 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 • 9 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...