Cant access pihole dashboard on any devices using any connections

[j4y11]

The issue I am facing:
cant access pihole dashboard on any devices using any connections
Details about my system:
im on a ubuntu laptop running on a intel centrino 2 and nvidia 9800m
What I have changed since installing Pi-hole:
i have default settings and configs too my knowledge

debug token: https://tricorder.pi-hole.net/yRvGkBp1/

[rdwebdesign]

You have dnsmasq installed in your system and it is using port 53:

[✗] udp:127.0.1.1:53 is in use by dnsmasq
    (...)
[✗] tcp:127.0.1.1:53 is in use by dnsmasq 

failed to create listening socket for port 53: Address already in use

Pi-hole needs this port free. You need to disable or uninstall dnsmasq.

[j4y11]

i've deleted dnsmasq and it still says its using ports

[rdwebdesign]

Please, generate a new debug token.

[j4y11]

after restarting this is the debug token
https://tricorder.pi-hole.net/RHAVrwuC/

[j4y11]

the ports are open now but the dashboard is still unavailable and its auto upgrading to https

[rdwebdesign]

OK.
Pi-hole is now working, but the web server is still not starting.

*** [ DIAGNOSING ]: Pi-hole processes
[✗] lighttpd daemon is failed

2023-12-06 19:20:38: (gw_backend.c.557) bind failed for: unix:/run/lighttpd/pihole-php-fastcgi.socket-0: No such file or directory
2023-12-06 19:20:38: (gw_backend.c.1700) [ERROR]: spawning gw failed.
2023-12-06 19:20:38: (server.c.1555) Configuration of plugins failed. Going down.

The issue is: No such file or directory. The file /run/lighttpd/pihole-php-fastcgi.socket-0 is not available.

What is the output of: ls -la /run/lighttpd ?

[rdwebdesign]

@j4y11

and its auto upgrading to https

Note:
This is just your browser trying https, because the domain wasn't found using http.
When the web server issue is fixed, this won't happen.

[j4y11]

@rdwebdesign

ls -la /run/lighttpd

ls: cannot access '/run/lighttpd': No such file or directory

[rdwebdesign]

You can try to create the path and set permissions, but I think they will be gone after restart.

I recently saw another case where the path is deleted on reboot.

The suggested solution was to recreate the directory on every lighttpd service start.
You need to edit the service file.

This command will open the file for edit, if your OS uses systemd:

sudo systemctl edit --full lighttpd.service

Then add this lines and save the file:

ExecStartPre=/bin/mkdir -p /run/lighttpd
ExecStartPre=/bin/chown www-data:www-data /run/lighttpd

Then reload the service files:

sudo systemctl daemon-reload

Maybe you will also need to restart lighttpd service with:
sudo systemctl restart lighttpd.service

[j4y11]

@rdwebdesign

sudo systemctl restart lighttpd.service

after following your steps this is my debug log

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

the panel is still non accessible

[rdwebdesign]

Now lighttpd started without issues.

Did you try to access using which IP?

• http://192.168.1.69/admin
• http://192.168.174.178/admin

[j4y11]

the first ip worked the second did not

[deHakkelaar]

Could you try below as well pls?

Lighttpd cannot start after reboot

You can simplify those three lines to a single one with below: ExecStartPre=/usr/bin/install -d /run/lighttpd -o www-data -g www-data -m 750 So it should look similar to below: pi@ph5a:~ $ sudo systemctl edit --full lighttpd.service [Unit] Description=Lighttpd Daemon After=network-online.target [Service] Type=simple PIDFile=/run/lighttpd.pid ExecStartPre=/usr/bin/install -d /run/lighttpd -o www-data -g www-data -m 750 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf ExecSta…

It merges three commands (mkdir, chown & chmod) into a single one.
Dont forget to run below after making changes and before you reboot to check:

sudo systemctl daemon-reload

The reason I include the chmod 750 (-m 750) is bc the socket folder on my Pi (with different path) has 750 permissions instead of 755 from the default umask:

pi@ph5a:~ $ stat /var/run/lighttpd
[..]
Access: (0750/drwxr-x---)  Uid: (   33/www-data)   Gid: (   33/www-data)

pi@ph5a:~ $ umask
0022

pi@ph5a:~ $ mkdir testdir
pi@ph5a:~ $

pi@ph5a:~ $ stat testdir
[..]
Access: (0755/drwxr-xr-x)  Uid: ( 1000/      pi)   Gid: ( 1000/      pi)

Always try to restrict as much as possible

EDIT:

pi@ph5a:~ $ man bash
[..]
       umask [-p] [-S] [mode]
              The user file-creation mask is set to mode.  If mode  begins
              with  a  digit, it is interpreted as an octal number; other‐
              wise it is interpreted as a symbolic mode  mask  similar  to
              that  accepted by chmod(1).  If mode is omitted, the current
              value of the mask is printed.  The -S option causes the mask
              to be printed in symbolic form; the default output is an oc‐
              tal number.  If the -p option is supplied, and mode is omit‐
              ted,  the  output  is in a form that may be reused as input.
              The return status is 0 if the mode was successfully  changed
              or if no mode argument was supplied, and false otherwise.

[rdwebdesign]

The first one (192.168.1.69) is the IP configured in your wifi interface wlp4s0.
Apparently it's working as it should.
I really expected only 192.168.1.69 to work.

The other one is on a different subnet range (looks like an USB Ethernet Adapter).

[j4y11]

Yeah it was a phone with USB tethering but it's working fine now thanks for the help

[j4y11]

The other one was a phone with USB tethering but yeah everything is working as it should