AdminLTE version is v5.9 - php.socket-0 Connection refused

Help docker
1

Hello,

just upgraded to the new image pihole/pihole:latest
here the version status:

  Pi-hole version is v5.7 (Latest: v5.7)
  AdminLTE version is v5.9 (Latest: v5.9)
  FTL version is v5.12 (Latest: v5.12)

the localhost/admin page return a 404
I noticed this inside the docker instance:

unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused

root@2d77a06f3f0c:/var/log/lighttpd# tail -f error.log
2021-12-24 12:34:51: (server.c.1464) server started (lighttpd/1.4.53)
2021-12-24 12:40:58: (server.c.1464) server started (lighttpd/1.4.53)
2021-12-24 12:40:58: (gw_backend.c.476) unlink /var/run/lighttpd/php.socket-0 after connect failed: Connection refused

pihole is working but not the admin page.

Thanks for your help

2

it's ok now.
thanks

3

Did you do anything to make it work?

4

quick response.
no, it's not working, even after restarting docker desktop / host

7

do you have any clue about this issue ?

thanks :blush:

8

as a workaround , I change the host/container port for web:

    ports:
      - "8080:80/tcp"

now I can access from hosts with http://localhost:8080/admin
I really don't know why. port 80 my host is not used.

thanks

9

Maybe your docker does not have low-number port binding privileges for some reason and, hence, fails in creating the web port at all if it is 80?

10

I found the issue.
my Nginx ingress on my docker desktop Kubernetes. :sob::joy: (my bad)

One more question
Since the last update, I can see a warning triangle information about full disk usage

Disk shortage (/etc/pihole/pihole-FTL.db) ahead: 73582116% used

but my pihole-FTL.db is only 352K Dec 26 09:35 pihole-FTL.db

Any clue about this ?

Best regards

11

The warnings have always existed in /var/log/pihole.log. A change to Pi-hole made them more visible by also printing them into /var/log/pihole-FTL.log and showing them on the dashboard.

Brief documentation for these warning can be found here:

https://docs.pi-hole.net/ftldns/dnsmasq_warn/

Your issue may be related to: