25 days ago
railway ssh --service API
Using SSH key:
🔍 No target found for '8811e921-9a1b-4131-bb10-135f76822c23'
Connection to ssh.railway.com closed by remote host.
Connection to ssh.railway.com closed.
9 Replies
25 days ago
Your API service exists in two environments: in production its latest deployment is successful, but in test it is currently sleeping. The "No target found" error from SSH means there is no running container instance to connect to. If your CLI is linked to the test environment, that would explain this, since sleeping services have no active container. Please confirm which environment your CLI is linked to by running railway status, and if it's the test environment, either switch to production with railway environment or wake the test service by sending it a request first. You can also try specifying the environment explicitly: railway ssh --service API --environment production.
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
railway ssh --service API --environment production
Using SSH key:
🔍 No target found for '8811e921-9a1b-4131-bb10-135f76822c23'
Connection to ssh.railway.com closed by remote host.
Connection to ssh.railway.com closed.
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
railway 4.59.0
Status changed to Awaiting Railway Response Railway • 25 days ago
23 days ago
Any update on this please?
21 days ago
We're having the same issue. I've upgraded my Railway CLI, linked to the correct project, environment and service, tried using -d with the correct deployment instance, tried plain bash ssh <service domain>@ssh.railway.com - all of these result in:
🔍 No target found for '2ccbd870-c3b0-4207-bd93-c606ea78d172'
Specify a service domain as the SSH username to connect
$> ssh example.up.railway.app@ssh.railway.com
Connection to ssh.railway.com closed by remote host.
Connection to ssh.railway.com closed.
Status changed to Awaiting User Response Railway • 18 days ago
enai-app
We're having the same issue. I've upgraded my Railway CLI, linked to the correct project, environment and service, tried using `-d` with the correct deployment instance, tried plain bash `ssh <service domain>@ssh.railway.com` - all of these result in: ``` 🔍 No target found for '2ccbd870-c3b0-4207-bd93-c606ea78d172' Specify a service domain as the SSH username to connect $> ssh example.up.railway.app@ssh.railway.com Connection to ssh.railway.com closed by remote host. Connection to ssh.railway.com closed. ```
14 days ago
Same Issue here
Status changed to Awaiting Railway Response Railway • 14 days ago
13 days ago
We're tracking this across multiple reports. If you haven't already, please add your details (CLI version, OS, service domain) to the GitHub issue on https://github.com/railwayapp/cli so the team has visibility into all affected cases.
Status changed to Awaiting User Response Railway • 13 days ago
Status changed to Solved mykal • 13 days ago
