[Support] binhex - PrivoxyVPN

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A new image has now been rolled out for all vpn enabled docker images (25th Feb 2021) i produce with the fix in place, i would encourage everyone to update to the recently created 'latest' tagged image. You can force the upgrade by toggling 'basic view' to 'advanced view' and then clicking on

Recommended by binhex

March 3Mar 3

26 minutes ago, amakleh said:
After updating to newest version I'm having problems starting up the docker. It gets stuck on "[info] Applying chown to paths '/etc/privoxy /home/nobody'..."
Full log
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2026-03-03 21:59:01.358880 [info] Host is running unRAID
2026-03-03 21:59:01.393153 [info] System information: Linux f63f64a8e7bd 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux
2026-03-03 21:59:01.444165 [info] Image architecture: 'amd64'
2026-03-03 21:59:01.481001 [info] Application name: 'privoxyvpn'
2026-03-03 21:59:01.507793 [info] Base image release tag: '2026012601'
2026-03-03 21:59:01.535600 [info] Application image release tag: '4.1.0-1-01'
2026-03-03 21:59:01.567760 [info] PUID defined as '99'
2026-03-03 21:59:01.600647 [info] User 'nobody' already has UID '99', skipping usermod
2026-03-03 21:59:01.626485 [info] PGID defined as '100'
2026-03-03 21:59:01.654569 [info] Group 'users' already has GID '100', skipping groupmod
2026-03-03 21:59:01.680195 [info] UMASK defined as '000'
2026-03-03 21:59:01.708743 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2026-03-03 21:59:01.745689 [info] Deleting files in /tmp (non recursive)...
2026-03-03 21:59:01.783134 [info] VPN_ENABLED defined as 'yes'
2026-03-03 21:59:01.814859 [info] VPN_CLIENT defined as 'wireguard'
2026-03-03 21:59:01.847386 [info] VPN_PROV defined as 'pia'
2026-03-03 21:59:01.884469 [info] VPN_CONFIG not defined (wireguard config doesnt file exists), defaulting to '/config/wireguard/wg0.conf'
2026-03-03 21:59:01.913402 [info] VPN_REMOTE_SERVER not defined (wireguard config doesnt file exists), defaulting to 'nl-amsterdam.privacy.network'
2026-03-03 21:59:01.941484 [info] VPN_REMOTE_PORT not defined (wireguard config file doesnt exists), defaulting to '1337'
2026-03-03 21:59:01.967635 [info] VPN_DEVICE_TYPE defined as 'wg0'
2026-03-03 21:59:01.997104 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2026-03-03 21:59:02.028474 [info] USERSPACE_WIREGUARD defined as 'no'
2026-03-03 21:59:02.061099 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2026-03-03 21:59:02.099491 [debug] iptables default policies available, setting policy to drop...
2026-03-03 21:59:02.132553 [debug] ip6tables default policies available, setting policy to drop...
2026-03-03 21:59:02.213407 [debug] DNS operational, we can resolve name 'nl-amsterdam.privacy.network' to address '212.56.48.14 212.56.48.28 212.56.48.36'
2026-03-03 21:59:02.273876 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '172.64.147.163 104.18.40.93'
2026-03-03 21:59:02.337412 [debug] DNS operational, we can resolve name 'piaproxy.net' to address '172.64.150.50 104.18.37.206'
2026-03-03 21:59:02.398532 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.18.159.201 104.19.240.167'
2026-03-03 21:59:02.442892 [debug] Showing name servers in '/etc/resolv.conf' before overwrite from NAME_SERVERS...
2026-03-03 21:59:02.472259 [debug] # Generated by Docker Engine.
2026-03-03 21:59:02.472300 [debug] # This file can be edited; Docker Engine will not make further changes once it
2026-03-03 21:59:02.472313 [debug] # has been modified.
2026-03-03 21:59:02.472325 [debug]
2026-03-03 21:59:02.472335 [debug] nameserver 192.168.1.1
2026-03-03 21:59:02.472345 [debug] search fritz.box
2026-03-03 21:59:02.472355 [debug]
2026-03-03 21:59:02.472365 [debug] # Based on host file: '/etc/resolv.conf' (legacy)
2026-03-03 21:59:02.472375 [debug] # Overrides: []
2026-03-03 21:59:02.507037 [debug] Showing name servers in '/etc/resolv.conf' after overwrite from NAME_SERVERS...
2026-03-03 21:59:02.535676 [debug] nameserver 1.1.1.1
2026-03-03 21:59:02.535724 [debug] nameserver 1.0.0.1
2026-03-03 21:59:02.767449 [debug] Docker interface name, Gateway interface name, Gateway IP, Docker interface IP, Subnet mask and CIDR are defined as 'eth0,eth0,172.17.0.1,172.17.0.3,255.255.0.0,172.17.0.0/16'
2026-03-03 21:59:02.860939 [info] LAN_NETWORK defined as '192.168.1.0/24,100.95.246.0/24'
2026-03-03 21:59:02.907811 [info] LAN_NETWORK exported as '192.168.1.0/24,100.95.246.0/24'
2026-03-03 21:59:02.939398 [info] VPN_USER defined as 'user'
2026-03-03 21:59:02.971447 [info] VPN_PASS defined as 'password'
2026-03-03 21:59:02.997830 [info] STRICT_PORT_FORWARD defined as 'yes'
2026-03-03 21:59:03.031129 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2026-03-03 21:59:03.063192 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2026-03-03 21:59:03.091032 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2026-03-03 21:59:03.121915 [info] ENABLE_SOCKS defined as 'yes'
2026-03-03 21:59:03.153617 [info] ENABLE_PRIVOXY defined as 'yes'
2026-03-03 21:59:03.184508 [info] SOCKS_USER defined as 'socksuser'
2026-03-03 21:59:03.214592 [info] SOCKS_PASS defined as 'sockspassword'
2026-03-03 21:59:03.243529 [info] Applying chown to paths '/etc/privoxy /home/nobody'...

