After every reboot of Pi-hole I have to restore the database via pihole -g -r because elsewise I'm getting a resolvement error for localhost in the diagnosis output of pihole -d.
This is my debug token after the database has been restored:
https://tricorder.pi-hole.net/r8cvx2k02j
The log is showing database errors - all I remember is having created a database with Postgres.
Does anybody know what to look for?
These database errors appear to be from your long term database, not the gravity database. Let's try making new database whole saving the old one if needed.
sudo service pihole-FTL stop
sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db
sudo service pihole-FTL start
The files actually were found in /etc/pihole and I did what you suggested with the errors having disappeared now.
https://tricorder.pi-hole.net/tnf0ulgy0r
But there's still an error:
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Accept-Ranges: bytes
ETag: "1251518635"
Last-Modified: Sat, 01 May 2021 17:40:05 GMT
Expires: Mon, 10 May 2021 16:18:19 GMT
Cache-Control: max-age=0
Content-Length: 10701
Date: Mon, 10 May 2021 16:18:19 GMT
Server: lighttpd/1.4.53
My latest debug token is at https://tricorder.pi-hole.net/tnf0ulgy0r.
My apologies for the error - my typo. I corrected my reply for the benefit of others who read this post in the future.
Should I create a separate thread for the other error?
Are you using the blockpage? If not then that result is correct.
How do I know if I'm using the blockpage?
You aren't. Ignore the warning.
Not all the blocking modes provide a block page. You are using NULL (the default) and this does not provide a block page.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.