@hmu yeah i already reported it. Quick dix dirty : replace the lsof from pihole script (there's only one) with
ss -lnp '( sport = 53 )'
It fixes the web interface
Git Clone URL: | https://aur.archlinux.org/pi-hole-server.git (read-only, click to copy) |
---|---|
Package Base: | pi-hole-server |
Description: | The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server. |
Upstream URL: | https://github.com/pi-hole/pi-hole |
Keywords: | ad block pi-hole |
Licenses: | EUPL-1.2 |
Conflicts: | pi-hole-standalone |
Submitter: | max.bra |
Maintainer: | max.bra (graysky) |
Last Packager: | max.bra |
Votes: | 112 |
Popularity: | 0.134716 |
First Submitted: | 2016-01-13 12:50 (UTC) |
Last Updated: | 2024-08-10 12:32 (UTC) |
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 82 Next › Last »
@hmu yeah i already reported it. Quick dix dirty : replace the lsof from pihole script (there's only one) with
ss -lnp '( sport = 53 )'
It fixes the web interface
@schmodd yes sorry, my fault. try now.
I'm getting with 5.2.3-1:
arch-server-core-5.2.3-764358184.patch ... FEHLGESCHLAGEN
arch-server-admin-5.3-764358184.patch ... FEHLGESCHLAGEN
Hi everyone, successfully running pihole with Apache since a few months, now after a recent update webinterface stopped working as well, taking ages to load. I think I have narrowed it down to the lsof -Pni:53
in the pihole script. It loads fine on the command line with sudo -u http /usr/sbin/lsof ...
, so /etc/sudoers.d/pihole
is working correctly, but apparently php running with apache just hangs when using exec('/usr/bin/lsof');
(tested in separate script). I'm not aware that I changed any security settings in either php.ini or httpd.conf, and my vhost definition basically just points to the admin/ dir. Is usage of exec('lsof');
restricted somewhere for apache?
@tkremer nice find. I've already uninstalled everything and went with installing this on a pi, which was my original plan anyways. I was just testing it out for a bit there on my manjaro installation. I hadn't been using lighttpd though either, I was/am using apache. I thought I had checked to make sure all of the apache and php settings were still correct, but I could have missed something for sure. Webservers are definitely not my area of expertise.
@heavy.rocks had the same problem and I can't really come up with an explanation but my /etc/php/php.ini was erroneous. It was missing the sqlite3 extension in the dynamic extensions section. After un-commenting the line and restarting lighttpd.service everything is working as expected again.
Latest version is broken for me. Web interface is not working. I'm running manjaro and apache and it had been configured and running for several months without any trouble. Latest update appears to have broken access to the web interfacee and in chronometer pi-hole is showing active, but FTL offline, and ads today and local qrys are 0%. Nothing under Top Advert/Domain/Client. It does seem to be blocking ads as far as I can tell though, I think. I don't know. I'm not sure what exactly to try and do to fix it at this point.
5.2.1 is broken for me with the webinterface running in apache. The problem is: I cannot access it at all, getting 408 or sometimes the login page shows after minutes but the login is failing timed out. Downgrading to my last installed version dbf2488c1ef4 solves the problem.
I have tried to access the interface from 3 different PCs 2 Android devices and via curl from the server itself. All have timed out.
I have a problem with the web interface. The statistics and settings are shown correctly, but no settings can be saved. No error messages are displayed (it even says that the settings have been updated; but they aren't).
Any ideas?
@setboolean i am running "true" arch. No manjaro or endeavour hère... I will try to recompile. Somthing to note is, everything works well in console, iincluding lsof...
Pinned Comments
max.bra commented on 2018-02-09 16:45 (UTC) (edited on 2019-10-18 23:14 (UTC) by max.bra)
ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.
First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.