SFTP timeout when accessing Railway volume
watrado
HOBBYOP

4 hours ago

Hello Railway Support,

I need to create a read-only backup of an existing Railway volume without restarting its sleeping service.

Project: MutationX OS Isolated 20261012

Environment: isolated-acceptance

Service: mutationx-isolated-control-plane

Volume: mutationx-isolated-evidence-only

CLI: 5.67.1, running on PythonAnywhere Linux.

Railway login, project linking, and SSH key registration succeeded. The SSH endpoint on port 22 returned a valid SSH banner.

However, two attempts to list the volume files failed:

Failed to initialize SFTP session

Caused by: Timeout

The temporary SSH key was revoked and the CLI session was logged out. The volume has no existing backups.

Please advise how to safely export this volume without restarting the service, deploying changes, or modifying existing data.

Thank you.

$10 Bounty

2 Replies

Status changed to Awaiting Railway Response Railway • about 4 hours ago


Railway
BOT

4 hours ago

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

Status changed to Open Railway • about 4 hours ago


an hour ago

You need active/running deployment to be able to access the volume files, you have to wake your service up from sleeping state and run the CLI again. There's no way to access files while your service is in the sleeping state


gamerc0der
PRO

8 minutes ago

Railway volume file commands and SFTP connections require an active deployment to access files (from my experince), which should be why your requests timed out where the service is sleeping. To safely export your data, without modifying "mutationx-isolated-control-plane', you can create a temp throwaway service (to be deleted later) and attach the existing volume and deploy without an active running program that may modify it. This allows you to create a backup and get a continuous SFTP/CLI volume export commands. Then once downloaded, you can simply delete this new throwaway service, cleaning up your env.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...