weirdcrap

I am ok with rebuilding the array to the new disk. If it turns out the disk is ok I can still pull the contents off the disk as long as the file system is ok right? Edit: on second thought I will just turn the server off and deal with it tomorrow. I have some co-workers using plex but I will text them and let them know what is going on. Sent from my XT1096 using Tapatalk

as the title states i just received a pushbullet notification from my server saying that disk 8 of my array has had 384 read errors. looking at the log (what i can see on my mobile phone) it looks like there were also write errors, possibly being due to the device not being ready? Being that i am going to be out for at least the next four or five hours i was hoping someone in thr community could take a look at the diagnostics logs and the smart reports and let me know if i need to throw my hot spare in to the array remotely ? I have a drive plugged in that is just waiting to be swapped for the first failed disk. I am waiting for fresh smart reports to return on the disk in question and will post thrm once i have thrm. I apolgize again for the errors in spelling and grammar i am on my mobile phone. Edit: in fact it looks like it has disabled the disk and won't even let me run a smart test on it. Should I assume the disk is shot and swap it? void-diagnostics-20160616-1907.zip

You and me both... Do you have NZBToMedia.py setup and working and could give me some instructions for the TorrentToMedia.py script? CP seems to do alright the majority of the time with getting stuff moved from SAB properly but it's torrent client support is horrendous. I had posted a thread on the CP forums about issues with the CP renamer causing all kinds of annoyances with still seeding torrents and the renamer partially moving files (causing both my plex copy and the original copy to be unplayable/unseedable) and constantly re-processing movies that are still seeding because it thinks they are repacks of a release (even though they are exactly the same). The moderators suggestion was to use his TorrentToMedia.py script. Should I put the script inside the docker container or will it get wiped out anytime the docker updates? How do I tell CP to use a post-processing script for just torrent downloads? Some basic steps to get it setup would be super helpful. Mr crap... I don't use NZBmedia.py at all and was just trying to help slimer, who left before we ever got to the root of his problem, which I'm sure was to do with his config somewhere. He hasn't been online since April so you may not get much feedback on your request. Good Luck nonetheless. Love the username Yeah it is a unique name that I picked back when I was a teenager haha. I am fairly certain my CP and Deluge configurations are correct as the majority of the time I do not have issues, the renamer grabs the media and copies things correctly. However occasionally (ie this morning) it just randomly starts to repeatedly re-process the same movies over and over and over again. But anyways , could you tell me if it is safe to put the script in the docker container itself? I am assuming it will survive any updates as long as I don't actually delete and re-create the container?

You and me both... Do you have NZBToMedia.py setup and working and could give me some instructions for the TorrentToMedia.py script? CP seems to do alright the majority of the time with getting stuff moved from SAB properly but it's torrent client support is horrendous. I had posted a thread on the CP forums about issues with the CP renamer causing all kinds of annoyances with still seeding torrents and the renamer partially moving files (causing both my plex copy and the original copy to be unplayable/unseedable) and constantly re-processing movies that are still seeding because it thinks they are repacks of a release (even though they are exactly the same). The moderators suggestion was to use his TorrentToMedia.py script. Should I put the script inside the docker container or will it get wiped out anytime the docker updates? How do I tell CP to use a post-processing script for just torrent downloads? Some basic steps to get it setup would be super helpful.

I am pretty sure I installed mine through CA and didn't have any issues. I believe CA just pulls the templates from the developers repo when you request them through CA. It could have just been a bad download of the XML template?

My log 100% contains my VPN username and password right near the top and yours doesn't even seem to make a mention of VPN anywhere in the log you posted. Here is what my log looks like: http://pastebin.com/B8cLidFk Having to enter the environmental variables manually is not the expected behavior, they should all be there and just need the values filled in. Are those the only environmental variables you have? If so you are missing some important ones. Based on what your log has in it I would say that these missing environmental variables are causing the VPN component of this docker to never be started in the first place which is why you are seeing your public ip address using the ip checking torrent file. The environmental variables you should have are: VPN_ENABLED yes VPN_USER UsernameHere VPN_PASS PasswordHere VPN_REMOTE nl.privateinternetaccess.com (this is the default one but can be changed to any PIA endpoint that supports port forwarding) VPN_PROTOCOL udp VPN_PROV pia ENABLE_PRIVOXY no (if you want to use privoxy you can, I choose not to) LAN_NETWORK 192.168.10.0/24 (this should be what you have based on what your IP scheme is) DEBUG false PUID 99 PGID 100 Out of curiosity did you get this docker template directly through binhex's repository or did you get it through the CommunityApplications plugin?

