Script Installed Dashboard at Apache:80

Help
1

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

Expected Behaviour:

Rather expected to find the dashboard at :8080, on the lighttpd server, but...

Actual Behaviour:

...instead it's only available on port 80 of my server's apache2 setup. It installed the lighttpd server, just didn't use it.

Debug Token:

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

Also experiencing an issue with very infrequent use of cache, as detailed in community post. Not sure if the two are related, but thought I'd better sort this part out first.

2

I'd be happier using the lighttpd server at :8080, as was using the apache:80 internally.

Love to know how to make the install script do this when I have a co-located apache2 server.

Is there any way to completely remove pi hole...safely?

3

Pi-hole's lighttpd installation would default to port 80, provided you opted for installing the webserver along with the admin UI during Pi-hole's installation.

You'd have to manually adopt your lighttpd configuration to move it to a different port.

Your debug log shows Apache listening on port 80 and lighttpd listening on 8080:

*** [ DIAGNOSING ]: Ports in use
    (...)
    tcp:0.0.0.0:8080 is in use by lighttpd
    (...)
    tcp:0.0.0.0:443 is in use by apache2
[✗] tcp:0.0.0.0:80 is in use by apache2 (https://docs.pi-hole.net/main/prerequisites/#ports)

This would imply that you already managed to move lighttpd to port 8080, and also that it's UI would be accessible via that port (and potentially via Apache's 80 as well, if that would be configured accordingly).

By what exact URL did you try to access Pi-hole's UI?

4

http://192.168.0.101/admin/index.php gives me the pi hole dashboard, whilst http://192.168.0.101:8080/admin/index.php just spins.

All my apache:80 files are still in /var/www/html, but I can no-longer reach them.

Post install, no reconfiguration of the lighttpd...dunno how?!

5

Oops! No Firewall entry for pi hole dashboard on :8080.

Now I have the dashboard at both http://192.168.0.101/admin/index.php & http://192.168.0.101:8080/admin/index.php, and my underlying apache setup accessible at http://192.168.0.101/

Anyone know how to constrain the lighttpd server to just port :8080, and free port :80 for my apache setup?

6

...or rather, how to prevent an existing apache setup from serving the pi hole dashboard via my internal-use port 80?

It's one or the other...not 100% sure which.

7

No, it appears that I have lighttpd serving the pi hole dashboard on port 8080, and have apache2 serving it on port 80.

I'd be very interested to learn how I might prevent the apache daemon from serving the pi hole dashboard on port 80, as I use that for testing internally.

8

Oh, this one's easy. I think I have it sorted.

Turns out that the pi hole installer script puts the dashboard admin files under /var/www/html.
That's also the content directory for my apache2 server. I just need to change the apache2 home directory, and then it won't serve the pi hole dashboard, like it is.

T.

9

Oh, great. All the pi hole scripts under /var/www/html are bound to that directory, as are all my pre-extant test files.

It doesn't appear possible (very easily), to shift the pi hole dashboard away from my apache2 installation's default home directory. :frowning:

10

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