Cannot access portal "Host validation failed"

Help
1

I have been successfully running Pihole in a bridged docker container for a few months now, and was trying to make a couple of changes today. Unexpectedly, I cannot connect to the webpage. I was able to connect earlier this week.

I’ve tried restarting the service and the same thing happens. Running web v6.1, core v6.0.6, FTL v6.1.

Expected Behaviour:

Navigating to the site I defined in pihole’s DNS brings me to the login page.

Actual Behaviour:

Navigating to the site I defined in pihole’s DNS presents me with the error message “Host validation failed. See logs for more details.”

I checked pihole.log and this is all that I found in the window I tried access the webserver.

Aug 24 18:00:00 dnsmasq[54]: query[PTR] 69.1.168.192.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: DHCP 192.168.1.69 is amazonplug022s.lan
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 1.0.0.127.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: /etc/hosts 127.0.0.1 is localhost
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 12.1.168.192.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: DHCP 192.168.1.12 is pc-ports.lan
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 166.1.168.192.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: config 192.168.1.166 is NXDOMAIN
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 1.0.18.172.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: config 172.18.0.1 is NXDOMAIN
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 217.1.168.192.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: config 192.168.1.217 is NXDOMAIN
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 100.0.31.172.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: config 100.0.31.172.in-addr.arpa is
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 1.0.0.1.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: cached 1.0.0.1 is one.one.one.one
Aug 24 18:00:00 dnsmasq[54]: query[PTR] 222.222.67.208.in-addr.arpa from 127.0.0.1
Aug 24 18:00:00 dnsmasq[54]: cached 208.67.222.222 is resolver1.opendns.com

Debug Token:

ERXY8820

2

I think that error message is coming from the container environment, not Pi-hole. Take a look at the container logs for more details.

Your changes may have moved your web-browsing host outside of the allowed range previously configured which can access the container and Pi-hole's web admin portal within.

3

I don’t think this is the case. I had not made any changes to pihole when I first encountered this issue, I was just trying to sign in to see what relevant fields were.

Additionally, the final entry in the docker log is stamped ~3 minutes before I tried to access the webserver.

4

That isn't a Pi-hole message.
Instead of looking into Pi-hole's logs, you should inspect the logs of whatever serves the website of the domain you are trying to access.
A cursory search could suggest that to be a homepage container, see e.g. Possible bug but more likely user error. "Host validation failed for: 192.168.0.X:3000. Hint: Set HOMEPAGE_ALLOWED_HOSTS to allow requests from this host." · gethomepage/homepage · Discussion #4789 · GitHub

1 Like
5

Ah yes, it’s an Nginx error. Thanks for the assist.

6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.