Skip to content

Clarify Railway SSH command boundaries#1160

Closed
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-ssh-port-forwarding
Closed

Clarify Railway SSH command boundaries#1160
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-ssh-port-forwarding

Conversation

@radiantjade
Copy link
Copy Markdown
Contributor

@radiantjade radiantjade commented May 15, 2026

Summary

  • clarify that railway ssh targets the selected running service instance, independent of whether the service came from a repository or Docker image
  • document that arguments after -- run inside the remote container and are not forwarded as local OpenSSH flags
  • point database/tunnel-style use cases toward railway connect or TCP proxy instead of railway ssh -- -L ...

Related Central Station question: https://station.railway.com/questions/railway-ssh-fails-with-unauthorized-imme-4e1737f8

Verification

  • git diff --check
  • pnpm exec content-collections build

The CLI accepts a remote command after --, but those arguments are not local OpenSSH options. Document that distinction so users do not expect railway ssh -- -L ... -N to create a local port-forward, and clarify that SSH targets the running service instance rather than a specific source type.

Constraint: Central Station question asks whether railway ssh supports image-based services and local tunnel flags
Rejected: Add CLI port-forwarding support | broader behavior change outside this docs bounty-sized fix
Confidence: medium
Scope-risk: narrow
Directive: Keep this doc aligned with src/commands/ssh/native.rs argument ordering in the CLI
Tested: git diff --check; pnpm exec content-collections build
Not-tested: live Railway SSH session
@brody192 brody192 closed this May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants