You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically, that works when localhost is removed from the ::1 abbreviation in /etc/hosts hence making localhost to resolve to 127.0.0.1 on the server. Otherwise the application is mapped on ::1:<port> and thus can't be proxied over the ssh tunnel.
Having IPv6 configured on the Windows 11 desktop won't help.
Yes, its a hack to remove ipv6 localhost, but I need to get the node.js app to send data via ipv4 .
It seams if ipv4 & ipv6 is ipv6 is prioritized over ipv4.
But with ipv6 localhost in /etc/hosts, ONLY the connection is established, logging server will show website data, but NO ACTUAL data is passed through the tunnel when its connect.
I don't quite understand the issue, are you trying to set up a forwarded port with ipv6 after connecting, and that isn't working? If that's it, I see microsoft/vscode-remote-release#7029
Does this issue occur when all extensions are disabled?:
Yes, ssh tunnel was connected with putty. Microsoft Windows said its not their fault.
Steps to Reproduce:
SSH will connect, tunnel is established.
localhost:port is not receiving any data, as if ::1:port to localhost:port is the issue
The same with ipv4 works.
The text was updated successfully, but these errors were encountered: