Squnkraid

I fixed it! To clarify and hopefully help someone else; What I ended up doing after updating DelugeVPN to :latest is this: - Edit DelugeVPN container and add all container ports that are running through DelugeVPN under "VPN_INPUT_PORTS" - To let those containers communicate with each other again, you need to change the local IP's in the respective settings of those containers (WebUI) to "localhost" That's pretty straight forward. WebUI is accessible and the containers can communicate with each other again. Problem was, for me at least, that SABnzbd is NOT running through the DelugeVPN. So Sonarr etc. were unable to connect to SAB. I have SABnzbd's WebUI set to port 8282 (Unifi already claimed 8080). Before the DelugeVPN update all other containers were connecting to SAB using "local lan IP:8282". That was no longer working. Q&A 27 in https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md So editing DelugeVPN again and added port 8282 under "VPN_OUTPUT_PORTS". In Sonarr I tested it again, but I still couldn't connect with SAB. Only when using Local Lan IP it took some processing time, but eventually returned an error. Also tried localhost, but no luck. SABnzbd also uses port 9090 so I thought maybe that would work. I added 9090 to "VPN_OUTPUT_PORTS", but still no luck inside Sonarr. Nothing worked. But then I noticed that SAB uses port 8080 (opposed to 8282) when using the container IP. So I added 8080 to "VPN_OUTPUT_PORTS" in DelugeVPN and used the "container IP:8080" inside Sonarr and BINGO! Container IP AND port 8080 gave a successful connection! Already tried to download a NZB and it works like a charm again. @binhex Maybe I'm misreading Q&A 27, but as far as I can tell the container IP is not mentioned. Perhaps you could add that? Because it looks like that is the only way to get this to work. And thanks for the hard work!

The following containers are routed through DelugeVPN (set this all up following Spaceinvader One's video's) - Sonarr, - Radarr, - Jackett, - NZBHydra Their ports are listed under VPN_INPUT_PORTS. I changed the server IP's to 'localhost' in settings and they can all communicate with each other and are accessible. No problem there. SABnzbd is outside the VPN connection. It uses port 8282. I have that port listed in DelugeVPN under VPN_OUTPUT_PORTS. But when I try to connect to it within Sonarr etc. it doesn't work. I have local server IP filled in, but also checked 'localhost' and 'container IP', it all comes back with an error. So not sure what I'm doing wrong here. I checked the Q&A section and all is setup like it should, I think. I'm probably overlooking something, but I don't know what.

Really appreciate it. The :latest images contains both VPN_INPUT_PORTS and VPN_OUTPUT_PORTS so I used those. I added all the containers using Delugevpn to VPN_INPUT_PORTS and they all became accessible again! And they can communicate with each other too. But SABnzbd is running outside the Delugevpn container (no need for VPN) and I can't get Sonarr,Radarr and NZBHydra to communicate with SABnzbd. I re-ran every step and the only thing I'm not sure about is the Proxy Settings Sonarr > Settings > General > Proxy Settings - Use Proxy = Yes - Proxy Type = HTTP(S) - Hostname = ip of server / localhost (tried both) - Port = 8118 - Username = "empty" - Password = "empty" - Addres for the proxy to ignore = ip of server / 192.168.*.* (wildcard for LAN) (tried both) This doesn't work? Privoxy is on in DelugeVPN container. After some searching I found this: https://github.com/binhex/arch-delugevpn/issues/257 and I'm guessing that's the problem? Looking at my Delugevpn container logs I seem to be running into the same issue (again, running ":latest") 2021-03-06 00:55:11,052 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-06 00:55:11,053 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-06 00:55:12,057 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-06 00:55:12,061 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-03-06 00:55:42,099 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-06 00:55:42,100 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-06 00:55:42,099 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-03-06 00:55:42,100 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-06 00:55:43,106 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-03-06 00:55:43,116 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 It looks to be crashing and restarting every 30 seconds. Am I missing something in the setup or is this indeed a bug? If so, please let me know if you need me to follow these steps to give you the info you need: https://github.com/binhex/documentation/blob/master/docker/faq/help.md EDIT: I tried removing the Privoxy folder in Appdata and restarting the container, but that didn't help.

I'm on :latest, but I don't have an 'ADDITIONAL_PORTS' option? What gives? I mean, Q24 says: "Edit 'ADDITIONAL_PORTS' env var and put applications Web UI port number in the 'value', if multiple ports required then use a comma to separate." On a side note - this is kind of hell for a newb Unraid user tbh. I'm new to Unraid and I'm in hour 4 trying to get this fixed, but I'm just going deeper down the rabbit hole. After finding this topic I changed the localhost and additional ports etc. But Sonarr (connecting to Delugevpn) couldn't connect to Sabnzbd (outside VPN network). Nothing was working. Finally decided to roll back but accidentally put a "~" in front of the version to pull. This resulted in a deleted Delugevpn container... First time for everything, right... Re-installing it, restoring appdata, nothing gave me back my previous setup. Appdata was intact, but the container was just not showing any of my old settings. No idea which search terms I needed to use to get this to work again so I decided for now to setup Delugevpn from the ground up (rewatching Spaceinvader's video) and find out later what I did wrong when restoring the backup. I followed the steps in de Q&A section, but like I said, now I don't see any "additional_ports" option is there. Kind of frustrating. Bouncing of the walls while falling to the bottom haha.