-
Notifications
You must be signed in to change notification settings - Fork 38
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.
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
Proxy times out when connecting over LAN #6
Comments
Same issue here, have you figured it out? |
The problem (at least in my setup) was, the docker network MTU, you can set it inside a compose file (or globally in docker) checkout my fork where I have an example on how to fix it. |
Am also having the same issue... Scratching my head for few hours now... Tried the network with lower mtu, but didn't help... Is it working for someone ?? |
try change the internal ip inside the sockd.conf, you can bind to a ip(0.0.0.0) instead of interface(eth0), i will Provider more info when i got time. check this Lozy/danted#18 (comment) (not tested btw) |
Hi Koin, |
It also works for me! Much Thanks. |
I'm having trouble using the proxy over my local network. When I run the command
curl --socks5 127.0.0.1:1080 https://api.ipify.org
from the computer running the container I get the expected result, but if I run
curl --socks5 192.168.0.28:1080 https://api.ipify.org
from that computer or another on the same network it times out after about a minute with this error:
curl: (28) Failed to connect to 192.168.0.28 port 1080: Connection timed out
The port is open but it appears to leave connections hanging when they come through the machine's LAN IP address.
The text was updated successfully, but these errors were encountered: