Unable to access Pi.Alert's web page

[Odradek]

Hello, I can't access the page because the port 80 is being used by another service (OpenmediaVault). so the question is: how can I change the port for Pi.Alert?
Thanks

[WildWeasel109]

I have a similar issue trying to install Pi.Alert on a bullseye. Install works OK (errors during Vendor Database module downloads, tried fix still failed) can access PiHole which is only offering DNS, can ping pi.alert (macos with Safari can’t resolve pi.hole as host name) and gets webpage permissions error (same error when using IP addr). I have UFW installed and running with port 80 allowed, Pi-hole is using another port.

When I checked netstat there’s no mention of port 80 being advertised. Lighttp service running OK.

Any suggestions or advice?

[LK7890]

I have same request, my 80 port is being used by another APP , I cannot find the doc about change the port for Pi.Alert

[smibrandon]

Pi.Alert uses the same port that you have designated for PiHole (typically 80). You can, however, change this in /etc/lighttpd/lighttpd.conf and look for the row server.port. I have mine setup for 8080, and it applies this to Pi.Alert, too. Once you change that, restart LigHTTPD by using sudo service lighttpd restart.

One important FYI, though: when you update PiHole, it reverts it back to 80. So, after you update, just jump in and put it back to 8080 (or whatever you choose to use)

[MarvinMynx]

Pi.Alert uses the same port that you have designated for PiHole (typically 80). You can, however, change this in /etc/lighttpd/lighttpd.conf and look for the row server.port. I have mine setup for 8080, and it applies this to Pi.Alert, too. Once you change that, restart LigHTTPD by using sudo service lighttpd restart.

One important FYI, though: when you update PiHole, it reverts it back to 80. So, after you update, just jump in and put it back to 8080 (or whatever you choose to use)

How do you access the pi.alert webpage? http://IP/pialert/ isn't working for me. If pi.alert always uses the same port (80/HTTP) as pi-hole does and pi-hole is already occupying http://IP and http://IP/admin how can I access the pi.alert website? http://IP/pialert/ just shows me the same page as http://IP does (from pi-hole)

[chowtime3721]

Pi.Alert uses the same port that you have designated for PiHole (typically 80). You can, however, change this in /etc/lighttpd/lighttpd.conf and look for the row server.port. I have mine setup for 8080, and it applies this to Pi.Alert, too. Once you change that, restart LigHTTPD by using sudo service lighttpd restart.
One important FYI, though: when you update PiHole, it reverts it back to 80. So, after you update, just jump in and put it back to 8080 (or whatever you choose to use)

How do you access the pi.alert webpage? http://IP/pialert/ isn't working for me. If pi.alert always uses the same port (80/HTTP) as pi-hole does and pi-hole is already occupying http://IP and http://IP/admin how can I access the pi.alert website? http://IP/pialert/ just shows me the same page as http://IP does (from pi-hole)

same here... i'm looking for answers of this problem too

[jokob-sk]

You can change the port by running:

sed -ie 's/= 80/= 8080/g' /etc/lighttpd/lighttpd.conf

Where 8080 is your new port number.

As for where the UI is located, in my docker fork it is http://HOST_IP:20211/pialert/devices.php but that will depend on your custom port.

[jonathankonrad]

Hello I have the same issue and I do not believe it is a port issue. On my install

http://IP/admin brings up the index.php of pi-hole. No problem, works great.

However,

http://IP/pialert just shows the '403 Forbidden' error message.

I have checked and there is a sym link that points /var/www/html/pialert to /home/admin/pialert/front Which is is where it installed following the instructions. In the front folder there is a link that points index.php to devices.php in that folder. I have checked all the permissions. The group is www-data for all the files. I am at a loss.

The scanning works from the terminal. It even emails a report properly. I just can't access the Web Interface.

[jonathankonrad]

I know this does not address the issue, but I started again, this time just using the script instead of the manual installation. Everything works. What is odd is checking all the files permissions and location, they appear the same. So ... I wish I could share what the difference was. Good news is the one-step script worked!