Package Details: pi-hole-web 6.5-1

Git Clone URL: https://aur.archlinux.org/pi-hole-web.git (read-only, click to copy)
Package Base: pi-hole-web
Description: Pi-hole Dashboard for stats and more.
Upstream URL: https://github.com/pi-hole/pi-hole
Licenses: EUPL-1.2
Submitter: max.bra
Maintainer: fabi
Last Packager: fabi
Votes: 5
Popularity: 1.31
First Submitted: 2025-02-21 17:04 (UTC)
Last Updated: 2026-04-10 09:09 (UTC)

Dependencies (0)

Sources (1)

Pinned Comments

max.bra commented on 2025-02-21 21:44 (UTC)

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 Next › Last »

fabi commented on 2026-04-09 13:27 (UTC)

Seems to be. But in my opinion the patch could simply be removed for the web part. The only thing it does is, replacing the urls, pointing to the github releases with links to the aur, which are broken anyway, as the js code adds the version at the end (e.g. https://aur.archlinux.org/packages/pi-hole-web/6.4.1).

If no one objects, I could change the pkgbuild and update it to 6.5.

tavianator commented on 2026-04-08 15:47 (UTC)

Looks like https://github.com/max72bra/pi-hole-web-archlinux-customization is gone?

sterni1971 commented on 2025-10-27 20:20 (UTC) (edited on 2025-10-27 20:21 (UTC) by sterni1971)

The Validating of source files arch-web-6.3-1.patch FAILED. I change PKGBUILD

$ diff PKGBUILD.orig PKGBUILD
23c23
<             'e6eb3b4c3e2e87eb1ae6ee939e41b8ed2324dddae9659fca283c1654c2ef3507')
---
>             '5678a1a5668c98d8d0b3f0fc9696c32f08172cd546934c4cd5bf2a67bf732171')

javallone commented on 2025-10-27 18:11 (UTC)

The checksum for arch-web-6.3-1.patch is failing.

graysky commented on 2025-06-10 17:15 (UTC)

So I figured out both problems. The issue is that I am running pihole in a container (lxc) using the overlayfs clone of a base system. /etc/pihole/versions is set in the base system upon installation but it seems to also be updated when pihole-FTL is started which creates a copy that overrides the base system's copy in the overlayfs in the container. I need to dig deeper to understand why it is updated by the service.

The breakage in the webclient was also due to a copy of /var/www/html/admin/scripts/js/index.js in the container. Once I removed that, the base lxc's version was allowed to get read and everything worked.

graysky commented on 2025-06-07 13:57 (UTC)

No, the version strings are still not updated.

max.bra commented on 2025-06-07 12:33 (UTC) (edited on 2025-06-07 12:34 (UTC) by max.bra)

||| It seems like a problem accessing the FTL DB...

Yes, but why only in this very latest version??

I ask myself questions... :-D O_o

max.bra commented on 2025-06-07 12:31 (UTC) (edited on 2025-06-07 12:32 (UTC) by max.bra)

It seems like a problem accessing the FTL DB...
Did you solve the problem of a few weeks ago where your versions file was not updated by the installation/update procedure?
Maybe it's all related...

graysky commented on 2025-06-07 11:49 (UTC)

Clearing cache had no effect. Confirmed on multiple browsers (chromium, firefox on linux) and safari on iOS.

https://i.postimg.cc/MpWMWKsJ/blank.jpg

1 2 3 Next › Last »