kae

Here's the output from 2.1.1-3-02 (Docker on Windows) sh-5.1# iptables -S -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -s 181.214.206.231/32 -i eth0 -j ACCEPT -A INPUT -s 191.96.168.215/32 -i eth0 -j ACCEPT -A INPUT -s 191.96.168.218/32 -i eth0 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i wg0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -d 181.214.206.231/32 -o eth0 -j ACCEPT -A OUTPUT -d 191.96.168.215/32 -o eth0 -j ACCEPT -A OUTPUT -d 191.96.168.218/32 -o eth0 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o wg0 -j ACCEPT sh-5.1#

Echoing the ip_tables issue on the :latest branch. Switching back to 2.1.1-3-02 allowed the container to boot. This appeared in the last day or so, likely as a result of the IPV6 issue that was fixed.

Just to tie up my support -- working again. Thanks for the quick fix!

Since the latest (today) update, privoxy is failing to start. Here is the relevant log section: [info] All checks complete, starting Privoxy... 2019-05-01T21:53:29.956623500Z 2019-05-01 21:53:29,957 DEBG 'privoxy-script' stderr output: 2019-05-01 21:53:29.957 7f0eef6eb140 Info: Privoxy version 3.0.28 2019-05-01 21:53:29.957 7f0eef6eb140 Info: Program name: /usr/bin/privoxy 2019-05-01T21:53:29.957904700Z 2019-05-01 21:53:30,007 DEBG 'privoxy-script' stderr output: 2019-05-01 21:53:30.006 7f0eef6eb140 Fatal error: can't bind to 172.17.0.4 :8118: The hostname is not resolvable 2019-05-01T21:53:30.007208000Z 2019-05-01 21:53:30,007 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139932369015472 for <Subprocess at 139932368914976 with name privoxy-script in state RUNNING> (stdout)> 2019-05-01 21:53:30,007 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139932368390128 for <Subprocess at 139932368914976 with name privoxy-script in state RUNNING> (stderr)> 2019-05-01 21:53:30,008 INFO exited: privoxy-script (exit status 1; not expected) 2019-05-01 21:53:30,008 DEBG received SIGCHLD indicating a child quit 2019-05-01 21:53:30,231 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 172.98.67.33 No changes in the startup or otherwise -- it was working fine last night after the latest Docker update, right up until watchtower updated to the latest 2 hour old version. Rolling back to the build from 3 months ago resolved the problem and restored network connection.