I have followed just about every other thread on changes to regain access to pihole admin page but none have worked so far. Not sure what else to try any help would be appreciated.
You have FTL running on the normal ports.
[✓] tcp:0.0.0.0:443 is in use by pihole-FTL
[✓] tcp:0.0.0.0:80 is in use by pihole-FTL
[✓] tcp:0.0.0.0:53 is in use by pihole-FTL
[✓] tcp:[::]:443 is in use by pihole-FTL
[✓] tcp:[::]:80 is in use by pihole-FTL
What is the complete URL you are using to access the Pi-hole web admin GUI?
Did you try from a different device or using a different browser?
Same here, just update the latest version and can't access (insert password and nothing happens)
I can access it via the pihole app on iphone but no luck with any browsers
You probably have a different issue.
https://discourse.pi-hole.net/t/psa-ftl-v6-2-ftl-v6-2-1-crashes-workaround/80339/2
1 Like
I don't think so... All is working properly, but I can't access the Admin page.
This is my log file (Docker container)
[i] Setting up user & group for the pihole user
[i] PIHOLE_UID not set in environment, using default (1000)
[i] PIHOLE_GID not set in environment, using default (1000)
[i] Starting FTL configuration
[i] Assigning password defined by Environment Variable
[i] Starting crond for scheduled scripts. Randomizing times for gravity and update checker
[i] Ensuring logrotate script exists in /etc/pihole
[i] Gravity migration checks
[i] Existing gravity database found - schema will be upgraded if necessary
[i] pihole-FTL pre-start checks
[i] Setting capabilities on pihole-FTL where possible
[i] Applying the following caps to pihole-FTL:
* CAP_CHOWN
* CAP_NET_BIND_SERVICE
* CAP_NET_RAW
[i] Starting pihole-FTL (no-daemon) as pihole
[i] Version info:
Core version is v6.1 (Latest: N/A)
Web version is v6.2.1 (Latest: v6.2.1)
FTL version is v6.2 (Latest: v6.2.1)
2025-06-03 19:34:37.223 CEST [52M] INFO: ########## FTL started on PiHole! ##########
2025-06-03 19:34:37.223 CEST [52M] INFO: FTL branch: master
2025-06-03 19:34:37.223 CEST [52M] INFO: FTL version: v6.2
2025-06-03 19:34:37.223 CEST [52M] INFO: FTL commit: d7ec012f
2025-06-03 19:34:37.223 CEST [52M] INFO: FTL date: 2025-05-30 22:56:39 +0100
2025-06-03 19:34:37.223 CEST [52M] INFO: FTL user: pihole
2025-06-03 19:34:37.223 CEST [52M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-06-03 19:34:37.502 CEST [52M] INFO: 1 FTLCONF environment variable found (1 used, 0 invalid, 0 ignored)
2025-06-03 19:34:37.502 CEST [52M] INFO: [✓] FTLCONF_webserver_api_password is used
2025-06-03 19:34:37.506 CEST [52M] INFO: Wrote config file:
2025-06-03 19:34:37.506 CEST [52M] INFO: - 155 total entries
2025-06-03 19:34:37.506 CEST [52M] INFO: - 145 entries are default
2025-06-03 19:34:37.506 CEST [52M] INFO: - 10 entries are modified
2025-06-03 19:34:37.506 CEST [52M] INFO: - 0 entries are forced through environment
2025-06-03 19:34:37.563 CEST [52M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-06-03 19:34:37.563 CEST [52M] INFO: PID file does not exist or not readable
2025-06-03 19:34:37.563 CEST [52M] INFO: No other running FTL process found.
2025-06-03 19:34:37.563 CEST [52M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2025-06-03 19:34:37.565 CEST [52M] INFO: PID of FTL process: 52
2025-06-03 19:34:37.567 CEST [52M] INFO: listening on 0.0.0.0 port 53
2025-06-03 19:34:37.567 CEST [52M] INFO: listening on :: port 53
2025-06-03 19:34:37.576 CEST [52M] INFO: PID of FTL process: 52
2025-06-03 19:34:37.576 CEST [52M] WARNING: chmod(/etc/pihole/pihole-FTL.db, 416): Verification failed, 33279 != 416
2025-06-03 19:34:37.590 CEST [52M] INFO: Database version is 21
2025-06-03 19:34:37.591 CEST [52M] INFO: Database successfully initialized
2025-06-03 19:34:43.761 CEST [52M] INFO: Imported 26848 queries from the on-disk database (it has 4136148 rows)
2025-06-03 19:34:43.761 CEST [52M] INFO: Parsing queries in database
2025-06-03 19:34:43.827 CEST [52M] INFO: 10000 queries parsed...
2025-06-03 19:34:43.906 CEST [52M] INFO: 20000 queries parsed...
2025-06-03 19:34:43.947 CEST [52M] INFO: Imported 26848 queries from the long-term database
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Total DNS queries: 26848
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Cached DNS queries: 15510
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Forwarded DNS queries: 7094
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Blocked DNS queries: 4036
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Unknown DNS queries: 0
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Unique domains: 2011
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Unique clients: 14
2025-06-03 19:34:43.947 CEST [52M] INFO: -> DNS cache records: 512
2025-06-03 19:34:43.947 CEST [52M] INFO: -> Known forward destinations: 2
2025-06-03 19:34:47.624 CEST [52M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available
2025-06-03 19:34:47.624 CEST [52/T91] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
2025-06-03 19:34:47.624 CEST [52/T92] INFO: NTP server listening on :::123 (IPv6)
2025-06-03 19:34:47.624 CEST [52M] INFO: FTL is running as user pihole (UID 1000)
2025-06-03 19:34:47.624 CEST [52M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-06-03 19:34:47.625 CEST [52M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-06-03 19:34:47.626 CEST [52M] INFO: Web server ports:
2025-06-03 19:34:47.626 CEST [52M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2025-06-03 19:34:47.626 CEST [52M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2025-06-03 19:34:47.626 CEST [52M] INFO: - [::]:80 (HTTP, IPv6, optional, OK)
2025-06-03 19:34:47.626 CEST [52M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK)
2025-06-03 19:34:47.641 CEST [52M] INFO: Restored 5 API sessions from the database
2025-06-03 19:34:47.693 CEST [52M] INFO: Blocking status is enabled
2025-06-03 19:34:47.786 CEST [52/T93] INFO: Compiled 2 allow and 0 deny regex for 14 clients in 42.7 msec
The OP debug log shows no Pi-hole issues and the phone app is connecting.
This shows FTL is running and the API is also working, so the web server seems to be working as expected.
Looks like this is a local network issue.
If you are sure this is the same issue, then check your local network.
If you prefer, you can open a new topic with a debug token. This will give us more information to work.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.