I updated my Pi this morning, and everything else seems to be working fine but Pi-hole has stopped blocking ads.
After trying some things out (like pihole -r, uninstalling and reinstalling, changing settings on the admin site, using both eth0 and wlan0) I seem to have made the issues worse because now I can't even access the admin site anymore.
I've kind of lost track of everything that I tested, but I am quite confident I tried all the things I could find on this forum related to my issue but so far with no success.
Expected Behaviour:
I expected ads to be blocked and the admin site to be accessible.
Actual Behaviour:
No ads are being blocked and the admin site is giving me a 403 error.
I hope I made this post in the correct manner. I've been struggling with solving the issue for about 10 hours now and I am coming to the conclusion that I am not capable of solving it by myself. So any help is very much appreciated. Thanks in advance!
Edit: I forgot to mention that the Pi is working just fine. It's only connected to wifi but I can use Kodi for instance. I've rebooted my router and my Pi many times aswell. I haven't changed any router settings.
Blocking works as expected and everything starts normally.
The thing i notice though, is that it's currently answering only queries originating from your wlan0 interface. That means that if you try to access something from a wired device, it will not work as it's not set to allow queries from anything else than queries on wlan0.
That (once we get your admin interface back) can be adjusted either via admin (easy, fast) or via editing the /etc/dnsmasq.d/01-pihole.conf file.
Let's get your admin back up and you can adjust that yourself.
The error seems to be related to permissions and maybe missing files.
I guess it makes sense that the Pi-hole is only answering queries from my wlan0 interface, since nothing is wired except for the router to the box where my ISP brings the internet into my home so to speak. Although now that I think of it, maybe that in itself is an issue. I recall having a tun0 option at some point, but I don't remember if that worked.
Anyway, to answer your question, the output is:
totaal 8
drwxr-xr-x 13 www-data www-data 4096 nov 2 2018 openrsd
drwxr-xr-x 11 www-data www-data 4096 nov 2 2018 pivpn-gui
I had access to the admin site for a minute, but after I rebooted I had the same 403 error again. I ran the pihole -r repair again and I still can't access the admin site.
During the repair process, the only thing that doesn't seem to be correct is the following:
[✗] Backing up index.lighttpd.html
No default index.lighttpd.html file found... not backing up
I have access to the admin site again now after another reboot. This is strange, but I'll take it. The status is 'active' but it's not blocking ads. So I guess it comes down to the DNS settings now. Do I need to put it on "listen on all interfaces"?
When I change my setting to eth0 I can't access the admin site again, so that seems to be taking me a step away from the solution. When I change it back to wlan0 through pihole -r (reconfigure), I still don't have access. Restarted my router, no change... I'll try reinstalling pihole again.