I would like to access the Admin Web-Interface via HTTPS instead of HTTP. HTTP should be disabled as well.
Can anyone help me to manage this? I already read this article: Enabling HTTPS for your Pi-hole Web Interface
But I just want to do it local. So my Web-Interface just can be accessed local. You may wonder why I need HTTPS if it is just local, but there are several reasons for me to do that.
And do I need a SSL-Certificate? I know that I will get a Security-Error-Message every time I want to visit the Interface. But except this fact, are there any other disadvantages? And will this Security-Error-Message disappear if I install a Self-Signed certificate with letsencrypt?
letsencrypt does not allow purely local domains like pi.hole.
No, I strongly disagree. 1.) HTTP works for everyone and is most people are able to trust the users in their internal network, 2.) As you already pointed out yourself, using self-signed certificates is quite a stony path with many obstacles on the way, 3.) HTTP needs to stay enabled for the blocking page. However, access to the admin interface may be restricted.
First at all, thank you for your input.
If I understand you right, it is not possible to get a SSL-Certificat for a local domain or it is really hard.
But I didn't need a SSL-Certificat, right (if I ignore the warning)?
So why did you wrote that I need a SSL-Certificate?
And if I disable HTTP, Pi-Hole won't work properly, right? But what exatly do you mean with "blocking page" and that the admin interface may be restriced?
But the most important questions: How to enable SSL?
So, I created a self-signed Certificate and enabled SSL. Seems to work. But if I set the Port to 8443 it doesn't work anymore. I thought 8443 is the standard port for a HTTPS Website with login-access? Nevertheless 443 works fine.
The encryption seems to be okay, but it is possible to change AES_128_GCM to AES_256_CBC with HMAC-SHA1?
And about disabling HTTP. I don’t get it.. Why wouldn’t Pi-Hole block any DNS-Requests anymore, if the interface is only reachable through HTTPS? I can’t see the connection.
For example: Before I used Pi-Hole I set my providers DNS as the default on my Router. And I told my devices to use the DNS-Server from my Router. And I disabled HTTP Access on my Router as well. So the interface of my Router can only be accessed through HTTPS. But DNS-Requests worked fine. So why is here a problem?
I've never heard of port 8443 being used. Did you specify that port when trying to go to the page? If not, then it will automatically use port 443 for HTTPS.
The encryption will depend on what you used to generate the certificate afaik.
Pi-hole will continue to block ads if you disable HTTP, but the block page will not show up for any HTTP ad, you might have HTTP ads time out causing the page to load slower, and the web interface will not be available over HTTP. I know some of these are not an issue for you, but disabling HTTP does not bring any real benefits.
I wasn't able to find any way to set it to AES256. Are there really any generator for AES256 and do you know one? I was looking on so many sites and didn't find any solutions.. =/
And I have another question. You may have heard of FritzBox. It's a router which is pretty popular in Germany. You can access the Web interface via http://fritz.box (Local-URL)
And there is also the possibility to set it to HTTPS only. Then there will be a certificate Error. But FritzBox have the option, to download the certificate and import it to Chrome. Then the Warning will disappear. Is this also possible with Pi-Hole?
AES 128 is preferred to AES 256. There has been discussions on whether AES256 extra security was worth the cost, and the result is far from obvious. At the moment, AES128 is preferred, because it provides good security, is really fast, and seems to be more resistant to timing attacks.
You should be able to do the same import with Pi-hole. It isn't a FritzBox specific thing.
Yes, when you generated your self-signed certificate you obtained a certificate. This can be imported in Chrome in a similar way. See maybe also this link for an example of how to add such a file to Chrome.
And about importing a self-signed certificate into Chrome. Is that dangerous? Because I heard that some Anti-Virus Programs also use self-signed Certificates to scan the Internet-Access. But some Viruses use those Certificates to sniffer and modify a SSL-Connection. Can this happen to me too with my self-signed Certificate?
Okay, so then these settings seem to be unsuitable at least for the browser you are using to connect to the Pi-hole. Maybe you can try putting them in one by one and see which one causes the connection to fail.
A hacker could steal the certificate and could then sign any mocked domain with it and you wouldn't get a warning about the certificate being doubtful (as it isn't as you explicitly added this certificate).
So, the problem is the certificate.
I created it like this:
> openssl dhparam -out dhparam.pem 4096
The other one like this:
> openssl req -new -x509 -keyout lighttpd.pem -out lighttpd.pem -days 365 -nodes
The second one (req) works fine. I will try to create a new one with dhparam. But this may take a while. But why are there so many parameters at the second Certificate? Are they not needed for the Diffie-Hellman as well? And do I have to set the Certificate to chmod 400?
And this may be a stupid question: But is it possible or necessary to disable sslv1?
If you are interested then read about the differente you can read e.g. on
This means: only the owner can read the file, nobody (not even the owner) can change it.
sslv1 does not exist. This version circulated only inside Netscape Communications, since it had several shortcomings and flaws. For example, it didn't provide data integrity protection. Not a stupid question at all
Thanks for your help! Everything is working fine now.
With websites like: SSL Server Test (Powered by Qualys SSL Labs) is it possible to test the SSL. Is there maybe an add-on or something like that to test the SSL on a local URL?
I just want to make sure that I didn’t forgot anything..