# Updated pihole, rebooted, pihole not providing dns service, no web UI

**URL:** <https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396>\
**Category:** Help\
**Created:** [February 21, 2025, 3:46pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396 "2025-02-21T15:46:29Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![roygrubb](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@roygrubb](https://discourse.pi-hole.net/u/roygrubb)\
**Post date:** [February 21, 2025, 3:46pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/1 "2025-02-21T15:46:29Z")

</div>

## Expected Behaviour:

Web Ui accessible, pihole filtering DNS

## Actual Behaviour:

Pihole blocking web access, no web interface.

After the update to v6, pihole runs but doesn't function. I have another pi with older pihole that I've fallen back on for now.

Running on RPi0 2W, PiOS fully updated before pihole update. Version shows

```auto
Core
Version is v6.0.3 (Latest: v6.0.3)
Branch is master
Hash is 0e6d9e74 (Latest: N/A)
Web
Version is N/A (Latest: null)
Branch is N/A
Hash is N/A (Latest: N/A)
FTL
Version is v6.0.1 (Latest: v6.0.1)
Branch is master
Hash is 62904aef (Latest: 62904aef)

```

In the past, updates were routine and non-breaking.

I'm using lighttpd for pihole and apache2 for all other web server work. It's on a purely local LAN.  
In the past, I accessed the UI via [http://192.168.0.100:8888/admin/index.php](http://192.168.0.100:8888/admin/index.php)

Is it practical to copy the pihole installation on the fallback pi? If so what do I need to copy?

Is there any way back, or can you advise what I should do?

Thanks

## Debug Token:

[https://tricorder.pi-hole.net/02vrRz6R/](https://tricorder.pi-hole.net/02vrRz6R/)

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [February 21, 2025, 3:54pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/2 "2025-02-21T15:54:45Z")

</div>

> [@roygrubb](#):
>
> In the past, updates were routine and non-breaking.

As noted in our release post ([Introducing Pi-hole v6 – Pi-hole](https://pi-hole.net/blog/2025/02/18/introducing-pi-hole-v6/#page-content)):

> For existing users, we recommend backing up your current configuration before proceeding, as the upgrade is strictly a one-way operation.

The debug log you provided shows a V5 installation, not a V6 installation:

```auto
*** [DIAGNOSING]: Core version
[✓] Version: v5.18.4
[i] Remotes: origin	https://github.com/pi-hole/pi-hole.git (fetch)
             origin	https://github.com/pi-hole/pi-hole.git (push)
[i] Branch: master
[i] Commit: v5.18.4-0-g2cf046d

*** [DIAGNOSING]: Web version
[✓] Version: v5.21
[i] Remotes: origin	https://github.com/pi-hole/web.git (fetch)
             origin	https://github.com/pi-hole/web.git (push)
[i] Branch: master
[i] Commit: v5.21-0-gbe05b0f

*** [DIAGNOSING]: FTL version
[✓] Version: v5.25.2
[i] Branch: master
[i] Commit: 8943e260

*** [DIAGNOSING]: lighttpd version
[i] 1.4.69

*** [DIAGNOSING]: php version
[i] 8.2.7

```

Please provide a debug log for the V6 install that is causing you problems.

---

<div class="post-metadata">

**Author:** ![smurf](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/s/ee59a6/32.png) [@smurf](https://discourse.pi-hole.net/u/smurf)\
**Post date:** [February 21, 2025, 3:57pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/3 "2025-02-21T15:57:46Z")

</div>

> [@roygrubb](#):
>
> In the past, updates were routine and non-breaking

Usually those are incremental updates, so rarely you have issue, but this time it was a major upgrade from v5 - v6. [Introducing Pi-hole v6 - Announcements - Pi-hole Userspace](https://discourse.pi-hole.net/t/introducing-pi-hole-v6/75863)

[DNS Issues After Updating to V6 - Help - Pi-hole Userspace](https://discourse.pi-hole.net/t/dns-issues-after-updating-to-v6/76386/4)

---

<div class="post-metadata">

**Author:** ![roygrubb](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@roygrubb](https://discourse.pi-hole.net/u/roygrubb)\
**Post date:** [February 21, 2025, 4:33pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/4 "2025-02-21T16:33:17Z")

</div>

Ah, OK that's my fall back pihole on 192.168.0.99 - sorry. Should have been  
[https://tricorder.pi-hole.net/xnU5Yo73/](https://tricorder.pi-hole.net/xnU5Yo73/)

---

<div class="post-metadata">

**Author:** ![roygrubb](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@roygrubb](https://discourse.pi-hole.net/u/roygrubb)\
**Post date:** [February 21, 2025, 4:35pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/5 "2025-02-21T16:35:16Z")

</div>

I see. Thanks.

I saw the mention of v6 on howtogeek.com and just did what I always do.

---

<div class="post-metadata">

**Author:** ![nero355](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/nero355/32/54774_2.png) [@nero355](https://discourse.pi-hole.net/u/nero355)\
**Post date:** [February 21, 2025, 6:36pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/6 "2025-02-21T18:36:35Z")

</div>

> [@roygrubb](#):
>
> I'm using lighttpd for pihole and apache2 for all other web server work. It's on a purely local LAN.  
> In the past, I accessed the UI via [http://192.168.0.100:8888/admin/index.php](http://192.168.0.100:8888/admin/index.php)

In that case edit /etc/pihole/pihole.toml and look at the ports = 80, 443os line and change it to 8888 or 8888s and then systemctl restart pihole-FTL 🙂

o = optional  
s = https  
by the way!

> [@](#):
>
> Is it practical to copy the pihole installation on the fallback pi?  
> If so what do I need to copy?

Please don't and just use pihole -up 🙂

> [@](#):
>
> Is there any way back, or can you advise what I should do?

This can be fixed so please try the above 😉

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [February 21, 2025, 9:08pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/7 "2025-02-21T21:08:23Z")

</div>

> [@nero355](#):
>
> In that case edit /etc/pihole/pihole.toml and look at the ports = 80o, 443os line and change it to 8888o or 8888os and then systemctl restart pihole-FTL 🙂
> 
> o = http  
> os = https  
> by the way!

This is wrong.

The correct meaning is:

- `o` means _ **optional** _. If not available it won't cause issues.
- `s` means _ **secure** _. It should be used for secure ports, using _https_ (any port without `s` will use _http_).
- `os` means you are setting both flags, optional and secure.

---

<div class="post-metadata">

**Author:** ![nero355](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/nero355/32/54774_2.png) [@nero355](https://discourse.pi-hole.net/u/nero355)\
**Post date:** [February 21, 2025, 9:12pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/8 "2025-02-21T21:12:06Z")

</div>

Yeah, sorry, should have known better after reading the documentation of Civetweb a while back... 😊

Edited now... Thnx! 😉

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [February 21, 2025, 9:15pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/9 "2025-02-21T21:15:28Z")

</div>

Note:

Every v6 option is very well documented in `/etc/pihole/pihole.toml` and in the _ **Settings \> All settings** _ page:

 ![image](https://discourse.pi-hole.net/uploads/default/original/3X/4/4/440afcc8aae6c68bd70585ca571cdce851989e38.png)

---

<div class="post-metadata">

**Author:** ![nero355](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/nero355/32/54774_2.png) [@nero355](https://discourse.pi-hole.net/u/nero355)\
**Post date:** [February 21, 2025, 9:19pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/10 "2025-02-21T21:19:30Z")

</div>

Thank you for that by the way! 🙂

Like I said earlier : It's the most beautiful config file I have ever seen !!! 👍 👍

---

<div class="post-metadata">

**Author:** ![roygrubb](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@roygrubb](https://discourse.pi-hole.net/u/roygrubb)\
**Post date:** [February 22, 2025, 7:58am UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/11 "2025-02-22T07:58:58Z")

</div>

Thanks for this.

pihole\_debug.log showed config error is REFUSED (EDE: not ready) which led me to look at upstream DNS and found that the pihole.toml file had upstreams = []  
so I changed it to upstreams = ["8.8.8.8", "1.1.1.1"]  
and now have web access. Would this not be carried over from the vsn5 configuration?

Next, as suggested, I changed to ports line to  
port = "8888o,443os,[::]:8888o,[::]:443os" ### CHANGED, default = "80o,443os,[::]:80o,[::]:443os"  
Have I got that right? I still have no access to the pihole web UI on [http://192.168.0.100:8888/admin/index.php](http://192.168.0.100:8888/admin/index.php)  
which gives a 404  
and [https://192.168.0.100:8888/admin/index.php](https://192.168.0.100:8888/admin/index.php)  
says This site can’t provide a secure connection which is fair enough

---

<div class="post-metadata">

**Author:** ![roygrubb](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@roygrubb](https://discourse.pi-hole.net/u/roygrubb)\
**Post date:** [February 22, 2025, 4:40pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/12 "2025-02-22T16:40:29Z")

</div>

/var/log/pihole/webserver.log reported  
cannot bind to 8888o: 98 (Address in use)  
cannot bind to IPv6 [::]:8888o: 98 (Address in use)

so in lighttpd.conf have changed  
server.port = 8888  
to  
server.port = 8889  
and restarted lighttpd

I now have access to the Web UI! 😅

Do you think it's worth persuading howtogeek to add some warning better than this?  
"Your settings will be automatically updated to the new format if you’re migrating from v5."

Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [March 15, 2025, 4:41pm UTC](https://discourse.pi-hole.net/t/updated-pihole-rebooted-pihole-not-providing-dns-service-no-web-ui/76396/13 "2025-03-15T16:41:18Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.