AUR (en) - pi-hole-server

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: pi-hole-server 5.18.3-4

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:	112
Popularity:	0.49
First Submitted:	2016-01-13 12:50 (UTC)
Last Updated:	2024-08-10 12:32 (UTC)

Dependencies (18)

bc (bc-gh^AUR)
bind-tools (bind-development^AUR, bind-git^AUR, bind)
inetutils (inetutils-git^AUR, busybox-coreutils^AUR)
iproute2 (iproute2-git^AUR, busybox-coreutils^AUR, iproute2-selinux^AUR)
jq (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 (procps-ng-git^AUR, busybox-coreutils^AUR)
sudo (fake-sudo^AUR, polkit-fakesudo^AUR, sudo-git^AUR, doas-sudo-shim^AUR, doas-sudo-shim-minimal^AUR, sudo-hg^AUR, sudo-selinux^AUR, fudo-git^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 .. 60 61 62 63 64 65 66 67 68 69 70 .. 82 Next › Last »

ChuckHL commented on 2017-06-29 01:01 (UTC)

I found a possible bug on the latest version 3.1-5. It seems that any domain added to the blacklist is not being blacklisted and is ignored. The problem seems to be that "pihole -g" (or update from the website) no longer pulls the blacklist domains into the gravity.list but rather creates a black.list file which is not added to /etc/dnsmasq.d/01-pihole.conf file.

max.bra commented on 2017-06-28 21:08 (UTC) (edited on 2017-06-29 08:29 (UTC) by max.bra)

@ChuckHL that folder is part of pi-hole git repo since forever but nothing point to it in installation shell script: or is something atavic or something that will be implemented later on...

graysky commented on 2017-06-28 20:59 (UTC)

Does browsing to http://pi.hole/admin not work for others?

ChuckHL commented on 2017-06-28 04:56 (UTC)

I notice that other pihole installation (outside of ArchLinux) create a folder named /etc/.pihole that includes some directory named "block hulu ads" and has some extra files for blocking such ads. Will you include that in the following releases (or is it outside of the scope for you)?

max.bra commented on 2017-06-24 23:07 (UTC) (edited on 2017-06-24 23:44 (UTC) by max.bra)

hi bofslime, thanks for reporting. > sqlite3.c:84551:1: note: here > case OP_AggStep: { > ^~~~ this is pi-hole-FTL compilation: messages like those are compilation warnings and you can ignore them. your system become unresponsive because FTL compilation is rather heavy for an arm processor. it's absolutely normal especially for a monocore cpu. not so normal the error at the end. ChuckHL too was reporting similar compilation error. try to download ftl package snapshot and recompile it or try to crosscompile it (https://wiki.archlinux.org/index.php/Cross-compiling_tools_package_guidelines) with a more powerfull machine.

bofslime commented on 2017-06-24 22:41 (UTC)

Seeing frequent issues when updating pi-hole from the AUR. My system will often become unresponsive when in this state and either have to wait it out, or preemptively have a 2nd session open as it stops accepting new sessions when stalling on building. Often this includes negatively affecting DNS resolution. sqlite3.c:84548:15: warning: this statement may fall through [-Wimplicit-fallthrough=] pOp->opcode = OP_AggStep; ^ sqlite3.c:84551:1: note: here case OP_AggStep: { ^~~~ {standard input}: Assembler messages: {standard input}:147265: Warning: end of file not at end of a line; newline inserted {standard input}:147690: Error: ']' expected -- `ldr r3,[fp,#-1' gcc: internal compiler error: Killed (program cc1) Please submit a full bug report, with preprocessed source if appropriate. See <https://github.com/archlinuxarm/PKGBUILDs/issues> for instructions. make: *** [Makefile:57: obj/sqlite3.o] Error 4 ==> ERROR: A failure occurred in build(). Aborting... The build failed.

max.bra commented on 2017-06-21 06:44 (UTC)

@graysky > Shall we create a wiki page for this package? Created a stub yesterday evening for server and standalone too > recommend you pass the version on to the source: yes nice shot!

graysky commented on 2017-06-20 22:26 (UTC)

@max.bra - recommend you pass the version on to the source: source=(pihole-$pkgver.tar.gz::https://github.com/$_pkgname/$_pkgname/archive/v$pkgver.tar.gz admin-$_wwwpkgver.tar.gz::https://github.com/$_pkgname/$_wwwpkgname/archive/v$_wwwpkgver.tar.gz

graysky commented on 2017-06-20 21:43 (UTC)

@max.bra - I have nginx-mainline working with this package. I will try to write up the steps. Shall we create a wiki page for this package?

graysky commented on 2017-06-20 19:26 (UTC)

@max.bra - I think the best method here is simply to put them in the optdepends array and to provide a template config for each. As well, you give some post-install instructions in /usr/share/doc/pihole/configuration which is the best place in my opinion for this. I recommend that you remove the systemctl calls from the .install files for this and the ftl package. Put the instructions in the configuration docs but never have pacman call systemctl unless data loss will result if you don't do it. I am pretty busy with life right now but I will do my best to help with the documentation and a nginx example config. I just can't devote lots of time to it in the short term.