SSH & Remote Administration

Stop manually forwarding ports for every single service

🧩 The Challenge

Setting up a half-dozen local port forwards in your SSH config file is a pain, and forgetting which port maps to which internal service is even worse. I spent years editing that file every time I needed to debug a different container.

💡 The Fix

Use SSH’s dynamic port forwarding feature to turn your machine into a SOCKS proxy, then configure your browser or tools to use that proxy directly. It beats managing a mess of static mappings.

ssh -D 8080 -N -f user@your-jump-host

⚙️ Why It Works

By opening a SOCKS proxy, your local machine tunnels all traffic through the remote host, letting you reach internal network resources as if you were sitting right next to them. You don’t need to define a new tunnel for every new port you encounter.

🚀 Pro-Tip: Use the FoxyProxy extension in your browser to toggle this on and off based on URL patterns so you aren’t routing your Netflix traffic through a server in another timezone.

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