4 months ago
MongoDB service is completely down — Railway dashboard shows 'Unable to connect via SSH / WebSocket error'. The service has been in this state for over an hour. We
▎ have production patient data that we cannot lose. We need urgent recovery or volume restoration. Service: MongoDB, Proxy:
▎ viaduct.proxy.rlwy.net:27959
3 Replies
4 months ago
Your MongoDB volume is in a healthy state with your data intact (~489 MB used of 5 GB). The "Unable to connect via SSH / WebSocket error" in the dashboard typically indicates a container-level issue, not data loss. To resolve this, open your MongoDB service, press Cmd/Ctrl+K to open the command palette, and select "Redeploy source image" - this re-pulls a fresh container image and usually fixes this class of issue (a normal redeploy from the menu won't work here, it must be "Redeploy source image").
Status changed to Awaiting User Response Railway • 4 months ago
Railway
Your MongoDB volume is in a healthy state with your data intact (~489 MB used of 5 GB). The "Unable to connect via SSH / WebSocket error" in the dashboard typically indicates a container-level issue, not data loss. To resolve this, open your MongoDB service, press Cmd/Ctrl+K to open the command palette, and select "Redeploy source image" - this re-pulls a fresh container image and usually fixes this class of issue (a normal redeploy from the menu won't work here, it must be "Redeploy source image").
4 months ago
dind't work
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 4 months ago
4 months ago
i already resolved.
Status changed to Solved funcadicol • 4 months ago