2twisty

IIIIIIInteresstingggg.. I noticed in the log that it complained that the VPN endpoint I had chosen did not support port forwarding. It still connected but just issued a warning about download speeds. So, I tried changing it to one of the ones listed in the log that DO support it, and POOF. Container starts with VPN and WebGUI comes up. So, I guess using an endpoint that supports port forwarding needs to be listed as a requirement rather than just a warning? NOTE: Previously I had tried other end points with the same failure result, but none of them were on the list of port forwarding endpoints either.

Well, turning the VPN off sure simplified that log! Basicially, it says "OK listening on port 8080 now." supervisord.log

ok. Here's supervisord.log. I looked through it and it looks like this may be something to do with it, since goes through all 12 retries several times in the log and never has success. I'll try grabbing a log with the VPN turned off to see if there is an obvious change in the logs, but I admit that log chasing isn't my strongest suit. 2019-09-15 12:50:47,822 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 12 retries left [info] Retrying in 10 secs... supervisord.log

Anybody have any suggestions for me on this? I REALLY need to get the VPN going since I am on Spectrum and don't want to get any nastygrams.

There are some great tutorials on YouTube by SpaceInvader1, that will help you understand in general hoiw to set up docker and UnRAID. You definitely dont want your data going in the /config folder. Check his stuff out. It helped me a lot when I was new to UnRAID.

Additional note: tried rebooting server, as well to clean out RAM and any stuck ports, etc. No dice. Same behavior.

SYNOPSIS: Web GUI won't load when VPN enabled I've read through this entire thread, and some have had a similar problem, but not exactly. I have installed this container with all the defaults and put the certs and ovpn file in the openvpn folder. I know my PIA account is working since I can log into the web site and also connect via the Windows client. There are no other containers using any of the ports that qbittorrentvpn is using. When I have the VPN enabled in the container, the container will start, but the web GUI refuses to connect. If I disable the VPN, Web GUI works fine. Uninstalled and reinstalled and even removed the folder from appdata to be sure there were no leftovers. When I uninstalled, I deleted the image. NOTE: I still have binhex-deluge installed, but it doesn't share any ports. I am transitioning to a VPN downloader which is why i chose the qbittorrent one so that I could use my non-VPN deluge client concurrently until its downloads complete. What information can I provide to help troubleshoot this?

OK, apparently, Radarr can still add items to Deluge, but the "connection test" fails. Honestly, at that point, it doesn't matter now that I have a Deluge 2.0 client (I run Linux Mint so I don't have the "windows" problem that others do. I'll go back to the other threads and edit them.

After a recent update to Deluge v2 (my binhex-deluge container auto updated), neither binhex-radarr nor binhex-sonarr can connect to it. When I test the connection, I get "authentication error" and I have changed no passwords. What additional information can I provide to allow you to help me with this? Right now, I can't add any new torrents to Deluge. Unraid 6.6.7. (crossposted in binhex-radarr and binhex-deluge support threads)

EDIT: Found help with the Radarr/Sonarr issues here: Binhex-Sonarr support thread After a recent update to Deluge v2 (my binhex-deluge container auto updated), neither binhex-radarr nor binhex-sonarr can connect to it. When I test the connection, I get "authentication error" and I have changed no passwords. What additional information can I provide to allow you to help me with this? Right now, I can't add any new torrents to Deluge. Unraid 6.6.7.

EDIT: Found help with the Radarr/Sonarr issues listed below here: Binhex-Sonarr Support Thread Looks like Deluge did get upgraded to v2. After upgrading the thin client, I can now connect, but I still can't get Radarr and Sonarr to talk to it. I am using the binhex versions of both radarr and sonarr. They don't report that any updates are available. Any idea where to go with this next? I'll check the support threads for those containers, as well.

Just today, my remote Deluge client started to refuse to connect to my docker. The Auth file still has the proper passwords in it. I checked Radarr and Sonarr and they too can no longer connect. When I test the connection in Radarr/Sonarr, I get "authentication failed." I am able to see my active torrents via the web interface from UnRAID, so I know that the daemon is still running and operating, and that the password is still recognized. Thinking that some config got corrupted, I stopped the container, renamed the config directory and removed the container, deleting the image. I downloaded a fresh copy. I changed no settings in the docker setup except the location of the /data directory, and made no config changes in either the web interface or via the terminal. So, this container is totally default. I still have the same problem. Neither my Deluge client nor Radarr/Sonarr can connect using the default "deluge" password. Same "authentication error." Have there been any recent changes to the container that might explain this? My torrents are crippled right now until I can get this working. What additional information do you need to allow you to help me figure this out? Still on UnRAID 6.6.7

TOPIC: Running this docker on a static IP and changing the listen address to port 80. I would like to be able to use DNS to resolve my dockers on separate IPs. So instead of http://rrl-nas.contoso.com:7878/ for radarr, I'd like a clean URL of http://radarr.contoso.com/ I thought I had this figured out when playing with OwnCloud, but I don't have the whole picture. Nothing I try seems to move the listen port from 7878 to 80. I tried settings in the UnRAID Docker UI as well as googling and trying to directly modify the config.v2.json file to change the exported port from 7878 to 80. Nothing works. What am I doing wrong?

Is there a way from the UNRaid UI to force a complete re-download of all the FS layers?

I'm having issues with both the linuxserver Radarr docker AND the Sonarr docker. Both of them claim to be unable to reach my deluge docker. If I install binhex/Radarr, it can connect. But I don't want to reconfigure Radarr in Binhex. I'd like to repair the linuxserver versions if I can. Any ideas? This just started this morning with both clients -- no updates applied. It just plain broke. Here's my log file. Full of errors. radarr.txt