Can you post your container log file and your environmental variable settings so I can make sure everything is set correctly? Also post your servers local IP and subnet so I can make sure the LAN_NETWORK variable is set correctly. Be sure to remove the VPN credentials from the container log and environment variables before posting. Where do I grab the container log? I am familiar with getting into the Docker containers I just want to make sure I grab the correct file. There are probably easier ways than this but this is the only way I have ever done it. On the docker container page turn on advanced view and find the delugevpn container id (mine is 6a153b1d55b1). In the terminal navigate to /var/lib/docker/containers and find the directory that matches the container id you found (the folder names will be longer than the container name but they should still be unique, in my case mine was: 6a153b1d55b172fd951a6c5c0c524c9737a67609bfd72e44e44a4d561e531521). In that folder there should be a LongContainerIDString-json.log file. Copy that over to somewhere that you can access from the machine you are posting from and attach it or if it won't fit pastebin it. Remember that the docker does print your VPN credentials in plain text so be sure to remove those first (they should be somewhere near the top). EDIT: Alternatively if you just started the container you should be able to get the full log from the web GUI by clicking the log icon all the way to the right of the container entry on the docker tab and copy pasting the contents of it. The web GUI only shows the last 350 lines of the log file and my container has been running for a while so my startup log info is long gone.

Can you post your container log file and your environmental variable settings so I can make sure everything is set correctly? Also post your servers local IP and subnet so I can make sure the LAN_NETWORK variable is set correctly. Be sure to remove the VPN credentials from the container log and environment variables before posting.

It should already be started, you simply need to check allow remote connections under preferences in the webui (see attachment). Then in CouchPotato this is what I have setup for deluge (see attachment). I use the IP address of UnRAID plus the port of the daemon and the user I defined in the auth file according to Q6 in the OP. I've checked all this many times. The daemon is not running. I get connection failed, which is 100% not to do with my ip or port. The auth file and details in CP are correct. Using a different version of CP gives the same issue. I am positive it is the Daemon. Can you post a copy of the container log? I believe it leaves your VPN credentials in plain text in the log so be sure to remove them.

It is possible the script wasn't properly detecting the new port assigned to you (might be related to the issues I am having with the Windows client). The link I posted a few posts back made it sound like you are dynamically given a port from the endpoint and it can change at any time.

That is using the site itself. When I view the peer list on a file I am seeding it shows my username, that I am seeding, and that I am connectable. In Deluge on Windows there is a way to test if you are connectable I believe but it is not present in this version.

Yes that is essentially the PIA linux script checking what port you have been assigned every five minutes to make sure it hasn't changed. If it has the Deluge port is updated accordingly (from what I understand of how this works). I upgraded my PIA client on the Windows machine I am trying to do some tests on and am still not having any luck with the client being able to tell me what port number I was assigned. If it eventually decides to tell me what port I have I will do some testing and see if my ports show open or closed. Maybe Binhex or some of the other users with some more experience with VPNs and bittorrent can shed some light on this (I just started using a VPN a month ago). EDIT: My Docker is seeding now and you are correct the port shows closed even when actively uploading data. EDIT2: Interestingly enough even though port utilities like the one you linked to above show my deluge port as being closed the tracker I am on is listing me as connectable.

Yes it is. According to a discussion on PIA's forums the port is only ever opened when you are actually sending data through it: https://www.privateinternetaccess.com/forum/discussion/4558/tcp-port-forwarding-not-working Do you have any torrents actively seeding (uploading data) when you are checking for connectivity? I just checked mine and it shows closed and I have no active uploads currently so AFAIK this is the expected behavior. EDIT: I am testing with a debian distro torrent on my home Windows machine and I am having issues getting the client to report what port number I have been assigned. Once I get that figured out I will do some more testing and report back whether my port shows open when I am seeding.

Did you verify that you are using a pia server that supports port forwarding? Specifically these endpoints (all outside of the US) : CA Toronto CA North York Netherlands Sweden Switzerland France Germany Russia Romania Israel Sent from my XT1096 using Tapatalk

