Arch Linux User Repository

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.

this need to be posted to pihole-FTL

it needs a recompilation

After this update:

upgraded nettle (3.5.1-2 -> 3.6-1)

pihole-FTL.service doesn't start anymore:

$ sudo systemctl status pihole-FTL.service ● pihole-FTL.service - Pi-hole FTLDNS engine Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2020-05-09 13:25:44 CEST; 95ms ago Process: 3736 ExecStartPre=/bin/chown -R pihole:pihole /etc/pihole (code=exited, status=0/SUCCESS) Process: 3737 ExecStartPre=/bin/chown pihole:http /etc/pihole/regex.list (code=exited, status=1/FAILURE) Process: 3739 ExecStartPre=/bin/chown root:root /etc/pihole/logrotate (code=exited, status=1/FAILURE) Process: 3741 ExecStart=/usr/bin/pihole-FTL no-daemon (code=exited, status=127) Main PID: 3741 (code=exited, status=127)

: pihole-FTL.service: Scheduled restart job, restart counter is at 5. : Stopped Pi-hole FTLDNS engine. : pihole-FTL.service: Start request repeated too quickly. : pihole-FTL.service: Failed with result 'exit-code'. : Failed to start Pi-hole FTLDNS engine.

Downgrade of nettle solved this problem

@deemon
1) pi-hole-gravity.timer is present in all versions and is statically enabled. All is in auto pilot mode. :-)
2) you can add as many DNS server you want. queries will be forwarded over all of them and if you query an URL that is in your intranet it will be resolved by your internal DNS. I have a similar config for my notebook.

I have this question though... It does say in wiki that the "standalone" version comes with the timer (pi-hole-gravity.timer) but no mention of it in server version. But does it have it also (and just not mentioned in the wiki) or I have to manually update the server filter lists with the server version?

Another question is, would it be possible to make it use DHCP aquired DNS server as the base, not the statically configured with pihole -a setdns 1.1.1.1 for example? PROBLEM is that when I am in my work LAN, we have our own internal DNS (only accessible from corporate WAN) with many internal server names and I would like to use that as base, but when outside building and in external networks, it's unreachable and I would like to use either whatever DHCP provides there or then the statical 1.1.1.1 would be OK also.

Thanks. Now works :-)

hi deemon, try now

Can't get this to work properly and wiki doesn't help either.

● pihole-FTL.service - Pi-hole FTLDNS engine
   Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2020-02-26 10:28:23 EET; 4min 34s ago
  Process: 1319 ExecStartPre=/bin/chown -R pihole:pihole /etc/pihole (code=exited, status=0/SUCCESS)
  Process: 1322 ExecStartPre=/bin/chown pihole:http /etc/pihole/regex.list (code=exited, status=1/FAILURE)

veebr 26 10:28:23 L480 systemd[1]: pihole-FTL.service: Service RestartSec=100ms expired, scheduling restart.
veebr 26 10:28:23 L480 systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
veebr 26 10:28:23 L480 systemd[1]: Stopped Pi-hole FTLDNS engine.
veebr 26 10:28:23 L480 systemd[1]: pihole-FTL.service: Start request repeated too quickly.
veebr 26 10:28:23 L480 systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
veebr 26 10:28:23 L480 systemd[1]: Failed to start Pi-hole FTLDNS engine.

also there is no such file as /etc/pihole/regex.list

ehm, what?

Please rename the tarball so it has pkgname in the filename. Thanks.

@ilcavero uhmm, i think the reason is: it's a mistake!! i will add them ASAP...