same issue here

Quote

Replies 632
Views 145.3k
Created 7 yr7 yr
Last Reply Apr 3Apr 3

Popular Days

Posted Images

March 3Mar 3

19 minutes ago, thadunno said:
same issue here

47 minutes ago, amakleh said:
After updating to newest version I'm having problems starting up the docker. It gets stuck on "[info] Applying chown to paths '/etc/privoxy /home/nobody'..."
Full log
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2026-03-03 21:59:01.358880 [info] Host is running unRAID
2026-03-03 21:59:01.393153 [info] System information: Linux f63f64a8e7bd 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux
2026-03-03 21:59:01.444165 [info] Image architecture: 'amd64'
2026-03-03 21:59:01.481001 [info] Application name: 'privoxyvpn'
2026-03-03 21:59:01.507793 [info] Base image release tag: '2026012601'
2026-03-03 21:59:01.535600 [info] Application image release tag: '4.1.0-1-01'
2026-03-03 21:59:01.567760 [info] PUID defined as '99'
2026-03-03 21:59:01.600647 [info] User 'nobody' already has UID '99', skipping usermod
2026-03-03 21:59:01.626485 [info] PGID defined as '100'
2026-03-03 21:59:01.654569 [info] Group 'users' already has GID '100', skipping groupmod
2026-03-03 21:59:01.680195 [info] UMASK defined as '000'
2026-03-03 21:59:01.708743 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2026-03-03 21:59:01.745689 [info] Deleting files in /tmp (non recursive)...
2026-03-03 21:59:01.783134 [info] VPN_ENABLED defined as 'yes'
2026-03-03 21:59:01.814859 [info] VPN_CLIENT defined as 'wireguard'
2026-03-03 21:59:01.847386 [info] VPN_PROV defined as 'pia'
2026-03-03 21:59:01.884469 [info] VPN_CONFIG not defined (wireguard config doesnt file exists), defaulting to '/config/wireguard/wg0.conf'
2026-03-03 21:59:01.913402 [info] VPN_REMOTE_SERVER not defined (wireguard config doesnt file exists), defaulting to 'nl-amsterdam.privacy.network'
2026-03-03 21:59:01.941484 [info] VPN_REMOTE_PORT not defined (wireguard config file doesnt exists), defaulting to '1337'
2026-03-03 21:59:01.967635 [info] VPN_DEVICE_TYPE defined as 'wg0'
2026-03-03 21:59:01.997104 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2026-03-03 21:59:02.028474 [info] USERSPACE_WIREGUARD defined as 'no'
2026-03-03 21:59:02.061099 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2026-03-03 21:59:02.099491 [debug] iptables default policies available, setting policy to drop...
2026-03-03 21:59:02.132553 [debug] ip6tables default policies available, setting policy to drop...
2026-03-03 21:59:02.213407 [debug] DNS operational, we can resolve name 'nl-amsterdam.privacy.network' to address '212.56.48.14 212.56.48.28 212.56.48.36'
2026-03-03 21:59:02.273876 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '172.64.147.163 104.18.40.93'
2026-03-03 21:59:02.337412 [debug] DNS operational, we can resolve name 'piaproxy.net' to address '172.64.150.50 104.18.37.206'
2026-03-03 21:59:02.398532 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.18.159.201 104.19.240.167'
2026-03-03 21:59:02.442892 [debug] Showing name servers in '/etc/resolv.conf' before overwrite from NAME_SERVERS...
2026-03-03 21:59:02.472259 [debug] # Generated by Docker Engine.
2026-03-03 21:59:02.472300 [debug] # This file can be edited; Docker Engine will not make further changes once it
2026-03-03 21:59:02.472313 [debug] # has been modified.
2026-03-03 21:59:02.472325 [debug]
2026-03-03 21:59:02.472335 [debug] nameserver 192.168.1.1
2026-03-03 21:59:02.472345 [debug] search fritz.box
2026-03-03 21:59:02.472355 [debug]
2026-03-03 21:59:02.472365 [debug] # Based on host file: '/etc/resolv.conf' (legacy)
2026-03-03 21:59:02.472375 [debug] # Overrides: []
2026-03-03 21:59:02.507037 [debug] Showing name servers in '/etc/resolv.conf' after overwrite from NAME_SERVERS...
2026-03-03 21:59:02.535676 [debug] nameserver 1.1.1.1
2026-03-03 21:59:02.535724 [debug] nameserver 1.0.0.1
2026-03-03 21:59:02.767449 [debug] Docker interface name, Gateway interface name, Gateway IP, Docker interface IP, Subnet mask and CIDR are defined as 'eth0,eth0,172.17.0.1,172.17.0.3,255.255.0.0,172.17.0.0/16'
2026-03-03 21:59:02.860939 [info] LAN_NETWORK defined as '192.168.1.0/24,100.95.246.0/24'
2026-03-03 21:59:02.907811 [info] LAN_NETWORK exported as '192.168.1.0/24,100.95.246.0/24'
2026-03-03 21:59:02.939398 [info] VPN_USER defined as 'user'
2026-03-03 21:59:02.971447 [info] VPN_PASS defined as 'password'
2026-03-03 21:59:02.997830 [info] STRICT_PORT_FORWARD defined as 'yes'
2026-03-03 21:59:03.031129 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2026-03-03 21:59:03.063192 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2026-03-03 21:59:03.091032 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2026-03-03 21:59:03.121915 [info] ENABLE_SOCKS defined as 'yes'
2026-03-03 21:59:03.153617 [info] ENABLE_PRIVOXY defined as 'yes'
2026-03-03 21:59:03.184508 [info] SOCKS_USER defined as 'socksuser'
2026-03-03 21:59:03.214592 [info] SOCKS_PASS defined as 'sockspassword'
2026-03-03 21:59:03.243529 [info] Applying chown to paths '/etc/privoxy /home/nobody'...

