Timeline for Unable to Connect to VNC Server Using SSH Tunnel
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2018 at 3:18 | comment | added | insideman | Yes, sorry the second 'l' was a typo. I did use a lower case 'l' when I tried it. It seems there is indeed some sort of cool down mechanism when I establish a connection through an ssh tunnel. I just tried my original command 'ssh -L 5901:127.0.0.1:5901 -N -f -l user server-ip' and can connect to 'localhost:5901' using a vnc viewer. I guess my question then is, how do I speed up this process. My solution is functional, but it can be inconvenient at times to wait 1+ hour to be able to connect using a different instance. | |
| Jun 12, 2018 at 15:18 | comment | added | Krzysztof Sawicki |
Look at parameters you've used: -L means "listen on port and forward to port", -l (small letter L) means "login". Command, you have executed has second -L instead of -l. Also, IMHO, it's simplier to use syntax user@host than -l user host.
|
|
| Jun 12, 2018 at 15:15 | comment | added | insideman | ssh -L 15901:127.0.0.1:5901 -N -f -L user server_address also gives an error, but it is slightly different: debug1: Local connections to LOCALHOST:15901 forwarded to remote address 127.0.0.1:5901 debug1: Local forwarding listening on 127.0.0.1 port 15901. debug1: channel 0: new [port listener] debug1: Local forwarding listening on ::1 port 15901. bind: Cannot assign requested address debug1: Requesting [email protected] debug1: forking to background debug1: Entering interactive session. debug1: pledge: network ipv6 issue here? | |
| Jun 12, 2018 at 14:57 | history | answered | Krzysztof Sawicki | CC BY-SA 4.0 |