-
Notifications
You must be signed in to change notification settings - Fork 25
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
PrivoxyVPN not forwarding port 8118 as expected #26
Comments
I've done some more investigation into this, and it seems to be because when launched in a docker swarm network, the container only binds port 8118 to IPV6 and not IPv4? For example, when deploying the container as a docker swarm service, I see the following:
And netstat only shows the container listening on IPV6:
But if I run the same commands on the container started with docker-compose I see:
And netstat shows that the container started under docker-compose is listening on BOTH IPv4 and IPv6?
|
Some more information using
|
Hi There,
Until recently privoxyVPN worked great on my Ubuntu 20.04 swarm setup. I recently upgraded to Ubuntu 22.04 and I'm not sure whether that is a factor in this but now I can't seem to contact the privoxy server on port 8118 from outside the container.
Whilst netstat reports port 8118 as listening on the node, it is not contactable outside of the container, either directly on the host node or from across the network.
(1) Running the following on the node itself (outside the container) returns results instantly with the correct (non-VPN) info:
(2) If I try to curl the same address via the privoxyvpn container, it just hangs and nothing is returned until I CTRL+C to exit the command:
curl http://ipinfo.io -x http://localhost:8118
(3) If I run the same commands (1) and (2) above but from within the privoxy container, they both return instantly with the IP details of the VPN connection/location.
Any ideas what might be going wrong here?
The text was updated successfully, but these errors were encountered: