Ability to change the GUI port

[John_Matrix]

Hello to everyone!

Is it possible to implement a form that give the Pihole admin to change the GUI port?
Indeed, in the case of an application must use the port 80 (for example a reverse proxy), it will conflict with the Pihole GUI port.

Many thanks in advance!

[yubiuser]

Is this a request for an option to expose an "easy" way to change the port or are you seeking help how to change the port.

For the latter have a look here:

Can't reach subdirectories on localhost:80

Not sure what FlightRadar24 is running as it's web server but most likely, lighttpd, a requirement of Pi-hole, took over and replaced that. Which is weird, because it should have failed at starting the service, since there should have been something there, serving the FlightRadar24 data, on port 80. Do you know what webserver the FlightRadar24 is based on ? L.E. Upon further analysis, it looks like the FlightRadar24 runs a custom app (which I assume is part web server) called fr24feed. I…

[John_Matrix]

This is indeed a request to "easy" change the port from the GUI (like we can find in OPNsense)
As far as I have found, this is possible to change the port by modifying some files in CLI but after a Pihole update, the default port will revert to 80

[Coro]

@John_Matrix

after a Pihole update, the default port will revert to 80

You can do this with modifying the lighttpd config file. I don't think it is reset on updates but this should be answered by a developer.

[yubiuser]

@John_Matrix

after a Pihole update, the default port will revert to 80

It should not, see here

Detect non-standard lighttpd port during update

I run lighttpd for pihole admin on a non-standard port (eg. 8080). Every time I update pihole with "pihole -up" it resets the server.port configuration setting in /etc/lighttpd/lighttpd.conf to use port 80, which means that the service won't restart and I have to go and manually update the lighttpd config. Since pihole updates are frequent, it'd be really nice if the update process could detect whether lighttpd is running on a port other than 80 and NOT change the server.port setting if so.

But if you try it and it does change the port back to 80, please file a bug report as this might be a regression.

[John_Matrix]

Thanks for the advice, I will modify the port and report back if it will be revert after an update.

[yubiuser]

Just for your info:

Help FTL not installed

It used to be that port 80 was a hard requirement for Pi-hole, though that it less relevant these days. The reason being is that we used to by default (though, it is still possible with some reconfiguring) serve a block page as a 404 for all Pi-holed requests, by returning the IP address of the Pi-hole and the rest of the url (e.g http://pi-hole-ip/images/advert.jpg, which doesn't exist, so 404 is returned) But since the rise of https, the block page has become less relevant. The plan for v6.0…

[RamSet]

@Coro

I don't think it is reset on updates but this should be answered by a developer.

@John_Matrix

Thanks for the advice, I will modify the port and report back if it will be revert after an update.

The lighttpd config file IS pulled "fresh" from github and no prior (local) changes to it are saved/restored, during an update/repair.

The PR specified above, pertains only to the Web interface (and its ability to handle different ports).

The installer/updater does not check for any custom ports. It pulls a pre-configured file on port 80 and overwrites the existing one.

[yubiuser]

Pi-hole v6 will allow to change the GUI port from the web interface itself.