The port that is being forwarded is randomly picked by the deluge startup script from what I can tell. It should show up in your container log when it starts and it can also be found in the Deluge preferences under Network > Incoming Ports. You also have to be sure you are using one of the PIA servers that supports port forwarding, the default one that Binhex has defined in the container (nl.privateinternetaccess.com) supports port forwarding and will work just fine.

It should already be started, you simply need to check allow remote connections under preferences in the webui (see attachment). Then in CouchPotato this is what I have setup for deluge (see attachment). I use the IP address of UnRAID plus the port of the daemon and the user I defined in the auth file according to Q6 in the OP.

Looks like the pull request was merged in Sonarr and this container autoupdates on restart so, yes it will have made it into the container as soon as you restarted after the PR was merged. Just tested it again, still the same issue. The meta file is added with the proper download directory and label, but it is not passed on to the torrent file itself. Is this something I should bring up on the sonarr forums then? The links I posted previously were the only thing I could find that sounded like the issue I am experiencing now. I was previously using deluge (as it played nice with CP, Sonarr, and Headphones without any of these issues) but I found it was more resource heavy (RAM wise) than I liked, my Plex machine is the older of my two UnRAID systems and the board only supports a maximum of 8GB (budget build lulz) and deluge was using 3GB before I stopped it.

Hey guys, I am using LinuxServer.io's Sonarr docker and BinHex's rtorrentvpn docker and I am having an issue with sonarr passing magnet links to rtorrent and the torrent not keeping the properties of the magnet link after it is removed (hope this makes sense). I did some research online and I found some info on the sonarr forums and in the issue tracker on GitHub and was wondering if anyone could tell me if this fix has been incorporated into the Sonarr docker (I am not a coder or an expert in navigating GitHub so I was hoping someone here could help). Here is the forum post that led me to the pull request on github: https://forums.sonarr.tv/t/rtorrent-magnet-not-resolved/8608/6 The forum post doesn't exactly describe the issue I am having but after reading through the whole discussion on GitHub it sounds like it was resolved with the pull requests they made. This post specifically describes the behavior I am experiencing: https://github.com/Sonarr/Sonarr/pull/1033#issuecomment-173240458 -Sonarr pushes magnet to rtorrent. -Sonarr starts magnet. -Magnet gets downloaded as meta file. -Rtorrent deletes magnet download, replaces it with a torrent download attached to the meta file. But doesn't transfer any other property. So the torrent gets the default download dir set without a label Could anyone tell me if this has made it into this docker? I am still experiencing the issue and I am a Git noob so I don't know how to check whether the pull was committed to the repository or anything like that.

