Dynamic Forwarding tunnel not work

[haleyshi]

I am a new user and not sure whether this is an issue or just my wrong config.

Version: 2.2.2
Platform: Windows

My configuration in WindTerm:

SSH >> Tunnels
Type: Dynamic forwarding
Listen Port: 3128

My Browser's Proxy settings:

Protocol: SOCKS5
Server: 127.0.0.1
Port: 3128

The Session with Tunnel is connected, but the proxy in browser does not work from WindTerm but same/similar settings works well from other terminals.

[kingToolbox]

I guess the problem is that you checked Accept local connections only, so that WindTerm only accepts connections from localhost. Please uncheck Accept local connections only and try again. If it doesn't work, I will solve the problem again. Thank you.

[haleyshi]

Thanks and the same problem when uncheck the "Accept local connections only".

And sometimes I can see this error popped up: "SOCKS5 handshake request is invlid.".

And when the session is connected, the error (tunnel by WindTerm) is SSL connection not secure, with code ERR_SSL_PROTOCOL_ERROR.

Please notice this is an internal site and normally (e.g. tunnel from MobaXTerm or FinalShell) it should go to a warning of connection "is not private", with code "NET::ERR_CERT_AUTHORITY_INVALID", as the expected behavior when set tunnel in other terminals, and user can still choose to go ahead to ignore the warning and open the link.

When the session is not connected, it is normal that the error is "not connected".

Thanks and hope the above information could help.

[kingToolbox]

Thank you for providing such detailed screenshots and instructions.

I think there should be a problem with SOCKS 5 proxy, which is a module I wrote by myself. I will investigate this issue. Once there is progress, I will update here. Please stay tuned, thank you.

[haleyshi]

Thanks a lot for the support.

[tinyhare]

Have the same problem，and it's better to have a window to show the tunnels.

[kingToolbox]

@tinyhare
WindTerm_2.3.0_Prererelease_3?

[tinyhare]

WindTerm_2.3.1， Windows 10
Sorry , Last time I made a mistake
I use SOCKS4

It will be : SOCKS 5 handshake request is invalid (I think this should be correct )

If I use SOCKS5, the session will crash:

This is my configure:

[tinyhare]

On windows ， we can temporary use ssh command ： ssh -D 1080 user@host

[cnvic]

The same issue on 2.4 release. Is there any fix plan?

[PluieM]

the same issue on 2.4.1

[xzy256]

2.4.1 works fine.

1. create jump machine session
2. create tunnal: set dynamic forward, session(select jump session), listen port, any address can link, open it (status is active)
3. create destinate machine session, set proxy: Socks v5 proxy, ip(127.0.0.1), port. Don't set user and password

[pingod]

the same issue on windows 2.4.1
SOCKS 5 handshake request is invalid (requested version: 71).

[HiddingMan]

This problem have been solved？
I meet the same problem in 2.5.0 with firefox.
What time this problem will be solved and this feature is always uesd?
Thanks a lot for the support!
Time out, please try again.

[vomobile]

The same issue on 2.5.0 (Linux).
Open a dynamic proxy tunnel on port 1080, Chome use this socks5 proxy to browse, page shows "ERR_SSL_PROTOCOL_ERROR", and Firefox page shows "PR_END_OF_FILE_ERROR".
But the dynamic SSH Tunnel with PuTTY worked.

[awohsen]

The same is still here from windows 11, I've seen putty or OpenSSH and others ask permission from windows firewall to do this with "Accept local connections only" unmarked (perhaps it helps the process).

[fbi007130]

the issue is still recurred in v2.6.0 .

[irhuahua]

This dynamic socks5 feature, used frequently at work, wants to schedule fixes。
version：WindTerm 2.5.0

[zen010101]

2.6.0 pre-release2 : the bug is not solved .

2023/08/11 20:07:06 [Warning] [170617049] app/proxyman/outbound: failed to process outbound traffic > proxy/socks: failed to establish connection to server > common/protocol: invalid domain name: �

[kingToolbox]

WindTerm_2.7.0_Prerelease_3 fixes the bug where dynamic port forwarding couldn't proxy DNS lookups. Please download and try it. Thank you.