14 days ago
We use Railway's standard deployed-service SSH/SFTP endpoint,ssh.railway.com,
with a registered SSH key and an exact deployment-instance ID. This concerns
ordinary service containers,not Cloud Agents,Sandboxes or tmux sessions.
Our finite job exports encrypted evidence,then exits. Railway reports the exact
replica EXITED and deploymentStopped=true. The client closes its SSH processes.
A later single SFTP handshake failed,but we are not treating that as proof of
server-side revocation. No remote file-content read was attempted in that check.
Could you confirm:
-
Does client disconnect/EOF terminate every server-side SFTP channel/resource
for that connection? Is there any durable/resumable SFTP session after it?
-
When the exact service replica becomes EXITED,what happens to an already-open
SFTP channel,including open file handles and mounted-volume access?
-
Does removing a registered SSH key terminate existing authenticated SSH/SFTP
connections,or only prevent new authentication? What propagation bound applies?
-
Is there an API/control to enumerate and revoke sessions for an exact replica
or key,and an authoritative audit event/readback proving completion?
-
If no such API exists,what supported teardown procedure guarantees this
boundary without deleting the persistent volume or retained evidence?
Please distinguish documented guarantees from current implementation behavior.
We have not removed the key,restarted the job or deleted any evidence.
1 Reply
Status changed to Awaiting Railway Response Railway • 14 days ago
14 days ago
These are the guarantees we can stand behind. Railway SSH connects your system ssh, scp and sftp clients to the running container you target by domain, service instance ID or deployment instance ID, and transfers reach that container's filesystem, including any mounted volume. Registered keys can be listed and removed with railway ssh keys (or --workspace for workspace keys, which grant access to every service in the workspace). The only reconnect-and-reattach behavior we offer is the opt-in tmux mode (railway ssh --session), and plain SFTP connections don't use it.
We can't give you a guarantee on the rest. That covers server-side cleanup of SFTP channels after a client EOF, what happens to an open channel or file handle when the replica exits, whether removing a key ends connections that are already authenticated, or how long that takes to apply. We haven't verified current behavior for any of these points, so please don't treat either answer as confirmed.
We offer no customer-facing API or control to list or revoke active SSH/SFTP sessions for a replica or a key. We also can't point you to an audit event that records a session closing.
Removing the registered key reliably stops that key from authenticating new connections. It doesn't touch your volume or the evidence on it.
Status changed to Awaiting User Response Railway • 14 days ago
7 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 • 7 days ago