SSH & Remote Administration

Stop wasting time on jump host hopscotch

🧩 The Challenge

Dealing with multi-hop SSH connections where you have to manually bounce through a bastion host just to reach a private database server is a massive time sink. I’ve spent way too many nights typing the same sequence of commands into different terminals just to reach a production box.

💡 The Fix

Use the ProxyJump configuration to tunnel your connection through the jump host transparently. It turns a multi-step process into a single command that acts like you’re connecting directly to the target.

ssh -J user@jump-host:22 user@target-server:22

⚙️ Why It Works

Setting this flag tells your local SSH client to establish a connection to the first host and then open a secondary connection to the target using the first as a TCP proxy. You get the security of the jump box without the mental overhead of maintaining nested sessions.

🚀 Pro-Tip: Add a Host block in your ~/.ssh/config for the target host with the ProxyJump directive set so you can just type ssh target-server and never think about it again.

Linux Tips & Tricks | © ngelinux.com | 7/19/2026