nowhere

So I haven't seen any comment on my statement about the main config file for privoxy in the appdata share for the container. Reading the privoxy manual it says that in order for privoxy to listen on the lan, I have to change the listen address in the main config file, which the docs define as just "config". The file is there but is zero sized, with no contents. I simply added the line listen-address XXX.XXX.XXX.XXX:8118 where the IP address is the docker container address and it seems to work now. So I suspect my container is corrupt somehow, having an empty config file. Or is this normal and I missed a config step somewhere? Thanks for the help so far!

The only things I can think of is either the iptables of the unraid server or the container. Unfortunately, I don't know enough about them to find anything subtle. I included them from my unraid server in my first post...

Hey thanks strike for helping out. I've tried an extension in chrome and setting the system proxy directly and I've tried setting the proxy in firefox as well as setting Sickrage in a docker on the same unraid machine as the binhex-delugevpn docker. I've also tried setting the proxy env variable in a shell and trying to ping. Nothing can connect. supervisord.log

Thanks but I can't connect from regular browsers either. I went ahead and tried just in case, to add the http:// in the sickrage proxy field but no luck connecting. The log didn't change either... 2017-10-18 18:25:39 INFO CHECKVERSION :: Request failed: HTTPConnectionPool(host=u'192.168.0.101', port=8118): Max retries exceeded with url: http://sickrage.github.io/sickrage-news/news.md (Caused by ProxyError('Cannot connect to proxy.', error(104, 'Connection reset by peer'))) 2017-10-18 18:25:39 WARNING MAIN :: Updating network timezones failed, this can happen from time to time. URL: http://sickrage.github.io/sb_network_timezones/network_timezones.txt 2017-10-18 18:25:39 INFO MAIN :: Request failed: HTTPConnectionPool(host=u'192.168.0.101', port=8118): Max retries exceeded with url: http://sickrage.github.io/sb_network_timezones/network_timezones.txt (Caused by ProxyError('Cannot connect to proxy.', error(104, 'Connection reset by peer')))

Unraid server is 192.168.0.101 and LAN_NETWORK is 192.168.0.0/24

Thanks binhex, but all that I know how to do. The problem is that once all that is done, I get a connection refused error message when pointing a browser's proxy settings on another machine to the unraid server's IP 192.168.0.101:8118. Here's the error message from SickRage in a docker on the same machine as the delugevpn docker: 017-10-17 19:53:54 INFO SEARCHQUEUE-DAILY-SEARCH :: [Rarbg] :: Request failed: HTTPConnectionPool(host=u'192.168.0.101', port=8118): Max retries exceeded with url: http://torrentapi.org/pubapi_v2.php?get_token=get_token&app_id=sickrage2&format=json (Caused by ProxyError('Cannot connect to proxy.', error(104, 'Connection reset by peer'))) my iptables on the browser machine is clear (but it shouldn't matter because I can't connect from other dockers on the same unraid server): ~$ sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination the iptables on the unraid machine are here. I'm not expert enough to determine if they are right but I did not set them. Installing dockers and virtual machines is what must have set them. ~# sudo iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 ctstate RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable DOCKER-ISOLATION all -- anywhere anywhere DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:bootpc Chain DOCKER (1 references) target prot opt source destination ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:8081 ACCEPT tcp -- anywhere 172.17.0.4 tcp dpt:sip ACCEPT tcp -- anywhere 172.17.0.5 tcp dpt:8989 ACCEPT tcp -- anywhere 172.17.0.6 tcp dpt:9117 ACCEPT tcp -- anywhere 172.17.0.3 tcp dpt:58846 ACCEPT tcp -- anywhere 172.17.0.3 tcp dpt:8118 ACCEPT tcp -- anywhere 172.17.0.3 tcp dpt:8112 Chain DOCKER-ISOLATION (1 references) target prot opt source destination RETURN all -- anywhere anywhere searching TCP in wireshark while trying to surf thru the proxy in chrome I see some chatter repeated over and over, highlighted in red 378 12.061765503 192.168.0.101 192.168.0.175 TCP 60 8118 → 34970 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0

I'm hoping someone can help me out. I have delugevpn installed and it works fine for downloading torrents. I can access the web interface for deluge and apps can push torrents through the webui. I cannot, however, get Privoxy to work. I set up chrome to use the proxy at 192.168.0.101:8118 and it errors with no internet connection. If I try to use curl to grab my IP addess it gets connection refused: curl ipinfo.io/ip curl: (7) Failed to connect to 192.168.0.101 port 8118: Connection refused I disabled Privoxy on this container, installed binhex's sabnzbvp and configured it to port 8119 with all the same results. I have no rules set in my client computer's iptables (running Ubuntu 16.04) and there's no errors in the delugevpn logs. I did notice that the privoxy config file in the container's folder is empty. /mnt/user/appdata/binhex-delugevpn/privoxy# ls -la total 164 drwxr-xr-x 1 nobody users 156 Oct 15 22:21 ./ drwxrwxr-x 1 nobody users 4096 Oct 15 22:21 ../ -rwxr-xr-x 1 nobody users 0 Oct 15 22:21 config* -rwxr-xr-x 1 nobody users 91347 Nov 6 2016 default.action* -rwxr-xr-x 1 nobody users 40438 Nov 6 2016 default.filter* -rwxr-xr-x 1 nobody users 627 Nov 6 2016 match-all.action* drwxr-xr-x 1 nobody users 4096 Nov 6 2016 templates/ -rwxr-xr-x 1 nobody users 3761 Nov 6 2016 trust* -rwxr-xr-x 1 nobody users 8794 Nov 6 2016 user.action* -rwxr-xr-x 1 nobody users 3334 Nov 6 2016 user.filter* I have intermediate networking skills. How do I find out what's blocking access to the proxy server? THANKS!

From their description in community apps:

I've been using this docker for some time without issue but I've recently been trying to use Privoxy and I'm unable to get it working. My unraid server IP is 192.168.0.101 and I'm able to connect to all the docker webui's fine thru their various ports. I've checked the IP the torrents see and it's the VPN IP as expected. When I set my proxy to point to 192.168.0.101:8118 (with or without http://) in chrome or firefox I get a proxy connection failed error. I tried SwitchOmega also to no avail. I don't see any errors in the supervisord.log and it looks like Privoxy is starting fine, though I don't see the port 8118 anywhere in the log file. I would have expected something highlighting that it's open for the proxy. Edit: Oh yeah, I don't have any other privoxy enabled dockers running (like sabnzbvpn etc)... Chrome Error: There is no Internet connection There is something wrong with the proxy server, or the address is incorrect. Try: Contacting the system admin Checking the proxy address ERR_PROXY_CONNECTION_FAILED I don't know what else to check. Any ideas/help? THANKS! supervisord.log