-
-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login loop #1615
Comments
Possibly a duplicate of #1614 ... What browser are you using? Can you try logging in with the browser's developer tools open, and see if anything unusual shows up? Can you also try opening in incognito/private browsing mode, and try another browser if possible. |
Same issue here, on following branches:
Tried on
same issue on all. |
Found a work-around on the new/FTL_is_my_home branch of AdminLTE: usually, you would log on by going to pi.hole:8080/admin, in which case the error occurs. However, when you just go to pi.hole/admin, the problem does not occur! Afterwards, you can just add :8080 and the interface is functional. Hope this helps pinpoint the cause / solution! |
Just FYI regards |
Absolutely aware of that, just thought it might be of help to you guys 👍 |
I'm using Firefox on a Mac. But I've also tried on Safari on iPhone 12 - same issue. |
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. |
Versions
Platform
Expected behavior
Expected: Login process works and takes me to the dashboard
Actual behavior / bug
When I try to log in, I insert my password but I'm taken back to the login screen. If I insert an incorrect password, the error message appears that the password is incorrect.
Steps to reproduce
Steps to reproduce the behavior:
Go to admin page, try to log in
Debug Token
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
See attached zip with a video of the bug
Screen Recording 2020-10-27 at 8.16.50 pm.mov.zip
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: