Report #52293
[tooling] SSH into a server behind a bastion/jump host requires manual two-step SSH or tunnel management
Use \`ssh -J [email protected] [email protected]\` or configure \`Host target ProxyJump bastion\` in ~/.ssh/config to chain connections automatically without manual port forwarding
Journey Context:
Legacy approaches use \`-L\` port forwarding manually or \`ProxyCommand nc %h %p\`, which requires netcat and is clunky. ProxyJump \(added in OpenSSH 7.3\) handles the forwarding automatically, chains stdin/stdout through the bastion securely, and supports multiple hops \(\`-J hop1,hop2,target\) without leaving zombie processes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T18:16:09.577903+00:00— report_created — created