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.134716
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 .. 54 55 56 57 58 59 60 61 62 63 64 .. 82 Next › Last »

graysky commented on 2017-12-11 22:11 (UTC)

@max.bra - You introduced lighttpd.conf with the 3.2-2 commit but you are installing lighttpd.pihole.conf in the PKGBUILD. That first one seems to be unused. They are different from each other.

max.bra commented on 2017-12-11 21:52 (UTC)

@graysky removed -R, my fault...

max.bra commented on 2017-12-11 21:49 (UTC) (edited on 2017-12-11 21:49 (UTC) by max.bra)

@graysky there is no need to recourse all, all other files are sudoed accessed. our /etc/pihole is 755, i know. but my /etc/pihole is always 777 and i don't know why. i have never found a chmod 777 in the project... bah...

graysky commented on 2017-12-11 21:45 (UTC)

@max.bra - I haven't updated to 3.2-2 yet but simply chown pihole:pihole /etc/pihole was all that's needed... the -R switch will make all files under there pihole:pihole when it seems that they should be root:root. Also, my /etc/pihole is 755 not 777.

max.bra commented on 2017-12-11 21:41 (UTC)

@MartB thanks for reporting, patch applied. Changed /etc/pihole ownership too but, as for now, my /etc/pihole directory is always chmodded to 777 by the running pihole...

MartB commented on 2017-12-11 20:18 (UTC) (edited on 2017-12-11 20:34 (UTC) by MartB)

@schmodd apply this patch right after the version.patch file in the pkgbuild.

https://github.com/pi-hole/pi-hole/commit/80e17ab72180f15ac4d5ff0044d4e8eafd95bc29.patch

This will be in the next version for sure and it fixes your issue if you install bind-tools

schmodd commented on 2017-12-11 17:32 (UTC) (edited on 2017-12-11 18:47 (UTC) by schmodd)

Hi, it seems that Pihole 3.2 is working fine so far with one exception: When I try to update my lists (via webinterface - tools) I get:

[✗] DNS resolution is currently unavailable

[✗] DNS resolution is not available

Ok, they got it on the buglist on github already, nothing to do with the package here i guess. SRY.

artafinde commented on 2017-12-09 10:31 (UTC)

@max.bra ping if you need help testing or packaging.

max.bra commented on 2017-12-09 09:50 (UTC)

Hi batal, 3.2 is a big release. I think that the package should be ready for beginning of he week.

batal commented on 2017-12-09 08:35 (UTC)

Hello! I don't want to press or anything, just am excited: Do you have a schedule for version 3.2 yet? Thanks for maintaining the package. I couldn't use Arch if you would not :-)