Skip to content
Railway SSH Security and Storage Audit
10thcosmos
OP

a month ago

Hello Railway Support Team,

We are configuring secure SSH access to our production CVS Matrix service.

Project: genuine-vitality

Service: cvs-matrix

Environment: production

Railway CLI: v5.70.0

During our first SSH connection to ssh.railway.com, we received an ED25519 host-key verification prompt displaying:

SHA256:+S1xg92FrnHz6pY3bpKmh1OGtWQGNANXi1PzlxA7Blg

We understand from Railway's previous support responses that multiple SSH hosts are used and that fixed host-key fingerprints are not published.

Could you please clarify:

  1. What is Railway's officially recommended secure procedure for trusting the host key on the first SSH connection?
  2. Is there a supported alternative to SSH for inspecting the running container's filesystem and mounted volumes?
  3. How can we safely preserve existing uploaded files before attaching a persistent volume?

Our objective is to protect existing client floor plans and assessment data before making any storage or deployment changes.

We have not accepted the SSH host key or modified production storage.

Thank you for your guidance.

Solved

3 Replies

Railway
BOT

a month ago

We don't publish host-key fingerprints for ssh.railway.com and we can't confirm whether a specific fingerprint is ours. The endpoint is served by multiple hosts, each with its own key, and those keys change without notice, so a fingerprint that differs between connections is expected. We don't have an official procedure for host-key trust on this endpoint, so how you handle it is up to your own security policy.

For volume files, railway volume browse opens an interactive browser, and railway volume files list, download and upload work in scripts, with no SSH setup needed (docs). Those commands only work once a volume is attached. Today, files outside a volume can only be reached in the running container through SSH.

To keep the uploaded files that exist now, copy them off the running container before you change storage. scp and sftp work against ssh.railway.com, and transfers reach the container's filesystem, for example scp -r <service-domain>@ssh.railway.com:/app/uploads ./uploads (docs). After the volume is attached, you can put them back with railway volume files upload.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway

We don't publish host-key fingerprints for `ssh.railway.com` and we can't confirm whether a specific fingerprint is ours. The endpoint is served by multiple hosts, each with its own key, and those keys change without notice, so a fingerprint that differs between connections is expected. We don't have an official procedure for host-key trust on this endpoint, so how you handle it is up to your own security policy. For volume files, `railway volume browse` opens an interactive browser, and `railway volume files list`, `download` and `upload` work in scripts, with no SSH setup needed ([docs](https://docs.railway.com/volumes)). Those commands only work once a volume is attached. Today, files outside a volume can only be reached in the running container through SSH. To keep the uploaded files that exist now, copy them off the running container before you change storage. `scp` and `sftp` work against `ssh.railway.com`, and transfers reach the container's filesystem, for example `scp -r <service-domain>@ssh.railway.com:/app/uploads ./uploads` ([docs](https://docs.railway.com/cli/ssh)). After the volume is attached, you can put them back with `railway volume files upload`.

10thcosmos
OP

a month ago

Thank you for the explanation.

Before proceeding, we need human technical guidance on safely preserving our existing production uploads.

Our CVS Matrix service currently appears to have no persistent volume attached, while MySQL has its own volume.

Could a Railway engineer please confirm the safest supported procedure to:

  1. Establish secure SSH/SCP access when official host-key fingerprints are unavailable.
  2. Back up existing files from /shared-storage/public/assets/uploads/grid-maps/ without modifying the running container.
  3. Attach persistent storage and restore the files without risking data loss or unintended deployment changes.

Please also confirm whether attaching a volume to the running service triggers a redeployment or restart.

We have not changed the production storage configuration.

Thank you.


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

The cvs-matrix service in production has no volume attached, so its uploaded files live only on the container's own filesystem, and that filesystem is discarded whenever the service redeploys. That makes the order important: copy the files off first, then attach the volume, then restore them.

On host-key trust, there is no published fingerprint list and no Railway-recommended procedure. The endpoint is served by multiple hosts, each with its own key, and those keys change without notice, so how you handle first-connection trust is a decision for your own security policy. scp and sftp work against ssh.railway.com and read from the container's filesystem, so copying /shared-storage/public/assets/uploads/grid-maps/ out does not modify the running container (SSH docs).

When you attach the volume, it is made available at the mount path you choose. Once it is attached and the service is running on it, you can put the files back with railway volume files upload or check them with railway volume browse (volume docs). Redeploying a service that has a volume attached involves a short period of downtime, even with a healthcheck configured (healthcheck docs).


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...