as the subject already suggests my pihole doesn't working anymore after the update.
More precisely I get a "connection refused" if I want to connect to the web admin interface.
This pihole runs on a raspi 4 8GB with twisterOS.
I already did a debug for this pihole. Please find the token below.
For further information:
I did also an update on my synology docker, where my second pihole runs.
After the update -> recreating the docker container, I ran into the same issue. But in this case, I switched back to the previous (older) container and it works again.
yes, but I changed it to 8888, because of deCONZ/phoscon and it works flawlessly until I updated the pihole to the newest version.
In the meantime, I deactivated deconz completely, but this wasn't the solution.
pihole -d "tells" me that too, that port 80 is now free.
Update:
I found the issue... unfortunately, my /etc/lighttpd/lighttpd.conf was overwritten and the /etc/lighttpd/external.conf was deleted (by the update of the pihole?!) ...
I changed the port of the web admin/server back to 8888 and now it works.
Yes, as clearly indicated in the prominent header in that file:
###############################################################################
# FILE AUTOMATICALLY OVERWRITTEN BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
# #
# CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE: #
# /etc/lighttpd/external.conf #
###############################################################################
Changes to the lighttpd port should be made in the external.conf file, which is not subject to be overwritten by a Pi-hole repair or update.
I didn't dive so deep into it, thats why I couldn't help myself this time.
Thanks again!
But one more question please, are there any known issues with updating the docker container?
I did it now a few times, but it still doesn't work. The container keeps restarting.
It is unfortunately also not possible to do a debug.
You don't use the pihole -up command with a container. You load a new container image that already has the latest version. I believe we have updated the image - @PromoFaux can you confirm?