a month ago
When I try to SSH into my "Dragonfly Queue" service I get the error below:
Failed to connect: Your application is not running or in a unexpected state
This may happen because the service is serverless (sleeping) and has scaled to zero.
Serverless containers cannot accept SSH connections when idle.
To SSH into this service:
- Send a request to wake the service, then retry
- Or disable 'Sleep when idle' in service settings to keep it running
But the service is not set as serverless. How can I restore SSH?
5 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
It's online but it has four red alerts. They are there for a while but I can't turn them off using the Railway UI.
a month ago
No errors in logs. I restarted the deployment for internal purpose and these restarts caused these red flags to appear.
a month ago
Railway's SSH feature requires either /bin/bash or /bin/sh to exist in your container, as it doesn't use traditional SSH but rather a WebSocket-based connection that spawns a shell process. If your container doesn't have a shell available, you won't be able to SSH into it.