[zeta0134]

The WebUI port forwards can be made a bit more tolerable by using LocalForward in your ~/.ssh/config [1] assuming you're okay with the forwards being set up every time you log in. I agree that it's still clunky though; in-terminal tooling is generally preferable.

[1]: https://linux.die.net/man/5/ssh_config

[jek0]

I tried that in a different context... The problem if you're managing many servers is that you'll have to setup a different local port for each server. When I needed it, I had to go check the .ssh/config each time to figure out which port was bound for this server. Did not save any time.

[mdaniel]

FWIW `DynamicForward` turns on a SOCKS5 proxy, so a dedicated Firefox profile[0] that has its proxy set to the dynamic forward port will be able to browse as if running on the remote machine. I believe remote DNS resolution, works, too. It still could clash ports if you have the same DynamicForward port for multiple ssh configs, but it can drastically reduce the number of port-collisions

0 = you are of course welcome to try running Chrome with `--proxy-server` et al, but I find Firefox a ton easier to use in that situation