spin up a second pihole docker and upgrade them separately so they can failover to the other one while upgrading.

Think I’m going to take this advice and put it in action! Thank you!

I think something else may be wrong if it breaks for 20 minutes.

When I originally setup my PiHole many, many, many months ago when I was still learning the Docker engine I had little to no issue.

I don’t know what caused it either being a power-outage or network loss but ever since I’ve been experiencing DNS related issues (I suspect it’s NTP not syncing), some days I’ll wake up before work realizing “oh shit I have no internet access” frantically trying to fix the issue.

I think i might take the advice of other commenters here and host two PiHole servers on separate devices/stacks, just got to hope my router supports it.

http://localhost/

Uh oh, clearly somebody didn’t do their due diligence and test that while it was still in staging.

Chances are some manager was pushing for completion before they could catch it.

FYI: 127.0.0.1 = localhost - Essentially no device can access the resources except for the machine/server hosting it.

I personally couldn’t even get ssl/tls working with NPM, reverse proxying worked but it really didn’t feel right.

Eventually learned about SWAG and had a much better experience setting it up. Now here I am on Traefik thriving.

If only there was an operating system that is resilient and doesn’t crumble over minor errors.

I had a poor experience with NPM which turned me to SWAG, it worked, but was a tad slow. Moved to Traefik and haven’t looked back.

Last release was over 5 years ago and judging by the issues not receiving responses best to assume it’s deprecated.

Cool project it seemed.