Package Details: pi-hole-server 5.18.2-1

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: 111
Popularity: 0.67
First Submitted: 2016-01-13 12:50 (UTC)
Last Updated: 2024-04-01 18:11 (UTC)

Dependencies (18)

Required by (2)

Sources (15)

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.

Latest Comments

« First ‹ Previous 1 .. 65 66 67 68 69 70 71 72 73 74 75 .. 81 Next › Last »

slip commented on 2016-11-02 08:37 (UTC)

Eh, I need to be able to figure this stuff out better, so I can't blame you. Although my setup still isn't working :/ I get this timeout for the web interface ni journalctl Nov 02 09:33:40 pihole lighttpd-angel[269]: 2016-11-02 09:33:39: (mod_fastcgi.c.2534) FastCGI-stderr: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /srv/http/pihole/admin/data.php on line 26 Nov 02 09:33:40 pihole lighttpd-angel[269]: 2016-11-02 09:33:39: (mod_fastcgi.c.2534) FastCGI-stderr: PHP Warning: min(): Array must contain at least one element in /srv/http/pihole/admin/data.php on line 257 Nov 02 09:33:40 pihole lighttpd-angel[269]: 2016-11-02 09:33:39: (mod_fastcgi.c.2534) FastCGI-stderr: PHP Warning: max(): Array must contain at least one element in /srv/http/pihole/admin/data.php on line 256

max.bra commented on 2016-11-02 08:09 (UTC) (edited on 2016-11-02 08:25 (UTC) by max.bra)

@10479 yes my fault! there's something missing in dnsmasq conf updating... done! with new 2.9.5 dnsmasq config files i lost the include line! my pi manage dhcp part too and using a conf of mine i missed completely the serious mistake. sorry for wasting your time.

max.bra commented on 2016-11-02 07:57 (UTC) (edited on 2016-11-02 07:59 (UTC) by max.bra)

journalctl should say something... pihole -c output? forgot: yes, all is working here

slip commented on 2016-11-02 07:51 (UTC)

Yeah. I've been using this package since you first released it and have always been well off with the instructions. Both dnsmasq.conf and 01-pihole.conf are in their place on a literally fresh and fully up to date install of arch. I don't know. I give up. I've wasted entirely too much time on this. I've installed it about 20 times today including on a fresh arch install. Clearly something is wrong because the margin for error is incredibly slim on a fresh install with nothing else to interfere. But ads aren't being blocked, logs aren't being created and the interface reflects it.

max.bra commented on 2016-11-02 07:16 (UTC)

have you followed the configuration instructions? lighttpd.conf is new dnsmasq conf files, now, are two: dnsmasq.main -> /etc/dnsmasq.conf dnsmasq.include -> /etc/dnsmasq.d/01-pihole.conf

slip commented on 2016-11-02 05:01 (UTC) (edited on 2016-11-02 07:03 (UTC) by slip)

Edit - I've even nuked the entire pi and started from scratch since it's only used for pihole. Still no pi.hole/admin resolution and the web interface still hangs and does nothing. Maybe the web interface is an upstream issue as they've had that issue in the past. Even further analysis shows that no logs are being generated.

max.bra commented on 2016-11-01 21:23 (UTC)

@10479 it's a little recursive problem. upgrade follow post upgrade instruction (creating /etc/dnsmasq.d/01-pihole.conf) reinstall again or run pihole -g

slip commented on 2016-11-01 20:01 (UTC) (edited on 2016-11-01 20:03 (UTC) by slip)

Wow, fast response time!! I ran the latest update, but I'm still not getting pi.hole/admin to work. Are you? When I install, it complains about this, but to be fair, that was there after the last update as well. cat: /etc/dnsmasq.d/01-pihole.conf: No such file or directory cat: /etc/dnsmasq.d/01-pihole.conf: No such file or directory /usr/bin/pihole: line 126: /etc/dnsmasq.d/01-pihole.conf: No such file or directory Which is tied to: #add addn-host= to dnsmasq echo "addn-hosts=/etc/pihole/gravity.list" >> /etc/dnsmasq.d/01-pihole.conf It looks like this whole 01-pihole.conf is for that new enable/disable feature, but maybe it's causing more issues than it's trying to solve for us? Edit: And when I update pihole with pihole -g, I get this: ::: Refresh lists in dnsmasq... cat: /etc/dnsmasq.d/01-pihole.conf: No such file or directory cat: /etc/dnsmasq.d/01-pihole.conf: No such file or directory ::: No hosts file linked to dnsmasq, adding it in enabled state /usr/bin/pihole: line 126: /etc/dnsmasq.d/01-pihole.conf: No such file or directory

max.bra commented on 2016-11-01 19:29 (UTC) (edited on 2016-11-01 19:29 (UTC) by max.bra)

@10479 good point! thanks for reporting. completely missed that! done following official way. edit: typo

slip commented on 2016-11-01 18:44 (UTC)

One of the tweaks listed for the latest release is: [TWEAK] - Remove pi.hole and <hostname> from gravity.list put them as address= in 01-pihole.conf #849 I'm assuming that is what's causing the pi.hole/admin interface to stop working in the AUR release as I don't see that file, nor pi.hole referenced in the PKGBUILD. Not a huge deal, but the name resolution was nice, because just <hostname>/admin doesn't allow changes to be made in the web interface. Should pi.hole just be added back into the gravity.list?