I'm using the 'Remote - SSH' extension.
Suppose I set up static forwarding in my local ~/.ssh/config:
Host my_remote
HostName my_remote.com
User mike
ForwardAgent yes
LocalForward 3000 1.2.3.4:3000
So port 3000 is statically forwarded to port 3000.
Now if I output a link http://localhost:3000 to the terminal (from within the remote), when this link is 'Command + Clicked', vscode opens http://localhost:3001 in the browser - the wrong port, because it's auto-forwarded to the next available port.
It feels like if static forwarding for this port is already set up, it could always infer that no auto port forwarding is needed and hence open in the browser at port 3000.
The setting "remote.autoForwardPorts": false, does not help in this case.
Thanks :)
I'm using the 'Remote - SSH' extension.
Suppose I set up static forwarding in my local
~/.ssh/config:So port 3000 is statically forwarded to port 3000.
Now if I output a link
http://localhost:3000to the terminal (from within the remote), when this link is 'Command + Clicked', vscode openshttp://localhost:3001in the browser - the wrong port, because it's auto-forwarded to the next available port.It feels like if static forwarding for this port is already set up, it could always infer that no auto port forwarding is needed and hence open in the browser at port 3000.
The setting
"remote.autoForwardPorts": false,does not help in this case.Thanks :)