Skip to content
How can I verify the ED25519 host fingerprint for ssh.railway.com:22?
grundlegunt
OP

8 days ago

Before connecting to ssh.railway.com on port 22, I would like to independently verify its SSH server identity. Could Railway provide the current verified ED25519 host public key or SHA256 fingerprint, or point me to the supported method for verifying it? This question concerns the server host key, not my account SSH key. No credentials or private keys are included.

Solved

3 Replies

Railway
BOT

8 days ago

We don't publish a host key, fingerprint list, known_hosts entry, SSHFP record, or host CA for ssh.railway.com, so there isn't a supported way to check its host key against a reference from us.

The endpoint is served by multiple hosts, each with its own ED25519 key. Those hosts change regularly without notice, so the fingerprint you see can differ between connections and will change over time. A changed fingerprint on this endpoint is expected, and we can't confirm or deny any specific fingerprint you observe.


Status changed to Awaiting User Response Railway • 8 days ago


Railway

We don't publish a host key, fingerprint list, known_hosts entry, SSHFP record, or host CA for `ssh.railway.com`, so there isn't a supported way to check its host key against a reference from us. The endpoint is served by multiple hosts, each with its own ED25519 key. Those hosts change regularly without notice, so the fingerprint you see can differ between connections and will change over time. A changed fingerprint on this endpoint is expected, and we can't confirm or deny any specific fingerprint you observe.

grundlegunt
OP

8 days ago

Could a human member of Railway Support please review this? We need a supported way to authenticate the remote server before transferring a staging PostgreSQL backup. If ssh.railway.com has no verifiable host key or host CA, what supported connection or export method provides server identity verification (for example, certificate-validated TLS)? Please explain how to verify the endpoint and which official documentation to follow. We want to keep host/certificate verification enabled and avoid blindly accepting changing keys. Please keep this question open for human guidance.


Status changed to Awaiting Railway Response Railway • 8 days ago


8 days ago

The above response is correct.


Status changed to Awaiting User Response Railway • 8 days ago


Railway
BOT

a day 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 • about 23 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...