chesh

TVDB lookups are currently broken due to the migration of thetvdb.com. To temporarily fix this problem until the master branch gets the patch, follow these steps: *1st add your Github account and save in General Configuration> Advanced Settings> Github sub-section. Then go into: General Configuration> Advanced Settings> Branch Version> Select develop> Checkout Branch (will restart) Once it comes back up, TheTVDB lookups for new shows/episodes will work again, but no new artwork will be downloaded. Hopefully once both get patched in the master branch, BinHex will have compiled the new update and then you'll need to switch back to master branch in the location above and then update via your standard update procedure on the Docker page within UnRAID.

I'm now having issues connecting to rTorrent after an update today. I'm an UnRaid user that switched to this until SickRage figures out the issue w/ Deluge. Here is my log output after I deleted the image and rebuilt from template. ErrorWarningSystemArrayLogin 2017-03-10 10:28:07.479694 [info] Starting Supervisor... 2017-03-10 10:28:07,915 CRIT Set uid to user 0 2017-03-10 10:28:07,915 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing 2017-03-10 10:28:07,924 INFO supervisord started with pid 7 2017-03-10 10:28:08,927 INFO spawned: 'flood-script' with pid 119 2017-03-10 10:28:08,929 INFO spawned: 'start-script' with pid 120 2017-03-10 10:28:08,931 INFO spawned: 'rtorrent-script' with pid 121 2017-03-10 10:28:08,933 INFO spawned: 'rutorrent-script' with pid 122 2017-03-10 10:28:08,936 INFO spawned: 'privoxy-script' with pid 123 2017-03-10 10:28:08,938 DEBG 'flood-script' stdout output: [info] Flood not enabled, skipping starting Flood Web UI 2017-03-10 10:28:08,938 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,939 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,939 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,940 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,940 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-03-10 10:28:08,940 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 46963474132792 for <Subprocess at 46963474323576 with name flood-script in state RUNNING> (stdout)> 2017-03-10 10:28:08,940 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 46963474132648 for <Subprocess at 46963474323576 with name flood-script in state RUNNING> (stderr)> 2017-03-10 10:28:08,941 INFO exited: flood-script (exit status 0; expected) 2017-03-10 10:28:08,941 DEBG received SIGCLD indicating a child quit 2017-03-10 10:28:08,941 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-03-10 10:28:08,943 DEBG 'rtorrent-script' stdout output: [info] rTorrent config file already exists, skipping copy 2017-03-10 10:28:08,945 DEBG 'rtorrent-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-03-10 10:28:08,957 DEBG 'start-script' stdout output: [info] VPN default certs defined, copying to /config/openvpn/... 2017-03-10 10:28:08,964 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2017-03-10 10:28:08,967 DEBG 'start-script' stderr output: dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format... 2017-03-10 10:28:09,039 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-03-10 10:28:09,045 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2017-03-10 10:28:09,051 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2017-03-10 10:28:09,056 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2017-03-10 10:28:09,062 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2017-03-10 10:28:09,073 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2017-03-10 10:28:09,074 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-03-10 10:28:09,075 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 192.168.1.0/24 via 172.17.0.1 dev eth0 2017-03-10 10:28:09,075 DEBG 'start-script' stdout output: -------------------- 2017-03-10 10:28:09,083 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2017-03-10 10:28:09,108 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2017-03-10 10:28:09,165 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-03-10 10:28:09,166 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT -A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT -A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2017-03-10 10:28:09,166 DEBG 'start-script' stdout output: -------------------- 2017-03-10 10:28:09,167 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-03-10 10:28:09,185 DEBG 'start-script' stdout output: [info] OpenVPN started 2017-03-10 10:28:11,175 DEBG 'rtorrent-script' stdout output: [info] rTorrent not running [info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.16.10.6 different, marking for reconfigure 2017-03-10 10:28:11,176 DEBG 'privoxy-script' stdout output: [info] Configuring Privoxy... 2017-03-10 10:28:11,450 DEBG 'privoxy-script' stdout output: [info] All checks complete, starting Privoxy... 2017-03-10 10:28:11,451 DEBG 'privoxy-script' stderr output: 2017-03-10 10:28:11.451 2abda0ef0e00 Info: Privoxy version 3.0.26 2017-03-10 10:28:11.451 2abda0ef0e00 Info: Program name: /usr/bin/privoxy 2017-03-10 10:28:17,888 DEBG 'rtorrent-script' stdout output: [info] Removing any rtorrent session lock files left over from the previous run... 2017-03-10 10:28:17,892 DEBG 'rtorrent-script' stdout output: [info] Attempting to start rTorrent... 2017-03-10 10:28:17,895 DEBG 'rtorrent-script' stdout output: Script started, file is /home/nobody/typescript 2017-03-10 10:28:17,921 DEBG 'rtorrent-script' stdout output: Script done, file is /home/nobody/typescript

Know where to find SickRage's in-depth changelog? All I could seem to find was last updated in February.

So, after yesterdays update to both SickRage and Deluge, SickRage is no longer able to connect to Deluge. Both are using binhex's version of the containers. Anyone else seeing "2017-03-08 15:53:18 Thread-26 :: [41d7d9d] Request failed: No JSON object could be decoded" when SickRage tries to send a torrent over to Deluge since the update? Was hoping the Deluge container update today would have fixed the issue, but no luck. I've already tried destroying the dockers and then rebuilding them from template. Haven't gone the full nuclear option yet and blown away all dockers, docker.img file, and rebuild, but I think this is more of an API issue between programs and not the dockers themselves. Let me know if it's the software or the dockers, or my stuff is just borked. Thanks!

New update out 3 days ago. Your docker repository auto update script not working? Sickrage has had some updates out for a couple of days too. Just a head up.

Version 0.9.17.2.2159 is now available