No PiHole web interface after upgrade to version "v6.0.5-0-g9fe687bd"

Help
,
1

After an upgrade my existing PiHole install base to version "v6.0.5-0-g9fe687bd", I do no longer have access to the web interface.

I see in the log file "webserver.log" the following entries:

   [2025-03-09 15:03:48.024  12505] Initializing HTTP server on ports "80o,443os,[::]:80o,[::]:443os"
   [2025-03-09 15:03:48.274  12505] cannot create socket (entry 3)
   [2025-03-09 15:03:48.336  12505] cannot create socket (entry 4)
   [2025-03-09 15:03:48.336  12505] Failed to setup server ports
   [2025-03-09 15:33:16.109  462] Initializing HTTP server on ports "80o,443os,[::]:80o,[::]:443os"
   [2025-03-09 15:33:16.193  462] cannot create socket (entry 3)
   [2025-03-09 15:33:16.262  462] cannot create socket (entry 4)
   [2025-03-09 15:33:16.263  462] Failed to setup server ports
   [2025-03-09 22:32:30.855  4668] Initializing HTTP server on ports "80o,443os,[::]:80o,[::]:443os"
   [2025-03-09 22:32:30.902  4668] cannot create socket (entry 3)
   [2025-03-09 22:32:30.941  4668] cannot create socket (entry 4)
   [2025-03-09 22:32:30.942  4668] Failed to setup server ports

Debug token: 5lj1Qrxk

2

Can you please upload a new debug log?

The previous one is incomplete (apparently an issue in our server).

3

As requested, new debug token: gPYd3gRt

I have rebooted the server to make sure that it comes up in a clean state. The FTL.log file shows an entry:

   2025-03-10 20:37:42.854  [440M] ERROR: Start of webserver failed!. Web interface will not be available!
   2025-03-10 20:37:42.854  [440M] ERROR:        Error: Failed to setup server ports (error code 10.0)
   2025-03-10 20:37:42.855  [440M] ERROR:        Hint: Check the webserver log at /var/log/pihole/webserver.log

The webserver.log file shows than the following entries:

   [2025-03-10 20:37:42.765  440] Initializing HTTP server on ports "80o,443os,[::]:80o,[::]:443os"
   [2025-03-10 20:37:42.811  440] cannot create socket (entry 3)
   [2025-03-10 20:37:42.853  440] cannot create socket (entry 4)
   [2025-03-10 20:37:42.853  440] Failed to setup server ports

Additional information from my side after having reviewed all the debug logs: I have disabled IPv6 on my server.

Here the settings I have been using to have IPv6 deactivated on the Linux OS level:

  • Additional options in /boot/cmdline.txt command line:

ipv6.disable=1

  • Contents of /etc/modprobe.d/ipv6.conf file:
alias net-pf-10 off
alias ipv6 off
options ipv6 disable_ipv6=1
blacklist ipv6

No further changes in any other Linux config file.

4

That's probably what's causing webserver startup to fail, as Pi-hole's embedded webserver would try to bind IPv6 as well.

This would match the log info:

cannot create socket (entry 3)
cannot create socket (entry 4)

where entries 3 and 4 relate to the IPv6 addresses [::]:80o,[::]:443os.

To have Pi-hole's embedded webserver use IPv4 only, please try:

sudo pihole-FTL --config webserver.port "80,443os"
5

Have fired

sudo pihole-FTL --config webserver.port "80,443os"

and here the output found in the /var/log/pihole/webserver.log file:

[2025-03-10 20:37:42.765  440] Initializing HTTP server on ports "80o,443os,[::]:80o,[::]:443os"
[2025-03-10 20:37:42.811  440] cannot create socket (entry 3)
[2025-03-10 20:37:42.853  440] cannot create socket (entry 4)
[2025-03-10 20:37:42.853  440] Failed to setup server ports
[2025-03-10 21:50:46.699  440] Initializing HTTP server on ports "80,443os"

I now have access to the web portal :slight_smile:

9

The PiHole web interface has been running pretty slow when using HTTPS.

Thus, I have fired the command

sudo pihole-FTL --config webserver.port "80"

and the web interface access works much faster now on a Raspberry Pi 1 B+ device.

Maybe some little effort in further tweaking and optimising the code may increase the web interface access speed.

10

This is expected.

HTTPS communication needs to encrypt and decrypt web requests. This functionality demands a lot more processing. The difference is more noticeable on less powerful processors.

11

Yes, that's indeed my understanding. Hence the reason to deactivate HTTPS access as not required.

12

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