Hi,
I'm using pihole installed in an proxmox lxc container. everything worked fine so far until the last update. went from:
Core 6.0.6 -> 6.1
Web 6.1 -> 6.2.1
FTL 6.1 -> 6.2
functionality works
Web should open
functionally, still works
Can't connect to the web admin panel
https://tricorder.pi-hole.net/ne5nO0sq/
Thank you for the help
Looks like FTL has crashed:
-----tail of FTL.log------
2025-05-31 20:19:38.427 EEST [456M] INFO: FTL user: started as pihole, ended as pihole
2025-05-31 20:19:38.427 EEST [456M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 20:19:38.427 EEST [456M] INFO: Process details: MID: 456
2025-05-31 20:19:38.427 EEST [456M] INFO: PID: 456
2025-05-31 20:19:38.427 EEST [456M] INFO: TID: 456
2025-05-31 20:19:38.427 EEST [456M] INFO: Name: pihole-FTL
2025-05-31 20:19:38.427 EEST [456M] INFO: Received signal: Segmentation fault
2025-05-31 20:19:38.427 EEST [456M] INFO: at address: 0x7f7a979a61fb
2025-05-31 20:19:38.427 EEST [456M] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2025-05-31 20:19:38.427 EEST [456M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-05-31 20:19:38.427 EEST [456M] INFO: ------ Listing content of directory /dev/shm ------
2025-05-31 20:19:38.427 EEST [456M] INFO: File Mode User:Group Size Filename
2025-05-31 20:19:38.427 EEST [456M] INFO: rwxrwxrwx root:root 360 .
2025-05-31 20:19:38.428 EEST [456M] INFO: rwxr-xr-x root:root 480 ..
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 786K FTL-456-recycler
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 4K FTL-456-dns-cache-lookup
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 20K FTL-456-domains-lookup
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 4K FTL-456-clients-lookup
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 569K FTL-456-fifo-log
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 4K FTL-456-per-client-regex
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 20K FTL-456-dns-cache
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 8K FTL-456-overTime
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 4M FTL-456-queries
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 29K FTL-456-upstreams
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 348K FTL-456-clients
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 70K FTL-456-domains
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 123K FTL-456-strings
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 144 FTL-456-settings
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 328 FTL-456-counters
2025-05-31 20:19:38.428 EEST [456M] INFO: rw------- pihole:pihole 88 FTL-456-lock
2025-05-31 20:19:38.428 EEST [456M] INFO: ---------------------------------------------------
2025-05-31 20:19:38.428 EEST [456M] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-05-31 20:19:38.428 EEST [456M] INFO: Thank you for helping us to improve our FTL engine!
2025-05-31 20:19:38.428 EEST [456M] INFO: PID file emptied
We are investigating similar reports.
Had the same issue today. My pihole installation runs on Debian 12 (baremetal) and has a changed port (8080) in /etc/pihole/pihole.toml (also runs OMV on port 80). Worked just fine until today thow. I also verified that the port was still set to 8080 in pihole.toml, that was not the issue.
Long story short: I uninstalled pihole, rebooted the server and reinstalled pihole. After that, I changed the pihole webserver back to port 8080, rebooted the machine and pihole was back up and running, the web interface was accessible again with http://server-ip:8080/admin/ - was much faster than check dozends of forum posts, all in all may be 10 minutes or so. The server is a Ryzen 3 2200G based machine, so not that slow.
Of course I needed to reimport the Teleporter backup.
Ah almost forgot to mention, that the DNS resolution was not working while pihole was faulty. I had to set the DNS server back to the router temporarily.
Same problem here.
I've repeatedly tried installing Pi-Hole v6.1 on a Raspberry Pi 3B+ running a fresh installation of OS Bookworm with no luck. The Pi-Hole install seems to complete without obvious errors, but FTL fails to run and I can’t bring up the web console.
Previously I had Pi-Hole v6.0.6 running fine on the same Pi, but with RPi OS Bullseye.
I'm looking forward to a fix.
This is basically where I am at. In addition, the web monitor on my computer shows TWO data streams. My mental capacities are failing (I am over 80) and I am having difficulty putting together a description as a starting point.
Hi,
and me too...
After updating to the last version, no access to the admin page is possible. Id would be nice if anyone could tell me what to do now.
Thanks!
https://tricorder.pi-hole.net/YNIhXbyJ
I had the same problem after upgrading to FTL 6.2.1.. Resetting FTL using the following worked for me
sudo service pihole-FTL stop
sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db
sudo service pihole-FTL start
Thanks a lot, it's working again. This was the solution.
Thanks, will try that if I have the same issue in the future. However reinstalling did the trick, too - but that's expected since it removed the database, too 
Today there was an update and guess what: exactly the same issue! But stopping FTL, deleting the database and starting the service fixed it. All settings where still there. I think I add the database deletion to my update shell script (updates debian + OpenMediaVault and pihole) as a precautional maintenance.
service pihole-FTL stop
rm -f /etc/pihole/pihole-FTL.db
service pihole-FTL start
Today's update:
Core v6.1.1
FTL v6.2.1
Web interface v6.2.1
