Skip to content
Railway SSH Available?
steelnjax
OP

22 days ago

Since about October 27, railway ssh into our production service fails every time. Authentication succeeds, then the connection drops with "An error occurred connecting to your service." As of today (Oct 29), it also sometimes times out connecting to ssh.railway.com on port 22.

  • Project: carefree-renewal (2d8c9191-3f8a-42a0-b41b-f7db0bc4d30c)
  • Environment / service: production / syngen. Our non-prod environment fails the same way.
  • CLI: 5.71, tried with two different SSH keys.

We rely on railway ssh to run a delivery job inside this service, and those deliveries are blocked until it works. Could you confirm whether this is a known issue, and when it will be restored. Thank you in advance!

Solved

5 Replies

Status changed to Awaiting Railway Response Railway • 22 days ago


dizzydes90
EMPLOYEE

22 days ago

Hi,

Thanks for the detail. A healthy service that SSH authenticates to and then drops with "An error occurred connecting to your service" has one cause to rule out first. Could you check whether Static Outbound IPs is enabled on the syngen service, under its Settings, Networking, in production and in your non-prod environment? SSH and the dashboard Console are not available on a service with that feature enabled: the connection is accepted at ssh.railway.com and then closed, and redeploying or trying a different key doesn't change it. That would also explain both environments failing the same way.

If it is on, the ways to get a shell are to turn the feature off while you run the delivery job and back on afterwards (the assigned addresses are released when it's off and may differ when re-enabled, so avoid this if an external allowlist depends on them), or to run the job from a service without it, for example a sibling service from the same image using reference variables. If it is not on, reply here and we'll look further; nothing will be restarted or changed on our side without you.


Status changed to Awaiting User Response Railway • 22 days ago


dizzydes90

Hi, Thanks for the detail. A healthy service that SSH authenticates to and then drops with "An error occurred connecting to your service" has one cause to rule out first. Could you check whether Static Outbound IPs is enabled on the syngen service, under its Settings, Networking, in production and in your non-prod environment? SSH and the dashboard Console are not available on a service with that feature enabled: the connection is accepted at ssh.railway.com and then closed, and redeploying or trying a different key doesn't change it. That would also explain both environments failing the same way. If it is on, the ways to get a shell are to turn the feature off while you run the delivery job and back on afterwards (the assigned addresses are released when it's off and may differ when re-enabled, so avoid this if an external allowlist depends on them), or to run the job from a service without it, for example a sibling service from the same image using reference variables. If it is not on, reply here and we'll look further; nothing will be restarted or changed on our side without you.

steelnjax
OP

22 days ago

Thank you, that explains it. Static Outbound IPs are enabled on syngen in both production and non-prod.

Is SSH and Console access for services with Static Outbound IPs enabled something you plan to support in the future? If so, is there an expected timeframe? We can't turn static IPs off because an external partner allowlists those addresses, so we'd like to know whether to plan around this long term.


Status changed to Awaiting Railway Response Railway • 22 days ago


22 days ago

We aim to make SSH and Console work with Static Outbound IPs in the coming weeks, but we can't give a concrete timeline yet, so it's safest to plan around the current limitation for now.

In the meantime, one way to keep your static IPs is to deploy a separate small service without Static Outbound IPs in the same project and environment as a jumpbox. On its own, a jumpbox does not give you a shell inside syngen. You would also need to run a customer-managed SSH server inside syngen's image, listening on the private network, and connect to it from the jumpbox. That keeps syngen's outbound traffic on the allowlisted addresses.


Status changed to Awaiting User Response Railway • 22 days ago


steelnjax
OP

22 days ago

Got it. Thank you!


Status changed to Awaiting Railway Response Railway • 22 days ago


Status changed to Solved brody • 22 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.


Status changed to Awaiting User Response Railway • 16 days ago


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...