Package Details: pi-hole-server 5.18.3-4

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

Dependencies (18)

Required by (2)

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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 82 Next › Last »

max.bra commented on 2021-04-23 15:26 (UTC) (edited on 2021-04-23 15:30 (UTC) by max.bra)

@steadybright just tested: ookla speedtest.
pihole disabled, vivaldi no block: ads loaded
pihole enabled, vivaldi no block: ads NOT loaded

max.bra commented on 2021-04-23 15:23 (UTC)

@steadybright do you have any dns cache system in your machine? systemd dns stub?
or your browser do something you don't consider? for example: my vivaldi let me see ads only shutting down tracking service...

steadybright commented on 2021-04-23 15:16 (UTC) (edited on 2021-04-23 15:16 (UTC) by steadybright)

@max.bra thanks for the quick response. I updated to the latest (aur/pi-hole-server 5.3.1-2); however, now I can't seem to get pi-hole to filter. Everything is getting through. I confirmed that my DNS server is set to the pi-hole-server machine again. Re-booted the server and my local machine (from which I'm browsing). Could be my issue, but not sure what else to check. Oh, and I cleared my browser cache.

max.bra commented on 2021-04-23 14:41 (UTC) (edited on 2021-04-23 14:51 (UTC) by max.bra)

ok, found it. releasing ASAP.

max.bra commented on 2021-04-23 14:36 (UTC)

mmmh, there something wrong with 'pihole restartdns reload'...

max.bra commented on 2021-04-23 13:29 (UTC) (edited on 2021-04-23 14:04 (UTC) by max.bra)

@steadybright thanks for reporting. same here.
BLOCKING_ENABLED=true/false into /etc/pihole/setupVars.conf is correctly updated.
somebody else?

steadybright commented on 2021-04-22 15:13 (UTC) (edited on 2021-04-22 15:14 (UTC) by steadybright)

About a week ago, I noticed that when I disabled pi-hole via its web UI, pi-hole was still blocking sites as if it had not been disabled. There is no indication of failure in the web UI. It seems as if pi-hole believes it's disabled, but it is not. This happens whether I select Disable "Indefinitely," "For 5 minutes," "Custom time," etc.

Steps to reproduce the behavior:

  1. Go to 'http://<pihole_lan_ip>:808/admin/index.php'
  2. Login to the Web UI
  3. Click on 'Disable'
  4. Select any Disable option ("Indefinitely," "For 5 minutes," "Custom time," etc.)
  5. Observe "Enable(<COUNTDOWN>)" is active and counting down
  6. Try to open a blocked domain
  7. Observe that the domain is still blocked
  8. There is no error message. Pi-hole seems to think it's working as expected

max.bra commented on 2021-03-24 22:13 (UTC)

@jeffmikels no, the problem is in validIP($address) function that (in PHP8) will prevent insertion of v6_1 and v6_2 values at lines 181 and 184.
But believe me, with incoming pi-hole version 6, correcting it it's a complete waste of time.

jeffmikels commented on 2021-03-24 22:02 (UTC)

Making DNS Settings page compatible with PHP8...

in file /srv/http/pihole/admin/scripts/pi-hole/php/savesettings.php, replace two for loops...

details can be seen in my pull request here:

https://github.com/pi-hole/AdminLTE/pull/1774/commits/317a96a64365cfe797d4208ab87307b369b63f08

jeffmikels commented on 2021-03-24 21:51 (UTC)

php-fpm (8) behind nginx prevents access to the /etc/ directory entirely even when the web interface uses the pihole command line script!

My solution was to move /etc/pihole to /home/pihole and then create a symlink back to /etc/pihole.

Everything seems to be working from the web ui now.