search

things-go / go-socks5

socks5 server in pure Golang with much custom optional. Full TCP/UDP and IPv4/IPv6 support.
MIT License
368 stars 59 forks source link

server: failed to resolve destination #24

Closed HighNetFather closed 1 year ago

HighNetFather commented 1 year ago

Hello! I ran example through docker on a virtual machine ( repo: https://github.com/garik-code/go-docker-socks5 )

Help solve the problem:

socks5: 2023/05/14 12:54:54 [E]: server: connect to [2a02:26f0:4800::215:ad91]:443 failed, dial tcp [2a02:26f0:4800::215:ad91]:443: connect: cannot assign requested address
socks5: 2023/05/14 12:54:54 [E]: server: connect to [2a01:b740:1361:2::12]:443 failed, dial tcp [2a01:b740:1361:2::12]:443: connect: cannot assign requested address
socks5: 2023/05/14 12:54:57 [E]: server: readfrom tcp 172.17.0.2:8000->185.211.159.147:17827: splice: connection reset by peer
socks5: 2023/05/14 12:55:39 [E]: server: failed to resolve destination[m.vk.com], lookup m.vk.com on 8.8.8.8:53: read udp 172.17.0.2:33536->8.8.8.8:53: i/o timeout
socks5: 2023/05/14 12:55:39 [E]: server: failed to resolve destination[m.vk.com], lookup m.vk.com on 8.8.8.8:53: read udp 172.17.0.2:33536->8.8.8.8:53: i/o timeout
socks5: 2023/05/14 12:56:21 [E]: server: failed to resolve destination[m.vk.com], lookup m.vk.com on 8.8.8.8:53: read udp 172.17.0.2:52157->8.8.8.8:53: i/o timeout
socks5: 2023/05/14 12:56:21 [E]: server: failed to resolve destination[m.vk.com], lookup m.vk.com on 8.8.8.8:53: read udp 172.17.0.2:52157->8.8.8.8:53: i/o timeout
HighNetFather commented 1 year ago

I solved the problem with the docker. It was necessary to open udp for the port