Package Details: pi-hole-standalone 5.1.2-1

Git Clone URL: https://aur.archlinux.org/pi-hole-standalone.git (read-only, click to copy)
Package Base: pi-hole-standalone
Description: The Pi-hole is an advertising-aware DNS/Web server. Arch alteration for standalone PC.
Upstream URL: https://github.com/pi-hole/pi-hole
Keywords: ad block pi-hole
Licenses: EUPL-1.1
Conflicts: pi-hole-server
Submitter: max.bra
Maintainer: max.bra
Last Packager: max.bra
Votes: 4
Popularity: 0.104109
First Submitted: 2016-01-13 12:39
Last Updated: 2020-09-04 18:18

Pinned Comments

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

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

1 2 3 4 5 Next › Last »

max.bra commented on 2020-09-04 18:19

@sjakub sorry for time wasting. should work now.

sjakub commented on 2020-09-03 04:31

I am getting this error while installing this package:

==> Generating initial block list, please wait...
/opt/pihole/webpage.sh: line 27: /etc/.pihole/automated install/basic-install.sh: No such file or directory
/opt/pihole/webpage.sh: line 210: valid_ip: command not found
/opt/pihole/webpage.sh: line 210: valid_ip6: command not found
error: command failed to execute correctly

max.bra commented on 2020-09-01 12:59

hi deemon, yes you can delete those files. left .list files in use are: adlists custom and local.

deemon commented on 2020-09-01 12:29

pacdiff says that there is new /etc/dnsmasq.d/01-pihole.conf.pacnew with gravity.list and black.list removed (compared to current/previous config). Are they no longer needed? can I delete then those .list files also? I assume yes, as I see there new gravity.db side-by-side with the (old?) gravity.list which I assume is the replacement, but just to be sure, asking this.

max.bra commented on 2020-05-09 12:55

this need to be posted to pihole-FTL

it needs a recompilation

dixi_minga commented on 2020-05-09 11:37

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

max.bra commented on 2020-02-26 10:05

@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.

deemon commented on 2020-02-26 09:01

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.

deemon commented on 2020-02-26 08:52

Thanks. Now works :-)

max.bra commented on 2020-02-26 08:44

hi deemon, try now