Hello, railway ssh for our production project stopped because the ED25519 host key presented by ssh.railway.com differs from the key currently stored in our known_hosts. We have intentionally not bypassed strict host-key verification. Current details: - Railway CLI: 5.31.0 - Timestamp: 2026-08-15T12:48:00Z - Host: ssh.railway.com - Previously trusted ED25519 fingerprint: SHA256:+S1xg92FrnHz6pY3bpkmh1OGtWQGNANXilPzlxA7B1g - Newly presented ED25519 fingerprint: SHA256:vJZQoaqWa82yW+Oe0SgY1zRmql6V0TJxuWgVoZB1pyE Could you please confirm: 1. whether the new fingerprint is an official current Railway SSH host key; 2. whether Railway recently rotated this key; 3. whether the previous fingerprint is now obsolete; 4. the recommended safe procedure for updating the single ssh.railway.com entry in known_hosts; 5. whether Railway publishes authoritative SSH host-key fingerprints anywhere. We have not used StrictHostKeyChecking=no, accept-new, or removed the existing entry. Thank you.

Please verify changed ED25519 host key for ssh.railway.com

jarbulove-ai

HOBBYOP

6 days ago

Hello,

railway ssh for our production project stopped because the ED25519 host key presented by ssh.railway.com differs from the key currently stored in our known_hosts.

We have intentionally not bypassed strict host-key verification.

Current details:

Railway CLI: 5.31.0
Timestamp: 2026-08-15T12:48:00Z
Host: ssh.railway.com
Previously trusted ED25519 fingerprint:

SHA256:+S1xg92FrnHz6pY3bpkmh1OGtWQGNANXilPzlxA7B1g
Newly presented ED25519 fingerprint:

SHA256:vJZQoaqWa82yW+Oe0SgY1zRmql6V0TJxuWgVoZB1pyE

Could you please confirm:

whether the new fingerprint is an official current Railway SSH host key;
whether Railway recently rotated this key;
whether the previous fingerprint is now obsolete;
the recommended safe procedure for updating the single ssh.railway.com entry in known_hosts;
whether Railway publishes authoritative SSH host-key fingerprints anywhere.

We have not used StrictHostKeyChecking=no, accept-new, or removed the existing entry.

Thank you.

Solved$10 Bounty

3 Replies

Railway

BOT

6 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 6 days ago

jarbulove-ai

HOBBYOP

6 days ago

This is currently blocking production SSH access. We only need an authoritative confirmation whether the newly presented ED25519 fingerprint belongs to ssh.railway.com. We are intentionally not bypassing StrictHostKeyChecking or replacing the known_hosts entry without verification. A Railway employee/Conductor confirmation would be greatly appreciated.

brody

EMPLOYEE

6 days ago

It is; it is one of many keys, but it will change again. We do not guarantee the lifespan of any particular key, nor do we provide a list of currently valid keys.

We also will not be able to manually validate keys going forward; this was a one-time act of goodwill to unblock you immediately.

Status changed to Awaiting User Response Railway • 6 days ago

brody

It is; it is one of many keys, but it will change again. We do not guarantee the lifespan of any particular key, nor do we provide a list of currently valid keys. We also will not be able to manually validate keys going forward; this was a one-time act of goodwill to unblock you immediately.

jarbulove-ai

HOBBYOP

6 days ago

Thank you for confirming this and for the one-time verification. This unblocks us.

We understand that ssh.railway.com may rotate between multiple valid host keys and that Railway does not guarantee the lifetime of a particular fingerprint or provide a complete list of currently valid keys.

We’ll proceed with the confirmed key for the current connection and adjust our Railway-specific SSH handling accordingly.

Thanks again for the help.

Status changed to Awaiting Railway Response Railway • 6 days ago

Status changed to Solved Railway • 6 days ago

Welcome!