Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pi-hole-server 5.18.4-1

Package Actions

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:	115
Popularity:	1.68
First Submitted:	2016-01-13 12:50 (UTC)
Last Updated:	2025-01-16 11:35 (UTC)

Dependencies (18)

bc (bc-gh^AUR)
bind-tools (bind-git^AUR, bind)
inetutils (inetutils-git^AUR, busybox-coreutils^AUR)
iproute2 (iproute2-git^AUR, busybox-coreutils^AUR, iproute2-selinux^AUR)
jq (jaq-bin^AUR, jq-git^AUR)
logrotate (logrotate-git^AUR, logrotate-selinux^AUR)
lsof (lsof-git^AUR)
netcat (nmap-netcat^AUR, openbsd-netcat-git^AUR, gnu-netcat-svn^AUR, gnu-netcat, openbsd-netcat)
perl (perl-git^AUR)
pi-hole-ftl^AUR
procps-ng (busybox-coreutils^AUR, procps-ng-git^AUR)
sudo (fake-sudo^AUR, polkit-fakesudo^AUR, sudo-git^AUR, doas-sudo-shim^AUR, doas-sudo-shim-minimal^AUR, sudo-hg^AUR, fudo-git^AUR, sudo-selinux^AUR)
git (git-git^AUR, git-gl^AUR) (make)
lighttpd (optional) – a secure, fast, compliant and very flexible web-server
nginx-mainline (nginx-quic-openssl-hg^AUR, nginx-quic-libressl^AUR) (optional) – lightweight http server
php-cgi (optional) – CGI and FCGI SAPI for PHP needed only for lighttpd
php-fpm (optional) – FastCGI process manager for php needed for nginx
php-sqlite (optional) – sqlite db access for nginx

Required by (2)

padd-git
pi-hole-whitelist-git (optional)

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 .. 47 48 49 50 51 52 53 54 55 56 57 .. 83 Next › Last »

ChuckHL commented on 2018-08-28 02:44 (UTC) (edited on 2018-08-28 03:08 (UTC) by ChuckHL)

Found the answer on this link.

https://discourse.pi-hole.net/t/0-0-0-0-response-on-pi-hole-4-0-for-blocked-domains/11589

and this: https://docs.pi-hole.net/ftldns/blockingmode/

The new blocking default method is redirecting everything blocked to 0.0.0.0

If you want the old behavior back, you need to add BLOCKINGMODE=IP OR BLOCKINGMODE=IP-NODATA-AAAA to /etc/pihole/pihole-FTL.conf

(Still not sure about the error I mentioned on my previous post about user 'pihole' not existing, and on the settings page under FTL Information, the User / Group shows as nobody / nobody)

ChuckHL commented on 2018-08-28 01:26 (UTC) (edited on 2018-08-28 02:23 (UTC) by ChuckHL)

I have uninstalled pi-hole-ftl and pi-hole-server and reinstalled but it did not help. One thing I notice thought when uninstalling is this error:

userdel: user 'pihole' does not exist error: command failed to execute correctly

When reinstalling the packages, I checked against /etc/passwd and no user pihole has been created.

P.S.: I am using pi-hole-server-4.0-8 and pi-hole-ftl-4.0-6 P.S.S: Another thing to mention is that my pi-hole box is not my DHCP server.

max.bra commented on 2018-08-27 18:45 (UTC)

Hi Taijian, no no everything is fine. ;-)

Taijian commented on 2018-08-27 18:40 (UTC)

One more thing (possibly?): I noticed that post_install we do:

chown -R http:http /srv/http/pihole

However, this is not done post_upgrade. Maybe it should? (no expert, just taking stabs in the twilight...)

max.bra commented on 2018-08-27 17:33 (UTC) (edited on 2018-08-27 17:34 (UTC) by max.bra)

how do i check? ps aux | grep dns

you should have stopped dnsmasq service before update and restart ftl after. as usual on any service replace update procedure. now it's late and is better and easier to reboot.

on my update pi-hole did not delete any of my 14 dns forward server... doh...

edit: formatting

max.bra commented on 2018-08-27 15:57 (UTC)

https://imagebin.ca/v/4DeSG7ssQfc9

stupid question: have you definitely killed old dnsmasq and are you using FTLDNS only?

ChuckHL commented on 2018-08-27 15:48 (UTC) (edited on 2018-08-27 15:54 (UTC) by ChuckHL)

If I leave gravity.list in the new format (per se) without the host ip in front of each domain and I try to go to those websites, the browser does not know where to go and returns an error that could not resolve the name (ERR_NAME_NOT_RESOLVED). If I add the host in front of each line I now can see "website blocked" pi-hole page.

max.bra commented on 2018-08-27 15:44 (UTC)

it's intentional since dnsmasq integration: https://github.com/pi-hole/pi-hole/commit/bac9e005aed0ac10ea9dfa63123ef1b5a9b7c72d#diff-9e53ae7c3c4f9235e5908d902fb93c8a

only local.list is leaved in hosts format

if you browse, for example, zzhomes.com you will receive tipical pihole blocking notification.

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 83 Next › Last »