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.152279
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 2 3 4 5 6 7 8 9 .. 82 Next › Last »

deemon commented on 2024-01-04 09:35 (UTC) (edited on 2024-01-04 09:37 (UTC) by deemon)

@max-bra found solution -- edited the previous post. same workstation. apparently Steam expects your own computer to do some DNS caching(?), but when you run your pi-hole in the same computer, pi-hole is the thing that will catch all the queries in the first place? Just in case made a bugreport to steam-for-linux github also for excessive DNS queries.

max.bra commented on 2024-01-04 09:06 (UTC)

@deemon seems to be related to some rate limit problem... No clue on why your steam is able to generate this... It seems like a DOS attack!! :-)
Anything particular in your setup? Is pi-hole on a different box or is in your workstation?

deemon commented on 2024-01-04 08:48 (UTC) (edited on 2024-01-04 09:32 (UTC) by deemon)

Found the reason for the pihole going wrong. When I start downloading new game with Steam, it manages to overwhelm pi-hole and stops functioning for everything. If the game is big enough, it crashes pihole several times after being reset. For downloading now 47GB of elden ring has caused it to crash 5 times at least and it's still 51% done still.

Apparently there's workaround to increase or remove (set 0/0) the RATE_LIMIT from default 1000/60, which you can do in /etc/pihole/pihole-FTL.conf

deemon commented on 2024-01-02 11:45 (UTC) (edited on 2024-01-02 12:26 (UTC) by deemon)

Last week pihole has started stop functioning (like 3rd time now) -- no DNS service working at all. Restarting the service has fix it. While it has been "stuck", pihole status still reports everything fine:

  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)

  [✓] Pi-hole blocking is enabled

However when you look into pihole -t you see MASSIVE spam of this nonsense:

Jan  2 13:38:30: query[A] google2.cdn.steampipe.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting google2.cdn.steampipe.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache8-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache8-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache8-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache8-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache8-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache8-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[AAAA] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[AAAA] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[AAAA] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[AAAA] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache1-sto2.steamcontent.com from 127.0.0.1
Jan  2 13:38:30: config error is REFUSED (EDE: blocked)
Jan  2 13:38:30: Rate-limiting cache1-sto2.steamcontent.com is REFUSED (EDE: blocked)
Jan  2 13:38:30: query[A] cache1-sto2.steamcontent.com from 127.0.0.1

max.bra commented on 2023-11-06 09:09 (UTC)

@smaxer maybe FTL is killed by some out of memory cleaner?

smaxer commented on 2023-11-02 23:52 (UTC)

No, basically just the same messages as coming from pihole-FTL.service

max.bra commented on 2023-10-31 11:29 (UTC)

hi smaxer, FTL relevant syslog/journal?

smaxer commented on 2023-10-31 06:20 (UTC) (edited on 2023-10-31 06:23 (UTC) by smaxer)

Pihole doesn't start correctly anymore on my machine. I can open the web interface but no data is shown. When I look into to logs the last line after (Finished config file parsing) is always truncated in the date sections.

Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] ########## FTL started on home! ##########
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] FTL branch: master
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] FTL version: v5.23
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] FTL commit: builtfromreleasetarball
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] FTL date: 2023-05-28
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] FTL user: pihole
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] Compiled for x86_64 (compiled locally) using cc (GCC) 13.2.1 20230801
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.431 4064M]    SOCKET_LISTENING: only local
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.432 4064M]    AAAA_QUERY_ANALYSIS: Show AAAA queries
[...]
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.433 4064M]    CHECK_LOAD: Enabled
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.433 4064M]    CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.433 4064M]    CHECK_DISK: Warning if certain disk usage exceeds 90%
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:00:42.433 4064M] Finished config file parsing
Oct 31 07:00:42 home pihole-FTL[4064]: [2023-10-31 07:0

Port 53 is used by pihole but is unresponsive (timeout) I tried to replace all my config files start from scratch and recompiled each package newly but didn't solve the issue - any ideas? Thanks!

max.bra commented on 2023-10-10 20:11 (UTC) (edited on 2023-10-10 20:11 (UTC) by max.bra)

@2-d in fact it is the root of the problem: they have renamed the AdminLTE project to web. fixed w/o release bump.
@2-d @grappas you can update your installation now and thanks for reporting.

2-d commented on 2023-10-10 19:15 (UTC)

@max.bra

Thanks for the update - this worked for me. I also had to change the wwwpkgname from AdminLTE to web.

_wwwpkgname=web