Package Details: pi-hole-server 4.4-1

Git Clone URL: (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:
Keywords: ad block pi-hole
Licenses: EUPL-1.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 62
Popularity: 2.59
First Submitted: 2016-01-13 12:50
Last Updated: 2020-02-26 10:58

Pinned Comments

max.bra commented on 2019-10-16 15:28

Since switching to pihole user for pihole-FTL - long term data is not retained on my machine.

sir_randomuser said: For some reason account http has expired, which was the root cause. Seems to be due to a recent systemd change:
Checking /etc/shadow, the user http had a trailing 1:

$ sudo cat /etc/shadow | grep http

Removing the expiration date has resolved it:

$ sudo chage --expiredate -1 http

max.bra commented on 2018-02-09 16:45

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 ( 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

1 2 3 4 5 6 ... Next › Last »

lewis2e commented on 2020-03-30 15:13

@max.bra Oh yeah! Sorry. I misread your comment! Cheers, anyway.

max.bra commented on 2020-03-30 15:10

glad you solve. anyway i was not speaking about /etc/resolv.conf... :-D

lewis2e commented on 2020-03-30 15:06

@max.bra Your suggestion gave me enough information to solve this! Massive thank you.

If you (or anyone) is interested...

I was unable to add the DNSStubListener=no option to /etc/resolv.conf as suggested* because I am using openresolv to manage that file. This is required by netctl which I am using as my network manager.

*EDIT - I misread @max.bra's comment. This was exactly what they were suggesting anyway :-)

I am sure that you probably can get openresolv to add the option, but I couldn't figure out how.

The solution was to instead add DNSStubListener=no to /etc/systemd/resolved.conf. This FINALLY seems to stop the dam thing binding to port 53 on boot, and pihole starts just fine. I note that systemd-resolved is still running (despite me disabling it), but seems to be keeping to itself now. There really is no killing that thing apparently....

Thank you for the help. Nice to get rid of this little paper cut every time I reboot my server.

max.bra commented on 2020-03-30 14:10

but... did you


in your /etc/systemd/resolved.conf?

max.bra commented on 2020-03-30 14:07

What about:

# grep -R -i resolved /etc/systemd/system/*
# grep -R -i resolved /lib/systemd/system/*

lewis2e commented on 2020-03-30 14:04

@max.bra I don't recall doing so, however, I built the system quite a long time ago now. I could not swear to it. More to the point, even if I did enable it, I should be able to disable it in the usual way (which I cannot). If the implication is that I am not using Arch, I am using Arch Linux Arm.

max.bra commented on 2020-03-30 13:56

@lewis2e in arch systemd-resolved it is not automatically enabled. that said, it should have been you who configured and enabled it.

lewis2e commented on 2020-03-30 10:25

Following every reboot, pihole.FTL fails to start. I have to manually stop the systemd-resolved.service and then restart pihole.FTL or it won't work.

I've tried disabling the systemd-resolved.service as described in the Arch Wiki, but it still starts up. I don't know how to find out what is calling for it. Any suggestions?

max.bra commented on 2020-03-23 10:27


ilpianista commented on 2020-03-23 10:19

Please note that sudo is required when using the UI:

lighttpd-angel[11938]: sh: sudo: command not found