I use this guy https://github.com/haugene/docker-transmission-openvpn
Open up the transmission rpc port and you’re golden. It also sets up a proxy for any other services/devices you want to run through the VPN. Supports port forwarding for PIA too.
Even if your router can issue two DNS servers you shouldn’t add a second that’s not a pihole.
Otherwise a client will just fail over any blocked lookups to the secondary, negating the purpose of a pihole.
I found it easiest to get them running on docker. The documentation wasn’t FANTASTIC, but it got me there in the end.
Then I have nginx proxy manager running in another docker container, which handles the virtual hosts for me. It’s the one actually bound to 80 and 443. Will help you get set up with SSL certs easily, too.
I use nginx proxy manager to route all my services. Just forward 80 and 443 from my router to that.
It won’t scale linearly. A lot of those users will be subscribed to subs the instance is already replicating. It would only be new subs that would add to the growth.
The lines before it seem to imply you’ve run it before. If this is a new install I’d try dropping the scheme entirely and starting again.