Skip to content
Railway Console Disconnects Despite Successful Deployment
observerdawn-a11y
OP

a month ago

Hello Railway Community,

I'm experiencing an issue with the interactive console for a Railway-hosted Node.js API service.

The deployment shows ACTIVE/SUCCESS, but when I try to open the console, it briefly displays "Connecting" and then changes to "Disconnected" without providing a shell prompt.

On another attempt, the console displayed "No running instances", even though the service dashboard indicated that the deployment was online.

What I've checked:

  • Deployment status is successful.
  • One replica is configured.
  • Recent CPU and memory usage are well below the configured limits.
  • Application startup completed successfully.
  • No obvious crash or out-of-memory errors were found in the available logs.
  • Actual running-instance availability has not been independently confirmed.

Could someone help clarify:

  1. What can cause the Railway console to disconnect despite a successful deployment?
  2. How can I safely verify whether an instance is currently running?
  3. Could this be a console-session or instance-discovery issue?
  4. Is there a supported, read-only alternative for inspecting the existing running container without restarting or redeploying it?

I'm specifically looking for diagnostic guidance that does not require modifying the running service.

Thank you!

Solved

1 Reply

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


Railway
BOT

a month ago

Your API services show their latest deployments as successful, and a successful deployment status alone doesn't confirm that the web console can reach a running instance.

For a read-only check that doesn't restart or redeploy anything, you can use the CLI. railway logs --service <name> --environment <env> --deployment streams the current deployment's runtime logs, and railway logs --lines 100 returns the most recent entries. railway ssh --service <name> --environment <env> opens a shell in the existing running container over a separate connection from the dashboard console. If more than one instance exists, --deployment-instance <id> lets you target a specific one. Running railway ssh does not restart or redeploy the service, and if it fails to connect, the error it returns will show whether an instance is actually reachable.


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


Railway
BOT

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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...