Pihole 6.0 is out with built in web server

General Discussion
1

Just updated, lighttpd nginx and apache options no longer needed.

pihole script asks if you want to disable the web server, if you choose not to, it tries to bind to port 8080

Apparently it’s not needing PHP either?

2

We know. Already discussed within our team today. Something we will look into shortly.

4 Likes
3

Should we update or wait for more info-patch etc?

4

Definitely wait if you don’t know what you are doing

3 Likes
5

I’ve accidentally update. Pi-Hole is dead, configuration deleted by updater. Do not update at this moment.

6

i did a pihole -up and it prompted to disable lighttpd, did so and both my dietpi piholes are running.

7

PiHole own update function is not something we manage.

8

Since I updated my pi-hole … it is not working anymore and I’m loosing dns quite often … that feel like I’ll have to re-install it … if any idea on the logs to check, I’m taking it …

9

Reinstall won’t help. Only restore from backup.

10

You might need to check with PiHole developer if you have issues with the app itself. Or you restore a backup

11

I did pihole -up and did not disable lighttpd as I have other things depending on it. Now pihole is runing but the web interface cannot be reached anymore. Any fix for this?
there’s no index.php anymore in /var/www/html/admin/

12

all files in admin folder have .lp extension, not .php

13

PiHole changed the port as it did not depend on web server anymore. It has a build in web functionality now. If PiHole detects a regular web server it will switch to port 8080. Forgot about PHP, lighttpd or Apache. They are not used by PiHole since v6.

14

oh!!! So everything was working fine, just right now PiHole is at 8080 port if you have something on port 80. Good to know.

15

Yes as long as you have a regular web server running, PiHole will switch ports.

Btw this is described on the current PiHole release information :stuck_out_tongue_winking_eye: Introducing Pi-hole v6 – Pi-hole

pihole-FTL will attempt to bind to ports 80 for HTTP and 443 for HTTPS. If there is any conflict on these ports, then it will revert to port 8080 for HTTP.

16

so what to do now if selcected not to disable lighttpd at upgrade? How do I get back to web interface?

17

Did you read any of the posts above?

18

I did port 8080 is working

19

You can check available ports as follows

ss -tulpn | grep LISTEN
20

The update went well for me. Just have to use HTTPS now and not http. I am using nginx.