faust
February 27, 2018, 8:49pm
1
Expected Behaviour:
Going to
http://192.168.178.x/admin/db_queries.php
Should open the admin panel as it did before rebooting but the site does not load anymore. Curl output:
RPI has a fixed IP in the router and th
Actual Behaviour:
$ curl -i http://192.168.178.x/admin/db_queries.php
curl: (7) Couldn't connect to server
Additional info
Added a tempfs and mounted it to
/var/log
Debug Token:
v47vp6ya8c
Unsure what kind of information i could add to help identify my problem - tried reinstalling but it didn't fix the panel.
Thanks for the help.
abarns
February 28, 2018, 3:05am
2
Good evening- I am having a similar problem, although with slightly different results than the original poster is seeing. I am getting an http 500 internal server error when attempting to connect following the upgrade to the most recent version of Pi-Hole. I've tried restarting lighttpd which has fixed problems for me before, but isn't working in this case.
I won't bore you with the intermediate details but I've uninstalled and re-installed at this point and it's still not working.
Debug token: d1jkmg9vwc
Thanks for the help and thanks for the awesome piece of software, I hope we can get it up and going again soon!
abarns
February 28, 2018, 3:13am
3
I think I found the solution for my issue, if anyone else encounters it (it fixed dnsmasq but my admin web panel is still not working):
Originally published at: https://pi-hole.net/2018/02/14/pi-hole-v3-3-released-its-extra-special/
Update 2018-02-20 18:05
Hi All, After a few days of pulling out our hair and troubleshooting this whitelisting issue that some of you have reported, we're finally getting to the bottom of it.
The good news is, whitelisting is not completely broken. You can still whitelist domains from the cli with no issues by calling pihole -w [domain-to-whitelist]. The issue only affects whitelisting from th…
1 Like
Hello,
I had a similar issue with my update.
I had Jessie + Pi-Hole (lighttpd / FTL v2.13.2) and another apache server running on a Rpi3.
The update broke Pi-Hole web admin and my apache server.
But I could see that Pi-Hole is working fine.
Fortunately I did an image of my SD card before the update, so I went back to it.
Everything is working fine again, but I have an old version of Pi-Hole.
Now I'm waiting for the next update, maybe it will fix my problem.
faust
February 28, 2018, 8:11am
5
Oh that is interesting to hear - i might try to roll back to the previous version - i somehow didn't think of updates screwing with the admin panel.
Edit:
I've found another thread mentioning that the service lighttpd might not be running and checked:
$ service lighttpd status
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2018-02-28 08:45:58 UTC; 92ms ago
Process: 4456 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
Process: 4446 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
Main PID: 4456 (code=exited, status=255)
Feb 28 08:45:58 raspberrypi systemd[1]: lighttpd.service: Main process exited, code=exited, status=255/n/a
Feb 28 08:45:58 raspberrypi systemd[1]: lighttpd.service: Unit entered failed state.
Feb 28 08:45:58 raspberrypi systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Edit 2:
Issue was resolved by creating the httpd log directory:
sudo mkdir /var/log/lighttpd && sudo chown www-data.www-data /var/log/lighttpd
This needs to be done on each reboot and it worked fine since then!
1 Like
system
Closed
March 21, 2018, 8:11am
6
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.