and i can't add adlist i get this error: Error, something went wrong! While preparing statement: no such table: adlist
ver:5.0
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.143133 |
First Submitted: | 2016-01-13 12:50 (UTC) |
Last Updated: | 2024-08-10 12:32 (UTC) |
« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 82 Next › Last »
and i can't add adlist i get this error: Error, something went wrong! While preparing statement: no such table: adlist
ver:5.0
i see this error in settings page https://i.imgur.com/gAzHnqh.png
im not using apache i use lighttpd
ver. 5.0 note: after updating please remember to restart your web server or simply reboot.
for the flag enthusiasts:
1) eventually, the right package to flag is FTL
2) ftl is not outdated, it needs only to be recompiled
It is broken. The binary needs libnettle.so.7, but arch provides libnettle.so.8.
@max.bra Sry didn't see your comment.
This is not outdated, it need recompilation.
@max.bra Oh yeah! Sorry. I misread your comment! Cheers, anyway.
glad you solve. anyway i was not speaking about /etc/resolv.conf... :-D
@max.bra Your suggestion gave me enough information to solve this! Massive thank you.
If you (or anyone) is interested...
I was unable to add the DNSStubListener=no option to /etc/resolv.conf as suggested* because I am using openresolv to manage that file. This is required by netctl which I am using as my network manager.
*EDIT - I misread @max.bra's comment. This was exactly what they were suggesting anyway :-)
I am sure that you probably can get openresolv to add the option, but I couldn't figure out how.
The solution was to instead add DNSStubListener=no to /etc/systemd/resolved.conf. This FINALLY seems to stop the dam thing binding to port 53 on boot, and pihole starts just fine. I note that systemd-resolved is still running (despite me disabling it), but seems to be keeping to itself now. There really is no killing that thing apparently....
Thank you for the help. Nice to get rid of this little paper cut every time I reboot my server.
but... did you
DNSStubListener=no
in your /etc/systemd/resolved.conf?
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.