webui not accepting my password

[ainelpb]

using this docker compose i cant login on webui

services:
pihole:
container_name: pihole
image: pihole/pihole:latest
ports:
- "53:53/tcp"
- "53:53/udp"
- "8800:80/tcp"
- "4443:443/tcp"
volumes:
- ./etc-dnsmasq.d:/etc/dnsmasq.d
- ./etc-pihole:/etc/pihole
environment:
- FTLCONF_webserver_api_password=myP@ssW0rd
- TZ=America/Chicago
- FTLCONF_dns_listeningMode=all
cap_add:
- SYS_TIME
- SYS_NICE
labels:
- "com.centurylinklabs.watchtower.enable=false"
restart: unless-stopped

networks:
default:
external: true
name: docker_network

[rdwebdesign]

Your real password probably has some special characters like $, `, *, ?, #, etc.

Try to put the password inside single quotes to prevent shell substitution or parameter expansion:

        environment:
            - FTLCONF_webserver_api_password='myP@ssW0rd'

Or you can try to use yaml syntax instead of shell syntax:

        environment:
            FTLCONF_webserver_api_password: 'myP@ssW0rd'

[Arciteck]

Same issue for me. If I enter an incorrect password, it actually tells me its incorrect, however if I input the correct password, the page just reloads and prompts for a login again.

[dhjensen]

Exact same experience for me until I opened the web UI(localhost) in incognito mode.
Turns out if I delete the cookie for the site the login works

[rdwebdesign]

Maybe we have 3 completely different issues.

@ainelpb

You only said you can't login, but you didn't give any details.

Does the page reloads after enter the password?
Do you see any error messages?
Can you login if you delete cookies and clear your browser cache?
Did you fix your issue (you never returned after my previous comment)?

@Arciteck

Are you using a reverse proxy?

@dhjensen

If you can login after deleting cookies, you probably had a different issue (just a browser issue) and now it is fixed. Did it happen again after cleaning the cookies?

[Arciteck]

@rdwebdesign, no reverse proxy here, however I've switched browser and tried to login, and it worked. How strange.

I just did a little more investigating/testing while typing this, and deleted the SID cookie from the original browser, and tried to login again, and it worked.

If its any help, I had previously installed pi-hole and never really got that far in setting it up (though I had managed to login), as my router was being awkward so I removed it. I've since got a new router, and re-added pi-hole to try again, and that's when I ran into the issue of not being able to login.

[dhjensen]

@dhjensen

If you can login after deleting cookies, you probably had a different issue (just a browser issue) and now it is fixed. Did it happen again after cleaning the cookies?

@rdwebdesign
Not had any problems since then... had some issues configuring the container initially... most likely related
Sounds like mine and Arciteck's issues is the same or similar

[ainelpb]

I commented line
#- FTLCONF_webserver_api_password=myP@ssW0rd
I blanked password using terminal and then I could log in

[rdwebdesign]

OK.

@Arciteck and @dhjensen:
Cleaning the cookies solved the problem. I think the problem was just a local browser issue.
Feel free to report back if the issue happens again, but apparently there is nothing wrong on the Pi-hole side.

@ainelpb:

I blanked password using terminal and then I could log in

Apparently your issue is different, but we can't be sure.

If you still want to try setting a password, please first delete Pi-hole cookies just to make sure this is not a browser issue, then try using a simple password (using only letters and digits) to make sure the compose file is working.

I still think your issue is related to my first comment (possibly shell expansion issues). If you can login using a simple password, then you can add a complex password, but make sure to use quotes.

[Pi-Mania]

Just had this issue with docker instance. For me, removing special characters in the FTLCONF_webserver_api_password solved it after 2 hours of misery.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.