Unable login into admin panel

[agentsas]

This is a: Run Issue (running Pi-hole container failing),

Details

Related Issues

• I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

1. Environment data

• Operating System: Ubuntu
• Hardware: Rock 5b
• Kernel Architecture: ArmV8 64bit
• Docker Install Info and version:
  • Software source: official docker-ce
  • Version: 2025.03.0
• Hardware architecture: aarch64

2. docker-compose.yml contents

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      # DNS Ports
      - "533:53/tcp"
      - "533:53/udp"
      # Default HTTP Port
      - "80:80/tcp"
      # Default HTTPs Port. FTL will generate a self-signed certificate
      - "443:443/tcp"
      # Uncomment the below if using Pi-hole as your DHCP Server
      #- "67:67/udp"
      # Uncomment the line below if you are using Pi-hole as your NTP server
      #- "123:123/udp"
    environment:
      # Set the appropriate timezone for your location from
      # https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g:
      TZ: 'Europe/Kaliningrad'
      # Set a password to access the web interface. Not setting one will result in a random password being assigned
      # If using Docker's default `bridge` network setting the dns listening mode should be set to 'all'
      FTLCONF_dns_listeningMode: 'all'
    # Volumes store your data between container upgrades
    volumes:
      # For persisting Pi-hole's databases and common configuration file
      - './data:/etc/pihole'
      # Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards. Needs environment variable FTLCONF_misc_etc_dnsmasq_d: 'true'
      #- './etc-dnsmasq.d:/etc/dnsmasq.d'
    restart: unless-stopped

3. on login form submit getting this response

{
    "session": {
        "valid": false,
        "totp": false,
        "sid": null,
        "validity": -1,
        "message": "no SID provided"
    },
    "took": 2.47955322265625e-05
}

These common fixes didn't work for my issue

• I have tried removing/destroying my container, and re-creating a new container
• I have tried fresh volume data by backing up and moving/removing the old volume data
• I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
• I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
• I have tried running without my volume data mounts to eliminate volumes as the cause

[crispybegs]

# Set a password to access the web interface. Not setting one will result in a random password being assigned

shouldn't you have a password in your compose?

environment:
      TZ: 'Europe/Kaliningrad'
      FTLCONF_webserver_api_password: 'your_password_here'
      FTLCONF_dns_listeningMode: 'all'

[agentsas]

I tried setting it to a custom value and getting a random password from the logs. In both case i've got this message

[rdwebdesign]

Please post a debug token:

• run docker exec -it <Pi-hole container name> pihole -d command.
• when asked to upload the log, answer Y.
• copy only the token and paste here.

[agentsas]

https://tricorder.pi-hole.net/PrbuShj5/

[rdwebdesign]

Which URL are you using to access the web interface?

• http://<host_machine_IP>/admin ?
• https://<host_machine_IP>/admin ?

Also, do you see the same issue if you try to connect using a different browser or a different device?

[agentsas]

Looks like problem present in Google Chrome, my version 133.0.6943.142 (Official Build) (64-bit)
I tried both
http://<host_machine_IP>/admin
https://<host_machine_IP>/admin

In Microsoft Edge i can login

[agentsas]

I use IP to access lan resources
Cookie name SID intersects with cookie from qBittorrent v5.0.4 WebUI

[PromoFaux]

Ah, here you go - cookies are unique to domain/IP but not port.

Try accessing via http://pi.hole/admin

[agentsas]

pi.hole resolves to internal docker address and is inaccessible
Should i change container network mode to host ?

nslookup.exe pi.hole
Server:  UnKnown
Address:  192.168.1.32

Name:    pi.hole
Address:  192.168.64.2

[PromoFaux]

Ah, OK - that's fine you can set two options in your compose file:

• FTLCONF_dns_reply_host_force4: true
• FTLCONF_dns_reply_host_IPv4: '[whatever your IP address is here]'

They could also be set in the web interface - but I find envvars a better way to ensure consistency