an hour ago
Please have a Railway engineer confirm the current ED25519 host key fingerprint for ssh.railway.com:22, or provide an authenticated way to verify the SSH gateway identity. The official Railway CLI presented SHA256:+S1xg92FrnHz6pY3bpkmh1OGtWQGNANXilPzlxA7B1g on 20 November 2026. We have not accepted this key. Our owner requires verification before access to a private staging service. Existing automated support replies say fingerprints are not published; please escalate to a human engineer. If stable fingerprints or a host CA are unavailable, what supported alternative allows authenticated command execution or a consistent volume backup over HTTPS without trusting an unverified SSH host key? No credentials or private project data are included in this request.
1 Reply
an hour ago
We don't confirm or attest SSH host key fingerprints for ssh.railway.com, and we don't publish a fingerprint list, known_hosts entry, SSHFP record, or host CA. The endpoint is served by multiple hosts, each with its own key, and those hosts change without notice, so the fingerprint can differ between connections and over time. We can't confirm or deny the specific fingerprint you received, and how you handle host key trust for this endpoint is your decision.
For a consistent copy of volume data without SSH, volume backups are managed from the service's Backups tab in the dashboard, where you can create a backup manually, set a daily, weekly or monthly schedule, and restore one into the same project and environment. Details are in the backups guide.
Status changed to Awaiting User Response Railway • about 1 hour ago