It sounds like the route (I assume in iptables) that the script is trying to add is failing to add and as binhex mentioned if the VPN connection fails this docker will not download anything as a protection measure for the user so you aren't downloading anything without the protection of the VPN. Binhex: I noticed this in my logs today: Authenticate/Decrypt packet error: packet HMAC authentication failed I saw your posts in your Docker archive thread here and I am using PIA so I'm not sure what my issue is. I checked the file permissions and they are fine, the VPN tunnel is working and I can verify that my IP address is not my ISP given IP, I have looked through the log files and can't find anything out of the ordinary besides a few small warnings but they were present before this hmac issue popped up so I think they are unrelated. [info] Env var PUID defined as 99 [info] Env var PGID defined as 100 [info] Permissions already set for /config [info] Starting Supervisor... 2016-05-03 12:41:31,385 CRIT Set uid to user 0 2016-05-03 12:41:31,385 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2016-05-03 12:41:31,399 INFO supervisord started with pid 12 2016-05-03 12:41:32,401 INFO spawned: 'start-script' with pid 15 2016-05-03 12:41:32,404 INFO spawned: 'webui-script' with pid 16 2016-05-03 12:41:32,406 INFO spawned: 'deluge-script' with pid 17 2016-05-03 12:41:32,408 INFO spawned: 'privoxy-script' with pid 18 2016-05-03 12:41:32,420 DEBG 'deluge-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-05-03 12:41:32,420 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-05-03 12:41:32,420 INFO success: webui-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-05-03 12:41:32,420 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-05-03 12:41:32,420 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2016-05-03 12:41:32,421 DEBG 'privoxy-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2016-05-03 12:41:32,467 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2016-05-03 12:41:32,701 DEBG 'start-script' stdout output: [info] VPN provider defined as pia [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2016-05-03 12:41:32,746 DEBG 'start-script' stdout output: [info] Env vars defined via docker -e flags for remote host, port and protocol, writing values to ovpn file... 2016-05-03 12:41:32,777 DEBG 'start-script' stdout output: [info] VPN provider remote gateway defined as nl.privateinternetaccess.com [info] VPN provider remote port defined as 1194 [info] VPN provider remote protocol defined as udp 2016-05-03 12:41:32,789 DEBG 'start-script' stdout output: [info] VPN provider username defined as SNIP 2016-05-03 12:41:32,798 DEBG 'start-script' stdout output: [info] VPN provider password defined as SNIP 2016-05-03 12:41:32,830 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.42.1 2016-05-03 12:41:32,843 DEBG 'start-script' stdout output: [info] Setting permissions recursively on /config/openvpn... 2016-05-03 12:41:32,849 DEBG 'start-script' stdout output: [info] Adding 192.168.0.0/24 as route via docker eth0 2016-05-03 12:41:32,850 DEBG 'start-script' stdout output: [info] ip route defined as follows... 2016-05-03 12:41:32,851 DEBG 'start-script' stdout output: -------------------- 2016-05-03 12:41:32,852 DEBG 'start-script' stdout output: default via 172.17.42.1 dev eth0 2016-05-03 12:41:32,852 DEBG 'start-script' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.24 192.168.0.0/24 via 172.17.42.1 dev eth0 2016-05-03 12:41:32,852 DEBG 'start-script' stdout output: -------------------- 2016-05-03 12:41:32,860 DEBG 'start-script' stdout output: [info] iptable_mangle module not supported, attempting to load... 2016-05-03 12:41:32,861 DEBG 'start-script' stderr output: modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.1.18-unRAID 2016-05-03 12:41:32,861 DEBG 'start-script' stdout output: [warn] iptable_mangle module not supported, you will not be able to connect to Deluge webui or Privoxy outside of your LAN 2016-05-03 12:41:32,951 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2016-05-03 12:41:32,952 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 1194 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A INPUT -s 192.168.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -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 1194 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -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 2016-05-03 12:41:32,953 DEBG 'start-script' stdout output: -------------------- [info] nameservers 2016-05-03 12:41:32,954 DEBG 'start-script' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2016-05-03 12:41:32,954 DEBG 'start-script' stdout output: -------------------- [info] Starting OpenVPN... 2016-05-03 12:41:33,012 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015 Tue May 3 12:41:33 2016 library versions: OpenSSL 1.0.2f 28 Jan 2016, LZO 2.09 Tue May 3 12:41:33 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-05-03 12:41:33,041 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 UDPv4 link local: [undef] Tue May 3 12:41:33 2016 UDPv4 link remote: [AF_INET]46.166.190.236:1194 2016-05-03 12:41:33,162 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this 2016-05-03 12:41:33,562 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.190.236:1194 2016-05-03 12:41:36,195 DEBG 'start-script' stdout output: Tue May 3 12:41:36 2016 TUN/TAP device tun0 opened Tue May 3 12:41:36 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Tue May 3 12:41:36 2016 /usr/bin/ip link set dev tun0 up mtu 1500 2016-05-03 12:41:36,196 DEBG 'start-script' stdout output: Tue May 3 12:41:36 2016 /usr/bin/ip addr add dev tun0 local 10.183.1.6 peer 10.183.1.5 2016-05-03 12:41:36,205 DEBG 'start-script' stdout output: Tue May 3 12:41:36 2016 Initialization Sequence Completed 2016-05-03 12:41:36,225 DEBG 'deluge-script' stdout output: [info] First run detected, setting Deluge listening interface 10.183.1.6 2016-05-03 12:41:36,341 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2016-05-03 12:41:36,341 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47066811981624 for <Subprocess at 47066811978312 with name privoxy-script in state RUNNING> (stderr)> 2016-05-03 12:41:36,341 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47066811981192 for <Subprocess at 47066811978312 with name privoxy-script in state RUNNING> (stdout)> 2016-05-03 12:41:36,341 INFO exited: privoxy-script (exit status 0; expected) 2016-05-03 12:41:36,342 DEBG received SIGCLD indicating a child quit 2016-05-03 12:41:32,954 DEBG 'start-script' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2016-05-03 12:41:32,954 DEBG 'start-script' stdout output: -------------------- [info] Starting OpenVPN... 2016-05-03 12:41:33,012 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015 Tue May 3 12:41:33 2016 library versions: OpenSSL 1.0.2f 28 Jan 2016, LZO 2.09 Tue May 3 12:41:33 2016 WARNING: file 'credentials.conf' is group or others accessible 2016-05-03 12:41:33,041 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 UDPv4 link local: [undef] Tue May 3 12:41:33 2016 UDPv4 link remote: [AF_INET]46.166.190.236:1194 2016-05-03 12:41:33,162 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this 2016-05-03 12:41:33,562 DEBG 'start-script' stdout output: Tue May 3 12:41:33 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.190.236:1194 2016-05-03 12:41:36,195 DEBG 'start-script' stdout output: Tue May 3 12:41:36 2016 TUN/TAP device tun0 opened Tue May 3 12:41:36 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Tue May 3 12:41:36 2016 /usr/bin/ip link set dev tun0 up mtu 1500 2016-05-03 12:41:36,196 DEBG 'start-script' stdout output: Tue May 3 12:41:36 2016 /usr/bin/ip addr add dev tun0 local 10.183.1.6 peer 10.183.1.5 2016-05-03 12:41:36,205 DEBG 'start-script' stdout output: Tue May 3 12:41:36 2016 Initialization Sequence Completed 2016-05-03 12:41:36,225 DEBG 'deluge-script' stdout output: [info] First run detected, setting Deluge listening interface 10.183.1.6 2016-05-03 12:41:36,341 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2016-05-03 12:41:36,341 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47066811981624 for <Subprocess at 47066811978312 with name privoxy-script in state RUNNING> (stderr)> 2016-05-03 12:41:36,341 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47066811981192 for <Subprocess at 47066811978312 with name privoxy-script in state RUNNING> (stdout)> 2016-05-03 12:41:36,341 INFO exited: privoxy-script (exit status 0; expected) 2016-05-03 12:41:36,342 DEBG received SIGCLD indicating a child quit 2016-05-03 12:41:37,775 DEBG 'deluge-script' stdout output: [info] First run detected, setting Deluge incoming port 51366 2016-05-03 12:41:37,775 DEBG 'deluge-script' stdout output: [info] Setting listening interface for Deluge... 2016-05-03 12:41:37,786 DEBG 'deluge-script' stdout output: [info] All checks complete, starting Deluge... 2016-05-03 12:41:37,999 DEBG 'deluge-script' stdout output: [info] Setting incoming port for Deluge... 2016-05-03 12:41:39,426 DEBG 'webui-script' stdout output: [info] Starting Deluge webui... 2016-05-03 12:41:40,004 DEBG 'deluge-script' stdout output: Setting random_port to False.. Configuration value successfully updated. 2016-05-03 12:41:40,533 DEBG 'deluge-script' stdout output: Setting listen_ports to (51366, 51366).. Configuration value successfully updated. 2016-05-03 12:41:40,580 DEBG 'deluge-script' stdout output: [info] Sleeping for 5 mins before rechecking listen interface and port (port checking is for PIA only) 2016-05-03 12:41:41,866 DEBG 'webui-script' stderr output: /usr/lib/python2.7/site-packages/pkg_resources/__init__.py:1246: UserWarning: /home/nobody/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable). warnings.warn(msg, UserWarning) 2016-05-03 12:43:13,201 DEBG 'start-script' stdout output: Tue May 3 12:43:13 2016 Authenticate/Decrypt packet error: packet HMAC authentication failed 2016-05-03 12:44:14,571 DEBG 'start-script' stdout output: Tue May 3 12:44:14 2016 Authenticate/Decrypt packet error: packet HMAC authentication failed I did some googling and other people who have experienced this error say it is some kind of TLS error and mention some ways to address it but I wanted to see what you thought about the issue first. EDIT: and now it seems to have stopped. I guess it must have been one of the torrents I was downloading? EDIT2: It seems to have stopped right after this: 2016-05-03 14:14:20,784 DEBG 'webui-script' stderr output: Unhandled error in Deferred: 2016-05-03 14:14:20,890 DEBG 'webui-script' stderr output: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/twisted/protocols/policies.py", line 120, in dataReceived self.wrappedProtocol.dataReceived(data) File "/usr/lib/python2.7/site-packages/deluge/ui/client.py", line 179, in dataReceived d.callback(request[2]) File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 393, in callback self._startRunCallbacks(result) File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 588, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/usr/lib/python2.7/site-packages/deluge/ui/web/json_api.py", line 579, in _on_got_files for index, torrent_file in enumerate(files): exceptions.TypeError: 'NoneType' object is not iterable