Same issue here

Quote

March 4Mar 4

same here, had to revert to ghcr.io/binhex/arch-privoxyvpn:4.0.0-1-01 manually

Quote

March 4Mar 4

Author

13 hours ago, amakleh said:
After updating to newest version I'm having problems starting up the docker. It gets stuck on "[info] Applying chown to paths '/etc/privoxy /home/nobody'..."
Full log
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/
2026-03-03 21:59:01.358880 [info] Host is running unRAID
2026-03-03 21:59:01.393153 [info] System information: Linux f63f64a8e7bd 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux
2026-03-03 21:59:01.444165 [info] Image architecture: 'amd64'
2026-03-03 21:59:01.481001 [info] Application name: 'privoxyvpn'
2026-03-03 21:59:01.507793 [info] Base image release tag: '2026012601'
2026-03-03 21:59:01.535600 [info] Application image release tag: '4.1.0-1-01'
2026-03-03 21:59:01.567760 [info] PUID defined as '99'
2026-03-03 21:59:01.600647 [info] User 'nobody' already has UID '99', skipping usermod
2026-03-03 21:59:01.626485 [info] PGID defined as '100'
2026-03-03 21:59:01.654569 [info] Group 'users' already has GID '100', skipping groupmod
2026-03-03 21:59:01.680195 [info] UMASK defined as '000'
2026-03-03 21:59:01.708743 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'
2026-03-03 21:59:01.745689 [info] Deleting files in /tmp (non recursive)...
2026-03-03 21:59:01.783134 [info] VPN_ENABLED defined as 'yes'
2026-03-03 21:59:01.814859 [info] VPN_CLIENT defined as 'wireguard'
2026-03-03 21:59:01.847386 [info] VPN_PROV defined as 'pia'
2026-03-03 21:59:01.884469 [info] VPN_CONFIG not defined (wireguard config doesnt file exists), defaulting to '/config/wireguard/wg0.conf'
2026-03-03 21:59:01.913402 [info] VPN_REMOTE_SERVER not defined (wireguard config doesnt file exists), defaulting to 'nl-amsterdam.privacy.network'
2026-03-03 21:59:01.941484 [info] VPN_REMOTE_PORT not defined (wireguard config file doesnt exists), defaulting to '1337'
2026-03-03 21:59:01.967635 [info] VPN_DEVICE_TYPE defined as 'wg0'
2026-03-03 21:59:01.997104 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2026-03-03 21:59:02.028474 [info] USERSPACE_WIREGUARD defined as 'no'
2026-03-03 21:59:02.061099 [info] NAME_SERVERS defined as '1.1.1.1,1.0.0.1'
2026-03-03 21:59:02.099491 [debug] iptables default policies available, setting policy to drop...
2026-03-03 21:59:02.132553 [debug] ip6tables default policies available, setting policy to drop...
2026-03-03 21:59:02.213407 [debug] DNS operational, we can resolve name 'nl-amsterdam.privacy.network' to address '212.56.48.14 212.56.48.28 212.56.48.36'
2026-03-03 21:59:02.273876 [debug] DNS operational, we can resolve name 'www.privateinternetaccess.com' to address '172.64.147.163 104.18.40.93'
2026-03-03 21:59:02.337412 [debug] DNS operational, we can resolve name 'piaproxy.net' to address '172.64.150.50 104.18.37.206'
2026-03-03 21:59:02.398532 [debug] DNS operational, we can resolve name 'serverlist.piaservers.net' to address '104.18.159.201 104.19.240.167'
2026-03-03 21:59:02.442892 [debug] Showing name servers in '/etc/resolv.conf' before overwrite from NAME_SERVERS...
2026-03-03 21:59:02.472259 [debug] # Generated by Docker Engine.
2026-03-03 21:59:02.472300 [debug] # This file can be edited; Docker Engine will not make further changes once it
2026-03-03 21:59:02.472313 [debug] # has been modified.
2026-03-03 21:59:02.472325 [debug]
2026-03-03 21:59:02.472335 [debug] nameserver 192.168.1.1
2026-03-03 21:59:02.472345 [debug] search fritz.box
2026-03-03 21:59:02.472355 [debug]
2026-03-03 21:59:02.472365 [debug] # Based on host file: '/etc/resolv.conf' (legacy)
2026-03-03 21:59:02.472375 [debug] # Overrides: []
2026-03-03 21:59:02.507037 [debug] Showing name servers in '/etc/resolv.conf' after overwrite from NAME_SERVERS...
2026-03-03 21:59:02.535676 [debug] nameserver 1.1.1.1
2026-03-03 21:59:02.535724 [debug] nameserver 1.0.0.1
2026-03-03 21:59:02.767449 [debug] Docker interface name, Gateway interface name, Gateway IP, Docker interface IP, Subnet mask and CIDR are defined as 'eth0,eth0,172.17.0.1,172.17.0.3,255.255.0.0,172.17.0.0/16'
2026-03-03 21:59:02.860939 [info] LAN_NETWORK defined as '192.168.1.0/24,100.95.246.0/24'
2026-03-03 21:59:02.907811 [info] LAN_NETWORK exported as '192.168.1.0/24,100.95.246.0/24'
2026-03-03 21:59:02.939398 [info] VPN_USER defined as 'user'
2026-03-03 21:59:02.971447 [info] VPN_PASS defined as 'password'
2026-03-03 21:59:02.997830 [info] STRICT_PORT_FORWARD defined as 'yes'
2026-03-03 21:59:03.031129 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2026-03-03 21:59:03.063192 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2026-03-03 21:59:03.091032 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2026-03-03 21:59:03.121915 [info] ENABLE_SOCKS defined as 'yes'
2026-03-03 21:59:03.153617 [info] ENABLE_PRIVOXY defined as 'yes'
2026-03-03 21:59:03.184508 [info] SOCKS_USER defined as 'socksuser'
2026-03-03 21:59:03.214592 [info] SOCKS_PASS defined as 'sockspassword'
2026-03-03 21:59:03.243529 [info] Applying chown to paths '/etc/privoxy /home/nobody'...

