# Locale DNS Adressen nicht erreichbar / https nicht verwendbar

**URL:** <https://discourse.pi-hole.net/t/locale-dns-adressen-nicht-erreichbar-https-nicht-verwendbar/66374>\
**Category:** Help\
**Created:** [November 17, 2023, 12:15am UTC](https://discourse.pi-hole.net/t/locale-dns-adressen-nicht-erreichbar-https-nicht-verwendbar/66374 "2023-11-17T00:15:19Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![chrislph](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/chrislph/32/32723_2.png) [@chrislph](https://discourse.pi-hole.net/u/chrislph)\
**Post date:** [November 17, 2023, 1:25am UTC](https://discourse.pi-hole.net/t/locale-dns-adressen-nicht-erreichbar-https-nicht-verwendbar/66374/2 "2023-11-17T01:25:36Z")

</div>

The user @WaLLy3K has posted this guide for HTTPS

> [@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/locale-dns-adressen-nicht-erreichbar-https-nicht-verwendbar/66374)._