railway ssh: "No target found" — gateway has no SSH target for a RUNNING V2 instance

[Ecdys]

Summary

railway ssh always fails with No target found for '<id>', even though the service instance is RUNNING and the app serves production traffic normally. The SSH gateway never resolves a target for the service's runtime-V2 instance.

Environment

• CLI: railway 5.20.0
• OS: macOS (darwin)
• Plan: Hobby
• Region: europe-west4-drams3a
• Runtime: V2
• Service domain: passion-livres-production.up.railway.app

What happens

$ railway ssh -s passion-livres "echo OK"
Using SSH key from file ~/.ssh/railway_passion.pub: railway-passion
No target found for '09964cc6-9132-4bcc-ade1-6b951ef5b243'
Connection to ssh.railway.com closed by remote host.

Note: 09964cc6-… is the serviceInstance id, not a deployment-instance id.

Things I tried (all fail identically)

• Re-login, including the new ssh_keys OAuth scope (railway login --browserless)
• Confirmed SSH key is registered (railway ssh keys shows railway-passion)
• railway restart -s passion-livres
• Full railway redeploy -s passion-livres → fresh RUNNING instance
• railway ssh -s passion-livres -d <running deployment-instance id> (verified RUNNING via railway status --json) → No target found for '<that id>'
• Direct ssh <service-domain>@ssh.railway.com -i <key> → connects to ssh.railway.com then hangs and is closed by remote host

Expected

railway ssh connects to the running instance, or returns an actionable error.

Notes

Matches a Central Station thread where Railway staff said they're "tracking this across multiple reports" and asked affected users to open a CLI issue. The RUNNING instance is reachable over HTTP (the app works), so only the SSH target registration appears broken.