12 hours ago, thadunno said:
same issue here

12 hours ago, Sic79 said:
Same issue here

1 hour ago, lukad said:
same here, had to revert to ghcr.io/binhex/arch-privoxyvpn:4.0.0-1-01 manually

Issue resolved, please pull down the latest image.

Quote

March 4Mar 4

that has definitely fixed it, thanks for the speedy fix! although now the logs aren't letting me know what the incoming port that's been assigned is. it's letting me know that it's successfully assigned one, but that's it.

Quote

March 5Mar 5

Wierd, seems like the DNS is not resolving for me anymore. if i revert to 4.0.0-1-01 it works again. Anyone else have this with the new version?

Edit: Ok, false alarm. Seems like the docker can resolve dns but not my clients connecting through the docker. Will troubleshoot some more

Edit 2: Solved, it works now, I had to get a new wireguard config to get it working again. Wierd that it worked in the older version though

Edited March 5Mar 5 by Sic79

Quote

4 weeks later...

April 1Apr 1

On 3/4/2026 at 12:49 PM, thadunno said:
that has definitely fixed it, thanks for the speedy fix! although now the logs aren't letting me know what the incoming port that's been assigned is. it's letting me know that it's successfully assigned one, but that's it.

I encountered the same issue earlier in the week. Digging around this morning I found if you open the Console for the binhex-privoxyvpn Docker Container and type "cat /tmp/getvpnport" it will show the incoming port.

Quote

April 3Apr 3

On 4/1/2026 at 11:31 AM, Firejack said:
I encountered the same issue earlier in the week. Digging around this morning I found if you open the Console for the binhex-privoxyvpn Docker Container and type "cat /tmp/getvpnport" it will show the incoming port.

thanks man, this works!

Edited April 3Apr 3 by thadunno

Quote

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Followers

Go to topic listing

Replies 632
Views 145.3k
Created 7 yr7 yr
Last Reply Apr 3Apr 3

[Support] binhex - PrivoxyVPN

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

IceNine451

binhex

binhex

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

IceNine451

binhex

binhex

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)