Hello.
I'm currently running pihole as a subdomain on my webserver along with pivpn to allow ad blocking no matter my location - My Pi-Hole Web Interface.
Everything was working perfectly, until I updated to the new version of Pihole, now all im getting is an 'index of'
The new web interface doesn't have PHP pages (it uses Lua code) and Apache2 won't be able to execute them. The new web interface uses an embedded web server into FTL and you don't need another web server.
If Apache2 is using port 80, the new Pi-hole web interface was configured to use port 8080.
Ok.. Thank you..
and there is no way to run this on apache2? (avid apache fan) How about nginx? Personally, I don't like lighttpd, but its sounding like the easy and fast way to fix my problems is to just spin up a new server just for pihole.
But honestly, I can do everything from CLI that I could from the pihole web interface. Blocking is currently working and I barely even use the interface. I can us pihole -t to make sure everything is working as it should.
Pi-hole uses its own web server now. It is embedded into pihole-FTL.
I don't know if Apache is capable of running pages written in Lua, but even if it can, I'm not sure how you will be able to make Apache run the code used to directly connect to pihole-FTL internal functions... so the answer is "No. Pi-hole web interface needs the internal web server".