Package Details: pi-hole-server 3.1.4-6

Git Clone URL: (read-only)
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:
Keywords: ad block pi-hole
Licenses: EUPL-1.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 25
Popularity: 1.668245
First Submitted: 2016-01-13 12:50
Last Updated: 2017-10-13 11:22

Dependencies (10)

Required by (0)

Sources (14)

Latest Comments

max.bra commented on 2017-10-13 11:24

v. 3.1.4-6 - nginx config changed

edit: typo

max.bra commented on 2017-10-09 18:33

well, you can still use the old config file, no problem at all.
or, you can follow the always excellent arch wiki:

BIGFAT commented on 2017-10-09 18:29

Hallo max.bra. Since im a beginner, it would be nice if you can tell me how. I dont know where to put exactly the list. Thank you.

max.bra commented on 2017-10-09 15:55

since it is almost a puddle, i've removed open_basedir directive from lighttpd config example.
pihole needed dirs list is now on the wiki for a rapid personal integration.

max.bra commented on 2017-10-05 20:14

as usual, open_basedir directory missing.
done and thanks for reporting.

be careful, update your lighttpd.conf

tsago commented on 2017-10-05 19:38

I can reproduce BIGFAT's issue on a >fresh< Arch VM, running latest pi-hole-server 3.1.4-3. Using lighttpd for pihole web-interface. Followed setup guide from arch wiki.

GUI -> Settings -> Teleporter -> click on Export
Same error as BIGFAT posted.
Error comes from script /srv/http/pihole/admin/scripts/pi-hole/php/teleporter.phpm line 170. ( )

Sounds like the "http" service user cannot create the temporary zip file? I know nothing about PHP, so I'm hitting a wall here...

edit: works when I change the folder from /tmp to /srv/http/pihole (line 164 of teleporter.php), so I'm pretty sure it's write permissions.
Broken setup on my side? Arch-specific pi-hole issue? General pi-hole issue that should be reported upstream? (I guess they'd notice already if this was issue from upstream)

graysky commented on 2017-10-05 18:40

No issue using nginx here. You haven't provided any level of detail for someone to help you. Also, the AUR isn't the appropriate place for this. Recommend you open a thread on the bbs and provide some details beyond "I can't use it."

BIGFAT commented on 2017-10-05 16:05

Hi, i have a small problem. I cant use the pi-Hole teleporter:
cannot open/create
PHP user: http

Thank you for the good work.

PS: Sorry for not giving details, but yes it was on lighttpd.

max.bra commented on 2017-09-10 19:44

hi tdlk,
especially with the latest package modifications after the arrival of graysky (now the package is freer and less automated, leaving the user many more decisions and configurations) it is not mandatory to use the conf recommended for lighttpd, you can use your config whenever you want.
Inserting open_basedir (in the original project there is no open_basedir directive) wants to give you a little more security handled directly by the maintainers. If one has different needs of course, he must take different paths.

tdkl commented on 2017-09-10 17:46

Can anyone explain me a good reason why open_basedir is defined in lighttpd.conf? Because while it might be fine if you only run pi-hole, it's a PITA if you want to run something else, for example Mediawiki on /mediawiki. Leaving the open_basedir out of lighttpd.conf and entering it in php.ini works for both.

This is the main problem I started to have with pi-hole a while ago - it's assuming it's the only player on ones system and not being a good citizen. It'll probably replace systemd at some point.

All comments