Railway CLI SSH authentication fails when listing volume files
arsmarttrading
HOBBYOP

2 hours ago

Hello Railway Support,

I'm using Railway CLI 5.71.0 on Windows with an existing registered ED25519 SSH key.

When I try to list files from a persistent Railway volume, the CLI prompts for my SSH key passphrase and then fails with:

  • Failed to authenticate via SSH key
  • Channel send error

The service is running, but I need read-only access to its persistent journal to verify whether an earlier acceptance test completed and cleaned up successfully.

Could a Railway engineer please clarify:

  1. How to diagnose the SSH authentication failure without replacing existing keys?
  2. Whether there is a secure method to access volume files without SSH?
  3. How to verify the SSH server's identity on first connection?
  4. Whether Railway support can perform a read-only process and journal inspection if authenticated access remains blocked?

Please do not restart, redeploy or modify the existing service, volume or journal.

Thank you.

Awaiting User Response

1 Replies

Status changed to Awaiting Railway Response Railway • about 2 hours ago


sam-a
EMPLOYEE

2 hours ago

We haven't changed anything on the service, volume or journal, and this reply doesn't change anything either.

On server identity: ssh.railway.com is served by multiple hosts, each with its own host key, and those keys can change at any time without notice. We don't publish fingerprints or a known_hosts list, and we can't confirm a specific fingerprint, so a different or changed fingerprint is expected.

On the authentication failure: if the service has Static Outbound IPs enabled, Railway SSH and the dashboard console are currently unavailable for it. In that case the usual workaround is to deploy a separate small service without Static Outbound IPs as a jumpbox. Could you confirm whether that feature is enabled on this service?

On read-only inspection: we don't inspect processes, files or volume contents inside a customer's container for them. Access to the journal has to come through your own authenticated session.


Status changed to Awaiting User Response sam-a • about 2 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...