a month ago
Railway CLI v5.63.1 returned exit 1 during volume files list at 2026-10-14 11:35:16.886–11:35:41.683 UTC: Failed to list / after reconnect / Failed to initialize SFTP session / Timeout. The deployment had completed earlier; a prior status snapshot showed its instance EXITED, but that snapshot predates the request and may not explain it. Does the supported volume-file route work against a completed deployment in this state? Is this a known v5.63.1 issue, and what is the smallest supported read-only diagnostic or next step? No restart or retry has been made.
1 Reply
a month ago
The railway volume files commands don't read the volume directly. They reach it through the service the volume is attached to, in the selected environment, and that service needs an active deployment.
We checked the latest deployment of the service that has a volume in that environment. It finished its deploy steps on 2026-10-14 at 10:59 UTC, and its only instance still reads as exited now, not just in your earlier snapshot. So the file commands have no running instance to connect through, which fits the SFTP setup timing out. A retry against the same state is not likely to behave differently.
We have no evidence that this is a problem specific to CLI v5.63.1. For a read-only check, look at that deployment's runtime logs and metrics in the dashboard to see when and why the process exited. If the worker is meant to run once and stop, file access through the CLI only works while an instance is running.
Status changed to Awaiting User Response Railway • about 1 month ago
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