New install of trixie on a rpi4. Installed pihole and everything works fine except I can’t access the admin page via https. I get this error regardless of the browser I use.
Firefox blocked your visit to this site because the signature on the certificate provided for pi.hole isn’t valid.
Error code: SEC_ERROR_BAD_SIGNATURE
Any suggestions?
Core v6.2.1, FTL v6.3, Web interface v6.3
debug token is: https://tricorder.pi-hole.net/2cn2nequ/
Try disabling the web interface on port 443:
In file /etc/pihole/pihole.toml change the port line to:
port = "80,[::]:80"
The browser gives me ERR_CONNECTION_REFUSED when trying to connect after changing this.
Can you access via IP?
Do you see the same error if you try from a different browser?
That message is what Edge gives me. Firefox says
Firefox can’t establish a connection to the server at pi.hole.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.
If I use http: then I can connect with either. I can also connect to http://192.168.1.253/admin. Just no https.
This is expected.
You are using only port 80:
2025-11-01 05:41:48.055 CDT [1207M] INFO: Web server ports:
2025-11-01 05:41:48.055 CDT [1207M] INFO: - 0.0.0.0:80 (HTTP, IPv4, OK)
2025-11-01 05:41:48.055 CDT [1207M] INFO: - [::]:80 (HTTP, IPv6, OK)
Without port 443, there is no https.
Then I don’t understand how this helps. I can access http just fine with the default setting. I just can’t open https because the browsers have problem with the cert.
You can't use https without port 443. Every browser will complain if you access https using port 80. You need to add port 443 to your config to use https protocol.
If you installed a custom certificate and it is invalid, you need to reinstall it.
If you are using the auto-generated Pi-hole certificate, you can simply delete all certificate files (they start with tls) in /etc/pihole and restart Pi-hole. A new certificate will be generated.
yeah, I am using what pihole generated. Deleting the tls files and restarting pihole hasn’t made a difference. I still get the same error. Up until a few weeks ago I was running this on bookworm for a few years and didn’t have a problem. I’ve tried uninstalling pihole and reinstalling it but no luck. I might try starting from scratch again.
I appreciate your help.
I tried reinstalling the os and pi hole from scratch and same issue. I compared the certificate from the copy running on bookworm to the cert issued by the copy running on trixie.
so, I deleted the tls files on the pihole running on bookworm and restarted pihole. I now get the same error on that.
I had backed up the tls files before I deleted them on bookworm. Since the updated copies didn’t work I restored the files and those worked. I then copied the tls files from the bookworm image to the trixie image and now trixie is working.
