I can't reach the Pi-hole v6 web interface

General Beta 6.0
1

Did exactly this today and for some reason I can't reach the webGUI of Pi-Hole v6 Beta :frowning:

I am trying to do a quick test while using a Debian 12.8 Live Boot x86-64 Release.

To show you the full LAN config :

  • 192.168.1.3 = Main enp3s0 Interface
    This is also the IP that I have chosen during the installation of Pi-Hole v5 Stable.
    It's the only interface with a Gateway and both APT and Unbound work just fine for example.
  • 10.0.0.136 = VLAN 10 Interface enp3s0.10
  • 10.0.254.3 = VLAN 254 Interface enp3s0.254
    These 2 are basically silly FTLDNS Interfaces only :slight_smile:

Result :

Both https://pi.hole/api/docs/ and https://pi.hole/api work just fine ?!?!

Any idea why the webGUI isn't working ??

I am also wondering what happend to "pihole restartdns" which use to restart Pi-Hole completely basically ?
Now only the two commands that don't restart the DNS Resolver are left ?!

Noticed it when setting up the webGUI password :wink:

Some other stuff you might want to know :

  • I am using SystemD-NetworkD for the LAN configuration.
  • When not using FTLDNS for the Host the SystemD-ResolveD Service is used for example during updates of Pi-Hole in the future.
  • SystemD-ResolveD and the Unbound Resolve thingy don't seem to have any kind of conflict.

Even tried installing Civetweb seperately and it even picked up the /opt/pihole/ path but then when I tried accessing it @ port 8080 like it shows itself I get the same error :grin:

2

I moved your post to a new topic because it is a new issue, not really related to the previous topic.

Please post a debug log to help us identify any issues.

1 Like
3

Without a debug log is not possible to really understand what is happening and we can only guess.

Did you read all v6 announcements? This is probably a web server conflict.

Pi-hole v5 used lighttpd as the web server. Pi-hole v6 has its own web server embedded in FTL.

If lighttpd is still installed and running, port 80 will be in use, so Pi-hole v6 will try to use port 8080.
If you also have another service using this port, you need to change the web server port to something else.

lighttpd is configured to serve pages only from /admin. The other path (/api) is served by the new web server.

Don't do that.

If you did, now you probably have 3 web servers running: lighttpd, civetweb and pihole-FTL.

This command is not needed any more.

If needed, pihole-FTL will automatically restart ifself after any configuration change.

1 Like
4

pihole -d -a is currently stuck at Discovering active DHCP Servers for some reason ?!

/EDIT :

After 10 minutes still does not continue ?!

Maybe it has issues with multiple Interfaces ?

5

There is only pihole-FTL active on the system right now :wink:

  • I removed Civetweb after noticing it does not help in any way.
  • When I installed Pi-Hole v5 the option to install LigHTTPd and PHP was skipped.

But I am still wondering a bit if that might actually be the issue ??
Does the migration to Pi-Hole v6 Beta check some kind of value that I do not wish to have any webGUI perhaps ?
How could I install it the v6 way so to speak ?

7

Try pihole-FTL dhcp-discover to check if there are issues during DHCP discovering.

1 Like
8

I only see some kind of weird issue with the Netmask at enp3s0.254 but I can tell you for sure that this is not the case in the DHCP Server configuration for that subnet/VLAN so I have no idea where that is coming from...

Also this command doesn't end at some point : Any way to skip this stuff ?!
All IP's are Static here :wink:

pihole-FTL dhcp-discover

Scanning all your interfaces for DHCP servers and IPv6 routers
Timeout: 6 seconds

  • Received 300 bytes from 10.0.0.138 @ enp3s0.10
    Offered IP address: 10.0.0.243
    Server IP address: N/A
    Relay-agent IP address: N/A
    BOOTP server: (empty)
    BOOTP file: (empty)
    DHCP options:
    Message type: DHCPOFFER (2)
    server-identifier: 10.0.0.138
    lease-time: 86400 ( 1d )
    netmask: 255.255.255.0
    router: 10.0.0.138
    dns-server: 10.0.0.139
    dns-server: 10.0.0.139
    hostname: "mintel"
    domain-name: "thuis.lan"
    --- end of options ---

  • Received 300 bytes from 10.0.254.1* Received 300 bytes from 10.0.254.1 @ enp3s0.254
    Offered IP address: 10.0.254.244
    Server IP address: N/A
    Relay-agent IP address: N/A
    BOOTP server: (empty)
    BOOTP file: (empty)
    DHCP options:
    Message type: DHCPOFFER (2)
    server-identifier: 10.0.254.1
    lease-time: 86400 ( 1d )
    Offered IP address: 192.168.1.102
    Server IP address: N/A
    Relay-agent IP address: N/A
    BOOTP server: (empty)
    BOOTP file: (empty)
    DHCP options:
    Message type: DHCPOFFER (2)
    netmask: 192.168.1.102
    router: 10.0.254.1
    dns-server: 10.0.254.2
    dns-server: 10.0.254.2
    domain-name: "254.lan"
    --- end of options ---

    server-identifier: 192.168.1.1
    lease-time: 86400 ( 1d )
    netmask: 255.255.255.0
    router: 192.168.1.1
    dns-server: 192.168.1.2
    dns-server: 192.168.1.2
    domain-name: "management.thuis.lan"
    --- end of options ---

9

If you want to generate a Debug Log without this section, you can temporarily edit the Debug Log to skip this step.

