Why ca i not access Dev releases on new setup?

General Beta 6.0
1

Hi.
On my primary Pihole i am running on Dev releases, but on my new pihole backup i cannot reach Dev releases, why not?
I has changed to V6 Dev when developing V6 was started.

What do i do?
Regards
Goldhammer

2

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d
3

Debug Token: https://tricorder.pi-hole.net/vNcKmcrg/

4

Your debug log shows the old web server (lighttpd) is still installed and using port 80. Pi-hole is trying to use the same port, but this is not possible resulting in "Address in use" error.

If you don't need to use lighttpd, the easiest solution is to uninstall lighttpd and then restart Pi-hole (sudo service pihole-FTL restart).

In case you are using lighttpd for other services, you will need to change one web server to a different port.

5

i only use lighttps forpihole, and it is pihole who installed it.

6

Pi-hole v5 uses lighttpd.

Now you are running Pi-hole v6.
Pi-hole v6 doesn't need an external web server and your previous configuration is in conflict with v6.

You just need to uninstall lighttpd. Try sudo apt remove lighttpd and then restart Pi-hole.

7

Looking at your debug log, your Pi-hole is working as it should, except for two warnings in the log file:

  1. No upstream servers are defined, i.e., your Pi-hole does not know how to resolve any domains outside your local network
  2. As @rdwebdesign already pointed out, lighttpd is still running on your system. You are right, it had been installed by an older version of Pi-hole. However, there is some detection in place that tries to prevent such scenarios. Maybe this was a race collision: When Pi-hole checked the ports, lighttpd wasn't up (for any reasons), it decided using port 80/443 is fine. It then, however, lighttpd did take these ports later, Pi-hole did not try to runaround this issue again.

@moderators Should we change how we deal with HTTP server ports? Or stick with what we have right now. Once we can switch to a more recent civetweb version, we can mark ports "optional", e.g., 80o,443so should mean that the webserver can start even when either of the ports is used (it'd only be served on the free port).

edit

8
  1. The web site is missing, When i try to access the admin part on
    http://192.168.80.7/admin/ it says
    403 Missing
    And it has not set password.
    and http://192.168.80.7 shows "Placeholder Place".
9

Please try

sudo service lighttpd stop
sudo service pihole-FTL restart

Does it work now?

11

YES, great now it work,
and the bottom line says:

  • Core vDev (development, d80259ee)
  • FTL vDev (development, 91ea8d49)
  • Web interface vDev (development, 51545cc9)

Thank You Very much for your help.
And Merry Christmas to all of you.

13

Great! Same to you.

Make sure to run a final

sudo service lighttpd disable

to ensure this won't happen again after the next system restart.

14

I just have ne more issue.

In Settings -> DNS --- on the bottom of the page, it says "Conditional forwarding"
On my primary Pihole my setting is:
true,192.168.80.1/24,192.168.80.1,

but that setting do not work on my pihole backup, when i write this it says:
Config item validation failed
dns.revServers[0]: contains two commas following each other immediately

Why...can i not use the same setting, they are on the same network?

15

I am running Debian Bookworm, but when i run this command i get:
Usage: /etc/init.d/lighttpd {start|stop|restart|reload|force-reload|reopen-logs|configtest|status}

16

Please try

sudo systemctl disable lighttpd

instead

17

Thank you, that works.