I have the same on one of my instances: removed lighttpd on install and have reset ports to default as above, but no web interface on any combination of http/https and ports...
Debug log: https://tricorder.pi-hole.net/zm22YeF0/
It's just randomly started working...!
You experienced a real crash.
Please post the crash log lines from /var/log/pihole/FTL.log
2025-02-18 21:24:27.447 UTC [454M] ERROR: ERROR: SQL query "DELETE FROM disk.message;" failed: database is locked (SQLITE_BUSY)
2025-02-18 21:24:27.447 UTC [454M] WARNING: Database busy in flush_message_table()!
2025-02-18 21:24:27.723 UTC [454M] INFO: FTL is running as user pihole (UID 998)
2025-02-18 21:24:27.725 UTC [454M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-02-18 21:24:27.725 UTC [454M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-02-18 21:24:27.726 UTC [454M] WARNING: No web server ports configured!
2025-02-18 21:24:27.726 UTC [454/T460] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-18 21:24:27.726 UTC [454/T460] INFO: ----------------------------> FTL crashed! <----------------------------
2025-02-18 21:24:27.726 UTC [454/T460] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-02-18 21:24:27.726 UTC [454/T460] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-02-18 21:24:27.726 UTC [454/T460] INFO: and include in your report already the following details:
2025-02-18 21:24:27.726 UTC [454/T460] INFO: FTL has been running for 27 seconds
2025-02-18 21:24:27.726 UTC [454/T460] INFO: FTL branch: master
2025-02-18 21:24:27.726 UTC [454/T460] INFO: FTL version: v6.0
2025-02-18 21:24:27.726 UTC [454/T460] INFO: FTL commit: eaa7dbb4
2025-02-18 21:24:27.726 UTC [454/T460] INFO: FTL date: 2025-02-18 17:19:26 +0000
2025-02-18 21:24:27.726 UTC [454/T460] INFO: FTL user: started as pihole, ended as pihole
2025-02-18 21:24:27.726 UTC [454/T460] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-02-18 21:24:27.726 UTC [454/T460] INFO: Process details: MID: 454
2025-02-18 21:24:27.726 UTC [454/T460] INFO: PID: 454
2025-02-18 21:24:27.726 UTC [454/T460] INFO: TID: 460
2025-02-18 21:24:27.726 UTC [454/T460] INFO: Name: civetweb-master
2025-02-18 21:24:27.726 UTC [454/T460] INFO: Received signal: Segmentation fault
2025-02-18 21:24:27.726 UTC [454/T460] INFO: at address: 0x4
2025-02-18 21:24:27.726 UTC [454/T460] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2025-02-18 21:24:27.726 UTC [454/T460] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-02-18 21:24:27.726 UTC [454/T460] INFO: ------ Listing content of directory /dev/shm ------
2025-02-18 21:24:27.727 UTC [454/T460] INFO: File Mode User:Group Size Filename
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rwxrwxrwx root:root 360 .
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rwxr-xr-x root:root 480 ..
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 88 FTL-454-lock
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 328 FTL-454-counters
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 144 FTL-454-settings
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 164K FTL-454-strings
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 102K FTL-454-domains
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 348K FTL-454-clients
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 29K FTL-454-upstreams
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 8M FTL-454-queries
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 8K FTL-454-overTime
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 20K FTL-454-dns-cache
2025-02-18 21:24:27.727 UTC [454/T460] INFO: rw------- pihole:pihole 4K FTL-454-per-client-regex
2025-02-18 21:24:27.728 UTC [454/T460] INFO: rw------- pihole:pihole 569K FTL-454-fifo-log
2025-02-18 21:24:27.728 UTC [454/T460] INFO: rw------- pihole:pihole 4K FTL-454-clients-lookup
2025-02-18 21:24:27.728 UTC [454/T460] INFO: rw------- pihole:pihole 29K FTL-454-domains-lookup
2025-02-18 21:24:27.728 UTC [454/T460] INFO: rw------- pihole:pihole 4K FTL-454-dns-cache-lookup
2025-02-18 21:24:27.728 UTC [454/T460] INFO: rw------- pihole:pihole 786K FTL-454-recycler
2025-02-18 21:24:27.728 UTC [454/T460] INFO: ---------------------------------------------------
2025-02-18 21:24:27.728 UTC [454/T460] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-02-18 21:24:27.728 UTC [454/T460] INFO: Thank you for helping us to improve our FTL engine!
2025-02-18 21:24:27.728 UTC [454/T460] INFO: PID file emptied
2025-02-18 21:24:27.728 UTC [454/T460] INFO: Stored 0 API sessions in the database
2025-02-18 21:24:28.728 UTC [454M] ERROR: ERROR: SQL query "DELETE FROM disk.session WHERE valid_until < strftime('%s', 'now');" failed: database is locked (SQLITE_BUSY)
2025-02-18 21:24:28.728 UTC [454M] WARNING: Database busy in restore_db_sessions()!
2025-02-18 21:24:31.813 UTC [454/T455] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2025-02-18 21:24:31.813 UTC [454/T455] INFO: Time offset: 9.976029e-01 ms (excluded 0 outliers)
2025-02-18 21:24:31.813 UTC [454/T455] INFO: Round-trip delay: 1.018274e+01 ms (excluded 0 outliers)
2025-02-18 21:24:31.813 UTC [454/T455] ERROR: Error NTP client: Failed to adjust time during NTP sync: Insufficient permissions
2025-02-18 21:24:32.815 UTC [454/T455] ERROR: add_message(type=13, message=Failed to adjust time during NTP sync: Insufficient permissions) - SQL error step DELETE: database is locked
2025-02-18 21:24:32.815 UTC [454/T455] ERROR: Error while trying to close database: database is locked
2025-02-18 21:24:32.815 UTC [454/T455] INFO: Local time is too inaccurate, retrying in 600 seconds before launching NTP server
2025-02-18 21:25:14.332 UTC [255/T258] ERROR: ERROR: SQL query "DELETE FROM network_addresses WHERE lastSeen < 1732051513;" failed: database is locked (SQLITE_BUSY)
Thanks. We'll come back to you.
Seems to be stable now - let me know if there's any database status I can query.
This means the crash has been caused in the civetweb project we embed. Is there any way you could think of being able to reproduce this? If so, it'd be absolutely fantastic if you could follow gdb - Pi-hole documentation and provide the backtrace information as described there. You can even leave the debugger attached for a long time as it should not affect the performance of your Pi-hole.
I guess I could restore my Proxmox backup and do the upgrade again? I'm not sure at what stage it happened, and might not have investigated further if not for trying to open the web interface...
I'm currently getting no queries on the Pi-hole and the log is full of database errors: don't want to move it in case you need further information here or if related: https://tricorder.pi-hole.net/RbCjQBd6/
Sorry for the delay in replying, pretty much is going on these days here! 
The database issues in the log are "database is busy" which can have a large number of causes.
Could you maybe upload the full logs for me? E.g. using
cat /var/log/pihole/FTL.log | pihole tricorder
cat /var/log/pihole/FTL.log.1 | pihole tricorder
zcat /var/log/pihole/FTL.log.2.gz | pihole tricorder
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.