Open /opt/pihole/piholeDebug.sh in a text editor, scroll down to the last lines of the file. Now find the line containing check_dhcp_servers and comment that line adding a # before it (like this #check_dhcp_servers). Save the file and execute pihole -d again.

NOTE: remember to revert the change after the log is generated.

1 Like
10

NICE!!! :grin:

https://tricorder.pi-hole.net/tyfL8qKW/

Hope you can find something :wink:

11

The first lines already show the issue.

Your pi-hole is running the wrong branch for the web interface:

*** [ 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

[i] Branch: master is wrong. It should be development.

Run pihole checkout web development and try to access the web interface again.

12

Forgot to mention that it already bugged me that I was seeing PHP files while they should not be there... Sorry! :flushed:
It has been a long day of staring at the Terminal Window...

I just did the new checkout and another update afterwards and now it shows this :

Core
Version is v5.18.4-666-g9d53ad7 (Latest: null)
Branch is development
Hash is 9d53ad76 (Latest: 9d53ad76)
Web
Version is v5.21-1089-g65ad66d6 (Latest: null)
Branch is development
Hash is 65ad66d6 (Latest: 65ad66d6)
FTL
Version is vDev-de61d82 (Latest: null)
Branch is development
Hash is de61d828 (Latest: de61d828)

Is this correct ?

13

Yes.

Are you able to access the web interface?

14

It seems I am not :frowning:

http://192.168.1.3/ Does not work.
Not even on 8080 just to make sure there is not some kind of weird conflict...

pihole-FTL seems down so no wonder it is not working :
systemctl status pihole-FTL
● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2025-02-07 21:47:19 CET; 811ms ago
Process: 121835 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Process: 121854 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=1/FAILURE)
Process: 121856 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
Main PID: 121854 (code=exited, status=1/FAILURE)
CPU: 153ms

15

The debug log shows port 80:

80o,443os,[::]:80o,[::]:443os

Well, if FTL is down nothing will work.

Try to restart it with sudo systemctl restart pihole-FTL.service

16

It seems there is something seriously wrong because that's what I have been doing multiple times now and even systemctl status pihole-FTL doesnt always give me the full output after a restart attempt :

systemctl status pihole-FTL

× pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2025-02-07 21:51:43 CET; 10min ago
Duration: 67ms
Process: 122174 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Process: 122193 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=1/FAILURE)
Process: 122194 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
Main PID: 122193 (code=exited, status=1/FAILURE)
CPU: 152ms

Feb 07 21:51:43 debian systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
Feb 07 21:51:43 debian systemd[1]: Stopped pihole-FTL.service - Pi-hole FTL.
Feb 07 21:51:43 debian systemd[1]: pihole-FTL.service: Start request repeated too quickly.
Feb 07 21:51:43 debian systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Feb 07 21:51:43 debian systemd[1]: Failed to start pihole-FTL.service - Pi-hole FTL.

root@debian:/var/log/pihole# systemctl restart pihole-FTL
root@debian:/var/log/pihole#
root@debian:/var/log/pihole# systemctl status pihole-FTL

● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2025-02-07 22:01:54 CET; 3s ago
Process: 122525 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Process: 122544 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=1/FAILURE)
Process: 122545 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
Main PID: 122544 (code=exited, status=1/FAILURE)
CPU: 142ms

root@debian:/var/log/pihole# systemctl status pihole-FTL

● pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2025-02-07 22:01:59 CET; 3s ago
Process: 122551 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Process: 122570 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=1/FAILURE)
Process: 122571 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
Main PID: 122570 (code=exited, status=1/FAILURE)
CPU: 151ms

/var/log/pihole/ files don't give me any clue either and neither does journalctl -u pihole-FTL -xr :frowning:

Can this happen because of the last checkout and/or a password reset ?

17

Now that the system has settled a bit I got this output :

systemctl status pihole-FTL
× pihole-FTL.service - Pi-hole FTL
Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2025-02-07 22:02:21 CET; 4min 15s ago
Duration: 87ms
Process: 122627 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
Process: 122646 ExecStart=/usr/bin/pihole-FTL -f (code=exited, status=1/FAILURE)
Process: 122647 ExecStopPost=/opt/pihole/pihole-FTL-poststop.sh (code=exited, status=0/SUCCESS)
Main PID: 122646 (code=exited, status=1/FAILURE)
CPU: 172ms

Feb 07 22:02:21 debian systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
Feb 07 22:02:21 debian systemd[1]: Stopped pihole-FTL.service - Pi-hole FTL.
Feb 07 22:02:21 debian systemd[1]: pihole-FTL.service: Start request repeated too quickly.
Feb 07 22:02:21 debian systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Feb 07 22:02:21 debian systemd[1]: Failed to start pihole-FTL.service - Pi-hole FTL.

18

Please post a new debug token.

1 Like
19

https://tricorder.pi-hole.net/75rEWJcQ/ :slight_smile:

22

Could you please run

cat /var/log/pihole/FTL.log | pihole tricorder
cat /var/log/pihole/FTL.log.1 | pihole tricorder

and provide the two generated tokens so we can assess what went wrong during your checkout process?

You could then try

sudo killall pihole-FTL
sudo rm /dev/shm/FTL*
sudo systemctl restart pihole-FTL
1 Like
24

Sure :

:slight_smile:

After those commands it seems to be running, but there was no /dev/shm/FTL for some reason ?

Status seems good now :

Aaaaand I am logged into the new Pi-Hole v6 Beta webGUI !!! :grin: Thank you! :+1: :+1:

Time to do some testing! :sunglasses: