Package Details: pi-hole-standalone 5.10-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.2
Conflicts: pi-hole-server
Submitter: max.bra
Maintainer: max.bra
Last Packager: max.bra
Votes: 6
Popularity: 1.22
First Submitted: 2016-01-13 12:39 (UTC)
Last Updated: 2022-04-23 09:07 (UTC)

Pinned Comments

max.bra commented on 2018-02-09 16:47 (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

max.bra commented on 2021-02-01 12:18 (UTC)

@ultraquist thanks for reporting. given that this package deserves more love, perhaps it's time to enable the same log rules as the server version. please let me know.

ultraquist commented on 2021-02-01 06:03 (UTC) (edited on 2021-02-01 06:24 (UTC) by ultraquist)

Hi, Sorry if this is a problem on my end or upstream, but logging doesn't seem to be working anymore, using pihole logging on. Issuing pihole -t to view the log tail gives:

  [i] Press Ctrl-C to exit
tail: cannot open '/var/log/pihole.log' for reading: No such file or directory
tail: no files remaining

It seems there has been some deletions to /etc/dnsmasq.d/01-pihole.conf. Adding these lines seems to fix:

log-queries
log-facility=/var/log/pihole.log
log-async

With /var/log/pihole.log existing with pihole:pihole ownership.

I think these lines are necessary, since /usr/bin/pihole just seems to try toggling the commenting on these lines using sed.

deemon commented on 2020-11-19 21:00 (UTC) (edited on 2020-11-19 21:00 (UTC) by deemon)

nov   19 22:52:24 L480 dnsmasq[62483]: bad address at /etc/pihole/adlists.list line 1
nov   19 22:52:24 L480 dnsmasq[62483]: bad address at /etc/pihole/adlists.list line 2
nov   19 22:52:24 L480 dnsmasq[62483]: bad address at /etc/pihole/adlists.list line 3
nov   19 22:52:24 L480 dnsmasq[62483]: bad address at /etc/pihole/adlists.list line 4

what is wrong? I have never done anything to this file.

$ cat /etc/pihole/adlists.list 
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
https://mirror1.malwaredomains.com/files/justdomains
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt

max.bra commented on 2020-10-28 10:07 (UTC)

hi Prakkie, i think you have posted in wrong package. you talk about UI but standalone version has CLI only. anyway, can you please reset your browser cache and continue this discussion in server package?

Prakkie commented on 2020-10-27 23:42 (UTC)

Hi, I am using latest version of this package and using nginx for reverse proxy. All working fine but unable to use UI. I cant do any changes through UI. I tried temporary disabling, changing theme, DNS setting etc.. All options give instant response but when clicked on any other option, it resets. It was working fine till upgrade. Please let me know if I am missing something. Thanks.

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

@sjakub sorry for time wasting. should work now.

sjakub commented on 2020-09-03 04:31 (UTC)

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

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 (UTC) (edited on 2020-09-01 12:40 (UTC) by deemon)

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

this need to be posted to pihole-FTL

it needs a recompilation

dixi_minga commented on 2020-05-09 11:37 (UTC)

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

@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 (UTC)

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

Thanks. Now works :-)

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

hi deemon, try now

deemon commented on 2020-02-26 08:36 (UTC) (edited on 2020-02-26 08:42 (UTC) by deemon)

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

max.bra commented on 2020-02-16 13:58 (UTC)

ehm, what?

MarcinWieczorek commented on 2020-02-16 13:56 (UTC)

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

max.bra commented on 2020-01-15 20:58 (UTC)

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

ilcavero commented on 2020-01-15 19:06 (UTC)

Hi @max.bra, thanks for the package, is there are reason why the chronometer and version scripts are not included?

pihole chronometer and pihole version commands fail due to undefined functions.

max.bra commented on 2019-10-18 23:11 (UTC) (edited on 2019-10-18 23:12 (UTC) by max.bra)

hi coxackie. for standalone version you need, as you said and as you read in the wiki, DNS service and pi-hole blocking enabled AND name resolving pointing to localhost. stop. nothing else.
pihole-FTL.service (since version 4 dnsmasq has been forked and integrated) IS the DNS server service (and a logger not so relevant in standalone version) and it is statically enabled. you need to mask it or it will always start with your system.

coxackie commented on 2019-10-18 15:49 (UTC) (edited on 2019-10-18 15:51 (UTC) by coxackie)

Hi @max.bra, thanks for your work. I have a naive question: how can we check that indeed all is running well? I have installed, not done anything regarding DNS, I run pihole status and get

  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

Does this mean that all is good? Otherwise, could you explain a bit better how to set 127.0.0.1 so it is the only DNS server in use, as the wiki mentions? Is it just a matter of having nameserver 127.0.0.1 in /etc/resolv.conf, or it requires more? Furthermore, does one need to start pihole-FTL.service, or is it optional in case one needs logs?

max.bra commented on 2019-09-17 17:12 (UTC)

hi mborder, try now and thanks for reporting

commented on 2019-09-17 16:33 (UTC)

I'm getting a number of errors with this that I suspect are new as of the most recent update. In the initial installation I get this:

==> Read setup instructions at <https://wiki.archlinux.org/index.php/Pi-hole>
==> Generating initial block list, please wait...
/opt/pihole/webpage.sh: line 299: syntax error near unexpected token `}'
/opt/pihole/webpage.sh: line 299: `}'
/usr/bin/pihole: line 28: main: command not found

Running commands with the pihole utility also seems to have errors

$ pihole status
  [✓] DNS service is running
  [i] Pi-hole blocking will be enabled
/usr/bin/pihole: line 258: /usr/local/bin/pihole: No such file or directory

$ pihole -a
  [✓] Restarting DNS service
/opt/pihole/webpage.sh: line 299: syntax error near unexpected token `}'
/opt/pihole/webpage.sh: line 299: `}'
/usr/bin/pihole: line 28: main: command not found

sonny commented on 2019-07-26 18:43 (UTC) (edited on 2019-07-26 18:46 (UTC) by sonny)

Since everything is pretty much optional in pi-hole-server and from what I can tell there does not seem to be much difference between the two, why not having a single pi-hole package?

It would decrease the burden on you and the users.

Also https://pi-hole.net/2018/10/15/announcing-our-restful-api-contributions-welcome/ will decrease dependencies.

max.bra commented on 2019-07-26 18:37 (UTC)

Absolutely yes. Server package do it and I need to align this package to. As I always said, this package deserve more love.

sonny commented on 2019-07-26 18:32 (UTC)

Okay it's working.

Thanks for the packages and helping out.

I spent a lot of time trying to make this work, wouldn't make more sense to just have pacman do that?

max.bra commented on 2019-07-26 18:22 (UTC)

Don't know why but I missed some wiki modifications: a step is missing. I need to align this installation to the server one. Can you please copy ""/usr/share/pihole/configs/dnsmasq.example.conf" to /etc/dnsmasq.conf and restart ftl?

sonny commented on 2019-07-26 18:05 (UTC)

Okay I just replaced pi-hole-standalone with pi-hole-server to test and it's working. Let me know if I can help debug this somehow.

max.bra commented on 2019-07-26 18:03 (UTC)

With no-resolv directive dnsmasq should not read that file

sonny commented on 2019-07-26 17:55 (UTC)

I did follow the wiki, I don't have systemd-resolved running. As I said, pihole is running and working, tested with

drill @127.0.0.1 TXT archlinux.org

it just seems to stop working as soon as I have nameserver 127.0.0.1 in my /etc/resolv.conf

max.bra commented on 2019-07-26 17:41 (UTC)

Hi sonny. Have you followed the wiki? Is ftl working or stops soon after starting? Nothing about systemd dns stub disabling?

sonny commented on 2019-07-26 16:42 (UTC) (edited on 2019-07-26 16:42 (UTC) by sonny)

Apparently pihole-FTL is reading my /etc/resolv.conf, could it be the problem?

juil. 26 18:41:05 evoli dnsmasq[9452]: reading /etc/resolv.conf
juil. 26 18:41:05 evoli dnsmasq[9452]: using nameserver 192.168.0.1#53

sonny commented on 2019-07-26 16:39 (UTC)

I can't make this work. pihole is started and running (drill @127.0.0.1 TXT archlinux.org works)

I have name_servers=127.0.0.1 in my /etc/resolvconf.conf.

But everytime my /etc/resolv.conf looks like nameserver 127.0.0.1 DNS is not working.

Any idea?

marza commented on 2019-02-22 08:34 (UTC)

Thanks for the fix and updates, everything works flawlessly here :D

max.bra commented on 2019-02-21 22:09 (UTC)

@davvore33 yes dig!! updated w/o version bump. thanks for reporting.

davvore33 commented on 2019-02-21 21:56 (UTC)

this package depends on extra/bind-tools too, please update

max.bra commented on 2019-02-21 16:34 (UTC)

@marza ... and yes, you don't need :

