-
Notifications
You must be signed in to change notification settings - Fork 53
Open
Description
I have problem whith authentication SOCKS5.
I run the server like this:
revsocks -listen :8443 -socks 94.111.11.145:9091 -pass SuperSecretPassword -tls -proxyauth user:13456789
client:
revsocks -connect 94.111.11.145:8443 -pass SuperSecretPassword -tls -proxyauth user:13456789
There is an error with SOCKS5 when connecting to 94.111.11.145:9091: Proxy requires authentication
server console:
2025/02/22 12:45:15 Starting to listen for clients
2025/02/22 12:45:15 Will start listening for clients on 94.111.11.145:9091 and agents on :8443 (TLS: true)
2025/02/22 12:45:16 No TLS certificate. Generated random one.
2025/02/22 12:45:19 [32.221.161.91:1508] Got a connection from 32.221.161.91:1508:
2025/02/22 12:45:20 [32.221.161.91:1508] Got Client from 32.221.161.91:1508
2025/02/22 12:45:20 [32.221.161.91:1508] Handshake recognized. Waiting for clients on 94.111.11.145:9091
2025/02/22 12:45:23 [32.221.161.91:1508] Got client. Opening stream for 32.221.161.91:1520
2025/02/22 12:45:23 [32.221.161.91:1508] Starting to copy conn to stream for 32.221.161.91:1520
2025/02/22 12:45:23 [32.221.161.91:1508] Starting to copy stream to conn for 32.221.161.91:1520
2025/02/22 12:45:23 [32.221.161.91:1508] Done copying conn to stream for 32.221.161.91:1520
client console:
2025/02/22 12:33:09 Using domain with user:13456789
2025/02/22 12:33:09 Connecting to the far end. Try 1 of 3
2025/02/22 12:33:09 Connecting to far end
2025/02/22 12:33:09 Starting client
2025/02/22 12:33:51 Accepting stream
2025/02/22 12:33:51 Passing off to socks5
2025/02/22 12:33:51 [ERR] socks: Failed to authenticate: No supported authentication mechanism
2025/02/22 12:33:51 Failed to authenticate: No supported authentication mechanism
Metadata
Metadata
Assignees
Labels
No labels