Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem with using socks5 in clients #206

Open
BEST8OY opened this issue Aug 18, 2024 · 1 comment
Open

Problem with using socks5 in clients #206

BEST8OY opened this issue Aug 18, 2024 · 1 comment

Comments

@BEST8OY
Copy link

BEST8OY commented Aug 18, 2024

@markpash
Nekobox TUN mode in linux logs

ERROR[0003] [2301711958 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0003] [1004609657 300ms] outbound/socks[proxy]: outbound connection to 91.108.56.184:443
INFO[0003] [2504692538 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0003] [2504692538 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0003] [2504692538 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
INFO[0003] [341439530 300ms] outbound/socks[proxy]: outbound connection to 149.154.167.91:443
ERROR[0003] [2504692538 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0003] [3479612992 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0003] [3479612992 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0003] [2355086406 300ms] outbound/socks[proxy]: outbound connection to 149.154.167.41:443
INFO[0003] [3479612992 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
INFO[0003] [1993183425 300ms] outbound/socks[proxy]: outbound connection to 149.154.167.50:443
ERROR[0003] [3479612992 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0003] [4004895702 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0003] [4004895702 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0003] [4004895702 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0003] [4004895702 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0003] [1995031615 300ms] outbound/socks[proxy]: outbound connection to 149.154.175.59:443
INFO[0003] [3593485883 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0003] [3593485883 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0003] [495069709 300ms] outbound/socks[proxy]: outbound connection to 149.154.175.54:443
INFO[0003] [3593485883 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0003] [3593485883 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0003] [1992460739 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0003] [1992460739 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0003] [1992460739 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0003] [1992460739 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0003] [3361466633 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0003] [3361466633 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0003] [3361466633 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0003] [3361466633 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0004] [100619651 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0004] [100619651 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0004] [100619651 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0004] [100619651 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0004] [4169937732 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0004] [4169937732 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0004] [4169937732 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0004] [4169937732 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0004] [1652516340 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:56730
INFO[0004] [3739259051 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:41034
INFO[0004] [3739259051 0ms] inbound/tun[tun-in]: inbound connection to 91.108.56.184:443
INFO[0004] [3200796673 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:46980
INFO[0004] [1652516340 0ms] inbound/tun[tun-in]: inbound connection to 149.154.167.50:443
INFO[0004] [3200796673 0ms] inbound/tun[tun-in]: inbound connection to 149.154.167.41:443
INFO[0004] [1596800032 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:45330
INFO[0004] [1596800032 0ms] inbound/tun[tun-in]: inbound connection to 91.108.56.184:80
INFO[0004] [1596800032 0ms] outbound/socks[proxy]: outbound connection to 91.108.56.184:80
INFO[0004] [1744287845 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:34486
INFO[0004] [1744287845 0ms] inbound/tun[tun-in]: inbound connection to 149.154.167.50:80
INFO[0004] [1744287845 0ms] outbound/socks[proxy]: outbound connection to 149.154.167.50:80
INFO[0004] [2993322812 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0004] [2993322812 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0004] [2993322812 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
INFO[0004] [3959814748 0ms] inbound/tun[tun-in]: inbound connection from 172.19.0.1:55822
INFO[0004] [3959814748 0ms] inbound/tun[tun-in]: inbound connection to 149.154.167.41:80
INFO[0004] [3959814748 0ms] outbound/socks[proxy]: outbound connection to 149.154.167.41:80
ERROR[0004] [2993322812 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0004] [2000321370 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0004] [2000321370 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0004] [2000321370 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843
ERROR[0004] [2000321370 0ms] inbound/tun[tun-in]: socks5: request rejected, code=4
INFO[0004] [2459429512 0ms] inbound/tun[tun-in]: inbound packet connection from 172.19.0.1:46984
INFO[0004] [2459429512 0ms] inbound/tun[tun-in]: inbound packet connection to 188.114.98.57:1843
INFO[0004] [2459429512 0ms] outbound/socks[proxy]: outbound packet connection to 188.114.98.57:1843

Warp-plus logs - Nekobox on linux and Nekoray on android

time=2024-08-19T02:54:45.211+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.262+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.332+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.335+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.337+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.337+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.338+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.372+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.408+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.631+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.631+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.632+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.635+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.636+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:45.934+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.178+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.192+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.332+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.333+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.335+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.339+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.646+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:46.933+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:47.262+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:47.333+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:47.337+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"
time=2024-08-19T02:54:47.337+03:30 level=ERROR msg="connect to 188.114.98.57:1843 failed: listen udp 188.114.98.57:1843: bind: cannot assign requested address"

Warp-plus logs - V2rayNG on android

time=2024-08-18T23:28:57.236Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.276Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.350Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.370Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.547Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.572Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.655Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.690Z level=ERROR msg="no supported authentication mechanism"
time=2024-08-18T23:28:57.827Z level=ERROR msg="no supported authentication mechanism"
@BEST8OY
Copy link
Author

BEST8OY commented Aug 19, 2024

This is a problem with these apps VPN mode.
No problem with proxy mode.
Is this the normal behavior of warp-plus? Why?
@markpash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BEST8OY