So it is. What would be the proper way to rectify this? Just move any content out of the appdata folders under user and/or user0 into the /mnt/cache/appdata folder and delete the root appdata directories from user and user0? I must not have something set up right in UnRAID in the first place as even folders that I had explicitly created on the cache drive under /mnt/cache are showing up in the /mnt/user (or user0) folder. These are folders that I SSH into the machine and created with mkdir under /mnt/cache. Could this be because I have disk shares turned on?

Hey Squid, I am trying to setup the backup feature of CA and my appdata share isn't listed even though I triple checked that it is set to cache only (see attachment). Any ideas on what I am missing? UnRAID v6.1.9 with latest CA installed.

Ah okay, that makes sense. Would using a port forward enabled end point put me at risk of having my ip leaked? Still new to the whole VPN thing and PIA warns in their support area that "Port Forwarding reduces privacy. For maximum privacy, please keep port forwarding disabled." I seem to be able to connect to other peers just fine without actually using a forwarding enabled end point (all though it does take longer and my speeds suffer somewhat because of it).

Any thoughts?

I have noticed this running through my docker log for DelugeVPN (referring to the "Error: Invalid port specification" & the "malformed expression"): 2016-04-24 14:09:27,263 DEBG 'deluge-script' stdout output: [info] Sleeping for 5 mins before rechecking listen interface and port (port checking is for PIA only) 2016-04-24 14:14:27,270 DEBG 'deluge-script' stdout output: [info] Deluge listening interface IP 10.117.1.6 and VPN provider IP 10.117.1.6 match 2016-04-24 14:14:27,342 DEBG 'deluge-script' stderr output: Error: Invalid port specification: 2016-04-24 14:14:27,342 DEBG 'deluge-script' stdout output: [info] Deluge incoming port closed 2016-04-24 14:14:28,089 DEBG 'deluge-script' stdout output: [info] Reconfiguring for VPN provider port 2016-04-24 14:14:28,089 DEBG 'deluge-script' stdout output: [info] Setting listening interface for Deluge... 2016-04-24 14:14:28,530 DEBG 'deluge-script' stdout output: Setting listen_interface to 10.117.1.6.. Configuration value successfully updated. 2016-04-24 14:14:28,574 DEBG 'deluge-script' stdout output: [info] Setting incoming port for Deluge... 2016-04-24 14:14:29,008 DEBG 'deluge-script' stdout output: Setting random_port to False.. Configuration value successfully updated. 2016-04-24 14:14:29,478 DEBG 'deluge-script' stderr output: [ERROR ] 14:14:29 main:347 malformed expression (,) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/deluge/ui/console/main.py", line 344, in do_command ret = self._commands[cmd].handle(*args, **options.__dict__) File "/usr/lib/python2.7/site-packages/deluge/ui/console/commands/config.py", line 102, in handle return self._set_config(*args, **options) File "/usr/lib/python2.7/site-packages/deluge/ui/console/commands/config.py", line 136, in _set_config val = simple_eval(options["set"][1] + " " .join(args)) File "/usr/lib/python2.7/site-packages/deluge/ui/console/commands/config.py", line 85, in simple_eval res = atom(src.next, src.next()) File "/usr/lib/python2.7/site-packages/deluge/ui/console/commands/config.py", line 54, in atom out.append(atom(next, token)) File "/usr/lib/python2.7/site-packages/deluge/ui/console/commands/config.py", line 77, in atom raise SyntaxError("malformed expression (%s)" % token[1]) I think this might have to do with the fact that I changed the privoxy port so deluge and sabnzbd could run side by side but figured I had better check with you to be sure. Even though privoxy is disabled in sab it still appears to bind the port so deluge wouldn't start until I changed it. Is it safe to just remove the port bindings from both if I don't intend on using privoxy with either of them?

For clarification of your statement on GitHub about Privoxy: "It also includes Privoxy to allow unfiltered access to index sites." Privoxy is only necessary if your ISP is filtering access to index sites and privoxy tunnels that access through the VPN? So if I don't have any ISP filtering like that I can simply leave privoxy disabled? EDIT: Nevermind, found the explanation I was looking for in your DelugeVPN support thread. To answer my own question, yes.