# Pi-Hole with Lighttpd HTTPS active on

**URL:** <https://discourse.pi-hole.net/t/pi-hole-with-lighttpd-https-active-on/33651>\
**Category:** Customizing Pi-hole\
**Created:** [May 30, 2020, 3:26pm UTC](https://discourse.pi-hole.net/t/pi-hole-with-lighttpd-https-active-on/33651 "2020-05-30T15:26:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [May 30, 2020, 3:30pm UTC](https://discourse.pi-hole.net/t/pi-hole-with-lighttpd-https-active-on/33651/2 "2020-05-30T15:30:27Z")

</div>

Its in the FAQ:

> [@Enabling HTTPS for your Pi-hole Web Interface](https://discourse.pi-hole.net/t/enabling-https-for-your-pi-hole-web-interface/5771):
>
> How can I enable HTTPS (SSL/TLS) for my Pi-hole Web Interface? Many users run their Pi-hole on Virtual Private Servers and such, meaning that they would need to access the Web Interface via insecure HTTP. Now, you are able to configure Pi-hole so you can securely access your Web Interface, and not cause issues with blocked HTTPS content. What has changed to allow this? With the release of v3.2, we have made changes to our default lighttpd config to not automatically enable the SSL engine if /et…

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-with-lighttpd-https-active-on/33651)._