strike

Regarding the speed. I'm sure you're already aware of this, but NordVPN does not offer port forwarding. And as long as you keep using them you will never be able to fully utilize your connection, as that requires an open incoming port for other peers to connect to. So your speed will always fluctuate but you almost certainly will never be able to get full speed. So my advice is, stop trying to get better speed or switch vpn provider to one that offers port forwarding.

Your template is too old and you need to add it yourself. On the bottom of the page click "Add another path,port..." And set it to variable, as the key you set "VPN_INPUT_PORTS", and as value you put the port. If you have multiple ports separate them with comma. Edit: Also see Q27: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Been years since I was using PIA, but maybe I can answer you anyway. Always use the most recent version of any software unless it for some reason gives you issues. PIA have .ovpn files for both TCP and UDP (at least they used to when I was using them). Use UDP if you can, as that is the fastest protocol.

See Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

No. IIRC it has to do with DNS validation.

First of all, you need to change your password asap, as it's in the log you posted. Second, set the STRICT_PORT_FORWADING to no, this setting only applies to PIA users. You need to have an open incoming port to get good speed. Have you port forwarded a port? It's unclear to me if purevpn offers port forwarding or not. In a quick google search, their website talks about port forwarding and what it is, but I can't see anything about if they offer port forwarding or not. I saw something about you need to download their app maybe? Are you on a private tracker? If so most of them require an open incoming port. And if you don't have it they won't let you download or it will be very slow. Try to download a well-seeded torrent on a public tracker, like a ubuntu ISO or something. Then you should at least be able to download, but the speed will be much slower than with an open incoming port. If you can download it on a public tracker you know it's definitely a port forwarding issue that's causing you to not be able to download on your private tracker. And there's no point in testing the speed on speedtest.net, that only works for web browsing and web downloads. The speed you get on torrents has nothing to do with your web browsing/web download speed as many factors are taken into account with torrenting. The only thing speedtest.net will tell you is that you MAYBE can get that speed, if all the conditions are right.

You didn't mention that in your OP, then you must add that subnet to your LAN_NETWORK as well. The point of the LAN_NETWORK variable is to define your network, and all the subnets you listed are different networks. So if you need access from all of them they need to be listed. There is no magical "catch all type networks" you can add instead, AFAIK anyway.

This is wrong. You need to set your LAN_NETWORK to 192.168.10.0,192.168.130.0 You can have multiple subnets defined, just separate them with comma. This container doesn't officially support a customs bridge network, like br0. It can work in some cases but sometimes it does not. If you want to go this route you'd better ditch the web ui and download the thin client and use that. Then you might get it to work on br0. By default all container on a custom bridge network are blocked from the host. This is a security feature. This means they can NOT access other containers on host and normal bridge network. They must be on the same custom bridge in order to communicate. I haven't tried it, but I think you can bypass this by setting "Host access to custom networks:" to enabled in settings->Docker.

This sounds like a volume mapping issue or a wrong path in the downloads section in deluge. Post your docker run command and a screenshot of the downloads section in deluge.

Hardware transcoding doesn't work in this container, reported by many people. Switch to the official one or the linuxserver one and you should be good.

Have you added your subnet under LAN_Network? Remember you're on a different network when connecting remotely over wireguard.

You can add or remove a subdomain to trigger the renewal process. If it fails again be sure to set the staging variable to "true", this will increase the rate limiting so you don't hit the limit when testing. Set it back to false when you have it working.

Make sure to read everything in Q6, there are a couple deluge specific things there you can try if you have tried everything else in there.

When torrenting to get great speed you need to have a port forwarded. NordVPN does not offer port forwarding, so you're out of luck there. Also see Q6: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

This is normal and harmless. If you're using PIA there is a script in place to bind the port every 15 min, this is a requirement from PIA side. If you don't bind the port every 15 min you will lose it and it will be assigned to someone else.

Sounds to me like you have your port forwarding backwards. On the WAN side it's port 443 and 80 that's need to be open. You can point those ports to 1443 and 180 on the LAN side. So you need to point port 443 to 1443 and port 80 to 180, not the other way around. And when you're checking if the port is open you have to check ports 443 and 80. Doublecheck your port forwarding and if it's still not working, post your docker run command and screenshot of the port forwarding. I don't know which config file you changed but you should post that too.

Yes it does, I just quoted from it: https://github.com/linuxserver/docker-swag/blob/master/README.md Just put all your extra domians in EXTRA_DOMAINS as it says. If you want mote info: Use google with the "site" argument as I have done for you here

Have you looked at the readme at github? I think it's mentioned somewhere else too and certainly in this thread. From the readme:

Look at the recommended post on the top of this page

@binhex Is there a way to get the "tun adapter IP" to stay persistent? So I finally updated the container today and I was already aware of the changes and the issues people are having. So read the faq and made changes accordingly. I have not had the time to read all the posts since the update tho so this may have been answered already. But yeah, I had issues with radarr connecting to deluge, but I figured it out I think. Don't know if it will stick tho, hence my question. I did what the faq says (ignored IP bypass part), but that didn't work. I get this error in radarr: Unknown exception: The operation has timed out.: 'http://192.168.2.218:8112/json' I'm running on a custom br0 network with its own IP and have been for a long time. And I'm only using privoxy included in delugevpn I'm not routing radarr through delugevpn. I then ignored Q25 and 27 in the faq, which don't apply, right? After trying a few things I tried changing the IP in radarr to the tun adapter IP, or the VPN IP/Deluge IP as my deluge log calls it and that worked! But not for long, as I restarted the container it gets a new tun adapter IP. Any other ideas to solve this? Nevermind, I figured it out. It was my pfsense firewall blocking. And I had to remove the IP's in the ignored field in radarr. And of course set the IP back to the IP I had before, not the tun adapter one. All working now!

Just updated the container and this warning is looping in the log nginx: [emerg] dlopen() "/var/lib/nginx/modules/ngx_http_lua_module.so" failed (Error loading shared library /var/lib/nginx/modules/ngx_http_lua_module.so: No such file or directory) in /config/nginx/nginx.conf:12 If I roll back to 1.12.0-ls36 the warning is gone. Any idea how to fix it?

You need to use the :v4-preview tag as v4 is not released as stable yet.

Your mappings looks fine now. And you have restarted the container right? Have you tried a well seeded torrent like ubuntu or something?

Yes, you should absolutely change to a endpoint that supports port forwarding

Yes, but set the download to path to /data/Incomplete then you should be good and your downloads should start fine.