Skip to content
Verify Railway SSH relay host keys and least-privilege unattended monitoring access
kruptoey
OP

17 days ago

We maintain an existing Railway project and are preparing a scheduled aggregate-only health monitor. The reviewed CLI is Railway 5.62.1, which connects through the native SSH relay ssh.railway.com. The operator connection already works.

Before enabling a clean CI runner with StrictHostKeyChecking=yes, please provide an authoritative current set of SSH server public host keys (known_hosts format), or an official HTTPS URL publishing those records, and the host-key rotation procedure. Our existing local operator trust record has ssh-ed25519 SHA256:+S1xg92FrnHz6pY3bpkmh1OGtWQGNANXilPzlxA7B1g. This is an observation to compare, not a request to accept an unverified key.

Please also confirm the supported least-privilege setup for unattended access to one existing project/environment: can an SSH key be restricted to that project/environment/service and read-only execution, or does it inherit broader account/workspace access? If command-level restrictions are unavailable, please confirm that limitation and the recommended supported alternative. We do not want to copy a personal login or workspace-wide SSH credential into CI.

No private key, API token, database credential, learner data or payment details are included. Monitoring and notifications remain disabled pending verification.

Solved

1 Reply

Railway
BOT

17 days ago

We don't publish a known_hosts list, fingerprint set, SSHFP record or host CA for ssh.railway.com, and we can't confirm or deny a specific fingerprint, including the one you observed. The endpoint is served by multiple hosts, each with its own key, and those hosts change routinely without notice, so the presented key can differ between connections and over time. There is no Railway host-key rotation procedure to follow, and how you handle host-key trust for this endpoint in CI is your decision.

On scoping, a workspace SSH key grants SSH access to every service in that workspace. Narrowing a registered key to a single project, environment or service, or limiting it to read-only commands, is not an option in the SSH key settings. For CI auth, the CLI separates project-scoped RAILWAY_TOKEN from account or workspace-scoped RAILWAY_API_TOKEN, and SSH key management requires the broader token or railway login, not a project token. More detail is in the railway ssh docs and CLI login docs.


Status changed to Awaiting User Response Railway • 17 days ago


Railway
BOT

10 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 • 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...