DaddyNugget

Correct, I wasn't trying to ask for help, I was trying to let the other user know that there may be an odd error here or there, but your overall instructions should work. The only thing I needed to do outside of that was update pacman, which I mentioned previously. This was just to help other people if they get stuck like I did. Sorry for the confusion. At this time I'm all set.

No, actually in my case I eventually received an error stating "This gateway does not support NAT-PMP" a few times then the loop stopped working. I simply started it again when I saw it, and it's been chugging along fine since. My guess is that their server restarted, or docker updated or something.

That gateway looks like IVPN not ProtonVPN. I'd double check to make sure everything is straightened out. For what it's worth I also got an error message while requesting a port forward, but this was after several hours of success.

Thank you so much for all that you do binhex! You've built so many amazing containers, and frankly I'd be lost without you. Just so you know, after this step I had to run 'pacman -Syu'. Without this I either had out of date repositories or something. I could see the package could be installed, but none of the repositories could give me the file. After running the command I declined all of the available upgrades (I was unsure if I would break the container), but re-running 'pacman -S libnatpmp' was successful. Also, in case you already aren't aware, IVPN also announced that it would no longer offer port fowarding. This will push many people to Proton VPN as it did myself. Hopefully Proton will make it easier to retain a port forward, but until then hopefully we can figure out a workaround for PMP request. I've seen some scripts online, but I'm unsure of the exact way to implement it with the current docker container. I've experimented with trying to change the port via the qBittorrent API, but that hasn't been successful for me. The only other route I can think of is when a port change happens to shut down qBittorrent, update the config, spin it back up. Either way seems rather cumbersome.

Thank you guys for posting here as soon as you realized there was an issue. Had a few updates break some things this week, and you guys just saved me some headaches after dealing with everything else. Rolling back now!

On Android devices I use 'CalibreCompanion' or 'CCDemo' (trial/free version). Super handy app that makes connecting to Calibre a breeze.

Noted, thank you so much. I'll look into it. I have other issues with my network so I'm just gutting it and starting from scratch to remove a couple years of duct tape and quick fixes. I will reference this when I redo it all.

Bear with me as I'm not sure what Stubby is. Unless it's already baked into the docker image. I had the setting working fine for over a month pointing to my router, then it failed 2 days ago. I have tried setting it to the loopback addresses in the description of the image as a troubleshooting step to no avail.

I am also having an issue with this container as of yesterday morning. -Using multiple VLANs on my network -One VLAN is using the piHole container for content filtering (kids network) -PiHole and pfSense are configured together to force all DNS queries on that VLAN to go through piHole then into pfSense. As of yesterday morning, with no visible changes, all DNS queries were lost on that VLAN. I monkied around with it for a couple hours and got it going again. This morning the same thing happened. I suspect there is a cron job or something happening at night causing this but I am not certain yet. The three symptoms I see are A) the piHole DNS service is not running. B) the docker is reported as 'unhealthy'. C) running pihole -r shows that the pihole itself cannot obtain DNS entries at this point, and that there is a kernel update available. If anyone has any pointers please let me know.