Herman Terds

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Herman Terds

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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 worki
  2. 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 e
  3. 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
  4. 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 tak
  5. 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.
  6. 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