$ pihole -a setdns serv_ip1, serv_ip2, ...

unless you need something other than google DNS servers.

max.bra commented on 2019-02-21 16:28 (UTC) (edited on 2019-02-21 16:32 (UTC) by max.bra)

@marza you are perfectly right! thanks for reporting.

  • pi-hole-ftl.service solved, sorry
  • wiki updated

this package deserves more love!

marza commented on 2019-02-21 15:21 (UTC) (edited on 2019-02-21 15:22 (UTC) by marza)

Update: Adding the dnsmasq.conf file manually with just the single "uncommented" line made everything work!

Except the setdns command, but I didn't really need it for anything but testing if it worked.

Now maybe the wiki entry should be updated to reflect that both versions use pihole-ftl and that the conf file might not be created automatically? And should it be made automatically (why not?), and if so, is this an upstream issue?

marza commented on 2019-02-21 14:42 (UTC) (edited on 2019-02-21 14:43 (UTC) by marza)

Hello, I've tried to get this package working, but I'm having some issues. The wiki entry seems to suggest that you need to configure a line in /etc/dnsmasq.conf, but I've never had dnsmasq on my machine. Looking up at the full version configuration, it mentions that Pi-hole-FTL provides it's own version of dnsmasq now, and will conflict with it. So here's what I've tried so far:

  • Following the wiki instructions for setting up everything except dnsmasq.

  • Openresolv is configured and updated to use 127.0.0.1 as name server.

  • enabling and starting pihole-FTL.service

This makes all lookups fail, and it doesn't seem like pihole is really doing anything.

An interesting fact is that running "pihole -a setdns 8.8.8.8" gives me this error:

[✗] Failed to restart pi-hole-ftl.service: Unit pi-hole-ftl.service not found.

(Yes I was running as root) But as mentioned above, I only have "pihole-FTL.service" and not "pi-hole-ftl.service" on my system. Is this a typo somewhere? And should I create /etc/dnsmasq.conf manually, or should that already be on my system?

max.bra commented on 2019-02-17 09:18 (UTC)

no it's not. description says "alteration".

erkexzcx commented on 2019-02-17 07:19 (UTC)

So basically "pi-hole standalone" is not even a thing in upstream? I am trying to update https://wiki.archlinux.org/index.php/Pi-hole but I am not 100% confident about "pi-hole standalone" due lack of information on Arch Wiki.

max.bra commented on 2019-01-20 22:11 (UTC)

@pepper_chico sorry but i don't see the problem...

pepper_chico commented on 2019-01-20 21:21 (UTC) (edited on 2019-01-20 21:22 (UTC) by pepper_chico)

@max.bra ah ok, many thanks for that explanation. I find it weird though that the wiki states the sky-hole usecase as the origin for pi-hole-standalone, since that usecase is about running it on the cloud, contrary to running it on the go on a laptop. It seems to me the server pkg is more proper for the cloud usecase.

max.bra commented on 2019-01-20 11:40 (UTC)

Hi pepper_chico, of course that the standalone version auto update the blocklist.

this package differs from the server for not having the web interface and an easier configuration since everything happens in localhost. the server version assumes a dedicated device in a LAN and if we talk about a laptop, by exiting the LAN, the advertising blocking service fails. the standalone version is designed to have on your laptop a light version of pihole that follows you and self-manages.

pepper_chico commented on 2019-01-19 23:02 (UTC) (edited on 2019-01-19 23:03 (UTC) by pepper_chico)

The Wiki states "The Arch Linux Pi-hole Standalone variant is born from the need to use Pi-hole services in a mobile context". What does that mean? Specially the "mobile context" part.

I'm trying to understand how this differs from pi-hole-server package. From the "standalone" designation it looks like it's targeted to run and self-update (the blocklist at least)?

I wished a clear explanation of what it provides of different.

max.bra commented on 2018-02-09 16:47 (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.

flying-sheep commented on 2017-12-28 14:35 (UTC)

Hi, whenever I run this, I get:

/usr/bin/pihole: line 15: /opt/pihole/COL_TABLE: No such file or directory

and indeed, the first noncomment lines of /usr/bin/pihole are:

readonly PI_HOLE_SCRIPT_DIR="/opt/pihole" readonly wildcardlist="/etc/dnsmasq.d/03-pihole-wildcard.conf" readonly colfile="${PI_HOLE_SCRIPT_DIR}/COL_TABLE" source "${colfile}"

…while /opt/pihole/ only conteins: gravity.sh list.sh mimic_setupVars.conf.sh webpage.sh