SSH & Remote Administration

Stop manually typing hostnames for your nested SSH jumps

🧩 The Challenge

Dealing with a jump host to reach your database server is annoying enough, but manually chaining SSH commands makes me feel like I’m back in 2005. I’ve wasted so much time fat-fingering multi-hop connection strings while trying to get a tunnel open.

💡 The Fix

You can tell your local SSH client to automatically proxy connections through a jump host using a simple configuration directive. It makes your remote servers feel like they’re sitting right on your local network.

Host internal-db
ProxyJump user@gateway-server
HostName 10.0.5.22
User dbadmin

⚙️ Why It Works

By setting the ProxyJump directive in your ~/.ssh/config file, SSH handles the TCP forwarding behind the scenes before it ever tries to auth against the target. It’s way cleaner than messy -oProxyCommand hacks we used to rely on.

🚀 Pro-Tip: Add the -v flag to your connection once if it hangs, so you can actually see where the proxy handshake is dying.

Linux Tips & Tricks | © ngelinux.com | 10/29/2026