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

I'm running delugevpn in another docker and I'd like to point this sickrage docker to use the proxy. Is that possible? I'm obviously not a networking expert and didn't see a config setting. Thanks! Update: I see that this is not configured at the docker level but inside the sickrage webui setting. On General/Advanced there's a place for the proxy URL. Turns out my Privoxy on the delugevpn isn't working. Traffic is blocked or something for some reason. When I try to use the proxy from a browser on the same network, I have no internet connection, so it's a totally different problem and this isn't the place to ask.

@strike Thanks for the reply. I'm not real familiar with Docker and the implications of having software running in a container. Is it OK to update sickrage inside the Docker container on my unraid server? What happens when an updated container is available? THANKS for helping the noob! UPDATE: HAHA I clicked the update link at the top, thinking I would lead to a dialog page, wizard or something but it updated right away and seems to be working again. As for what happens when the container is updated, we'll just see when it happens heh. Thanks to whomever fixed and is working on this awesome package!

Since 3/11, my Sickrage container can no longer snatch any torrent files. It seems to find torrent files OK and publishes in the log that they are downloading but they never get sent to DelugeVPN and they never show as snatched in History. Clicking the manual search button on an episode it's missed since this weekend pushes this into the log: 19:37:21 INFO::SEARCHQUEUE-MANUAL-311787 :: Beginning manual search for: [24 Legacy - S01E07 - 600 P.M. - 700 P.M] 19:37:21 INFO::SEARCHQUEUE-MANUAL-311787 :: [ThePirateBay] :: Performing episode search for 24: Legacy 19:37:22 INFO::SEARCHQUEUE-MANUAL-311787 :: [ThePirateBay] :: Quality of 24.Legacy.S01E07.WEB-DL.XviD-FUM[ettv] is SDTV 19:37:22 INFO::SEARCHQUEUE-MANUAL-311787 :: [ThePirateBay] :: Release: 24.Legacy.S01E07.WEB-DL.XviD-FUM[ettv] doesn't contain any of x264, ignoring it 19:37:22 INFO::SEARCHQUEUE-MANUAL-311787 :: [ThePirateBay] :: Quality of 24.Legacy.S01E07.HDTV.x264-SVA is SDTV 19:37:22 INFO::SEARCHQUEUE-MANUAL-311787 :: [ThePirateBay] :: Quality of 24.Legacy.S01E07.480p.168mb.hdtv.x264-][.600.P.M..-.700..mp4 is SDTV 19:37:22 INFO::SEARCHQUEUE-MANUAL-311787 :: Downloading 24.Legacy.S01E07.HDTV.x264-SVA from ThePirateBay But the episode returns immediately to Wanted status. This happens to everything I try to download. I only see one error in the log which I doubt is the problem: 19:23:52 ERROR::Thread-15 :: [edc61ac] Missing time zone for network: CBS All Access. Check valid network is set in indexer (theTVDB) before filing issue. Any help? THX!

I have the same question I'm assume that VM has some sort of host folder sharing but it's not in the GUI that I saw... Thanks!

Could you supply the run command of the sickrage container after you add the shared path? If sickrage works before you add the volume, it might sound like you might have specified an existing path in the container. If that is done, the folder inside the container is wiped (not really, but the content will not be available). Here's the command line (personal data xxxx'ed out): root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="sickrage" --net="bridge" -e TZ="America/Phoenix" -e HOST_OS="unRAID" -e "PGID"="100" -e "PUID"="99" -p 8081:8081/tcp -v "/mnt/user/data/xxxxxxx/torrent/complete/":"/downloads":rw -v "/mnt/user/data/xxxxxxxx/sickrage/":"/tv":rw -v "/mnt/user/data/xxxxxxxx/torrent/watch/":"/watch":rw -v "/mnt/user/appdata/sickrage":"/config":rw linuxserver/sickrage UPDATE: The only way I knew of off hand to get the start command was to go to the unraid sickrage settings page and change something and hit done. I put a space after something and deleted it and hit done and sickrage restarted. Now I can access the webgui for sickrage again. Very odd. I changed something else and hit done and it won't connect again. UPDATE 2: I believe I was simply being too impatient. I watched the unraid logs of the starting of the Sickrage container and there's a long pause at one of the steps (about 2 minutes or so). After this point the log stabilizes and I have access to Sickrage WebUI.

I installed sickrage and configured it fine using it's webui, had it download a couple TV shows but there's two problems. 1. When it added the torrents to binhex-delugevpn via remote access, deluge doesn't follow it's move to completed folder rules, while it does so perfectly if I add torrents manually. 2. If you modify the container settings (such as to add a shared watch folder to use blackhole torrent adding instead), when the sickrage container restarts you can no longer access the webui. The log fills very quickly with tons of this message: python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory I could never get the webui to respond so I had to nuke the container and start over. Even then it didn't respond so I removed it again, manually rm -rf the sickrage app folder, reinstalled and it still didn't respond. I turned of Privoxy on the binhex-delugevpn and it started working, but as soon as I got to adding a new path (the watch folder) it all started again. Let me know if I'm doing something wrong or there's a fix. Tomorrow I'm nuking the whole thing again and trying binhex's version... Thanks for the great work. It's an amazing product!