Herman Terds

Does anybody know why suddenly Sab is getting these "API missing" errors? (see img below) All of my various *darr tools and NZBhydra2 are working great and have the correct API, including the SABconnect chrome extension. Haven't changed anything that I know of. And I'm not a networking expert (or an Unraid expert) but I believe 172.17.0.1 is the main network interface set up by Unraid, correct? Does that mean some diagnostic tool in Unraid is trying to access Sab or something outside of Unraid? I have heard that security apps will sometimes scan web apps like Sab and cause this error. I know I can turn off this warning but I'd love to figure out what is going on. Note that the screenshot below was taken immediately after rebooting Unraid. I seem to get one or two of these every single day at 9:00 am.

I'm also unable to use "localhost" in Sonarr/Radarr/etc. Setting them to the app IP of 172.17.x.x works. I'm also still having DNS leaks with a Firefox proxy pointing at DelugeVPN as detailed here. Everything, including DelugeVPN, is set to Network type = Bridge in the container settings. Sonarr, Radarr, NZBHydra2, Jackett, etc., are all using HTTP proxy with 172.17.x.x:8118 and "bypass local network" turned on. This may be the wrong way to use DelugeVPN with other containers, I'm not sure. I'm also now getting this in my log over and over, even though everything seems to be working if you ignore the DNS leak. 2021-02-25 17:25:10,431 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2021-02-25 17:25:10,432 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2021-02-25 17:25:10,433 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-02-25 17:25:11,444 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-02-25 17:25:11,449 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2021-02-25 17:25:11,449 DEBG 'watchdog-script' stdout output: [debug] VPN IP is XXXXXX [debug] Deluge IP is XXXXXX 2021-02-25 17:25:41,451 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2021-02-25 17:25:41,481 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.1.4' 2021-02-25 17:25:41,482 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2021-02-25 17:25:41,490 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2021-02-25 17:25:41,502 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-02-25 17:25:41,503 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... <repeat forever>

Hey Binhex, I also wanted to thank you for this docker and helping me get Mullvad and wireguard working a few months ago. I haven't noticed any real problems but I ran into what appears to be a DNS leak when using Firefox through delugevpn/privoxy. I had been fiddling around with my ports/endpoint on the Mullvad website and I noticed for the first time that they had a "privacy checker" tool. Their tool shows both my VPN DNS and my NextDNS IPs. Previously, I had run the dnsleaktest.com and only seen my Mullvad DNS. I have Firefox set to DISable DNS over HTTPS, as recommended, but even if I enable it and point it directly at the Mullvad DNS, the checker still shows my NextDNS address alongside it. I have the Mullvad DNS as the only entry for both the "Container Variable: NAME_SERVERS" and in wg0.conf. The weird thing is that when I use the Mullvad wireguard Win10 tool, there are no DNS leaks. So there's something I'm doing wrong in my setup. I installed NextDNS on my Edgerouter-X as the default DNS using the NextDNS install script (https://nextdns.io/install) and I have all their install options enabled like "instant refresh" and "cache responses." Even with those options turned off, I still get DNS leaks with delugevpn/privoxy. Leaking to NextDNS isn't the end of the world but I'd like to understand why it's happening. If you or anyone has any guesses, I'd love to hear them. I've done a lot of searching on the NextDNS and Ubiquiti forums and haven't seen anyone with quite this exact problem or any solutions.

Ah. Well, like I said, no idea what I'm doing. OK so my parameters are now: --privileged=true --sysctl="net.ipv4.conf.all.src_valid_mark=1" and I just removed the port forwarding rule. Everything seems to be working. IPleak looks fine. I think seeding is working, downloaded ubuntu to check and it looks like I'm uploading. The reason I opened the ports before was because a tracker started throwing alerts that my ports were blocked. But it may have just been some lag from bringing Deluge up and down or I was still monkeying with Mullvad port settings. I've been up for 20 minutes or so now and although I'm not seeing any seeding with this particular tracker, I'm also not getting any blocked port messages either. Probably just zero peers to seed.

I think I might have everything working now with Mullvad/Wireguard although I don't seem to be seeding in Deluge but I can't tell if it's a problem or not. Might need to double check my Mullvad port setup. No obvious errors at least. IPleak.net tests look good, just no IPv6. My extra parameters are: --privileged=true --sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl="net.ipv4.conf.all.src_valid_mark=1" My wg0 is completely vanilla. I just dragged and dropped the Mullvad one in and didn't edit it at all. It's got the DNS line and it looks like the docker parameters take the ",::0/0" off of the AllowedIPs line automatically, as far as I can tell. But like I said, I don't really know what I'm doing. EDIT: I think seeding is working fine now. It was a router issue. Forgot change the port forwarding.

I did a little more screwing around. I really don't know what I'm doing but from referencing this thread: https://forum.armbian.com/topic/4861-wireguard-on-armbian-tinkerboard/ , if I delete ", ::/0" from "AllowedIPs = 0.0.0.0/0" in wg0.conf, I can avoid "Error: Rule family not supported." and get to "[info] WireGuard interface 'up' " But I still get connection refused for the Deluge web interface and proxy connections.

I'm also unable to get Mullvad wireguard to work. My log looks identical to Lucict's. Adding "--sysctl net.ipv6.conf.all.disable_ipv6=0" to parameters got rid of "RTNETLINK Permission denied." But I have the same resolvconf issue. Deleting the DNS line from wg0.conf gives me this: 2020-10-12 16:54:26,444 DEBG 'start-script' stderr output: Error: Rule family not supported. 2020-10-12 16:54:26,452 DEBG 'start-script' stderr output: [#] ip link delete dev wg0 2020-10-12 16:54:26,501 DEBG 'start-script' stdout output: [warn] WireGuard interface failed to come 'up', exit code is '1'