ChickenBoo

You can do the basic records via file. /etc/pihole/custom.list is a hosts formatted file for records so you don’t have to use a gui.

I had dns issues until I got my allowed ips squared away. You could try setting it to 0.0.0.0/0 if it’s not already to verify it’s not the problem.

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.

And then offered to pay for the BOM of the device acting as though that completely makes up for the mistake, ignoring the potential harm to Billets intellectual property.

Then their apology is all butt hurt that they THOUGHT they’d offered to pay for it, but only sent the email internally, not realizing their mistake until called out again. Then whining that no one is giving them the benefit of the doubt when they’ve demonstrated lack of judgement throughout the whole ordeal.

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.

As a half a pack a day smoker for most of my life, this is what all addicts say.

You’re just in denial.

If you can quit whenever you want then why is this worth the fight to you? Because you’re addicted.

They help you get through the day because not having them is a stressor. Because you’re addicted.

I haven’t had a cigarette in like 2 years and they still sound good sometimes. Because I’m addicted.

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 think it was red letter media that did a whole thing about how Freddy got fingered was likely a middle finger from Tom green to the studio who paid him to make that movie.

I think it’s this one.

https://youtu.be/gEn3wcpNsg8

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.