-
Notifications
You must be signed in to change notification settings - Fork 181
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
[BUG] Unable to access allsky.local with different browser #3730
Comments
Are you entering the "admin" login and "secret" password (or whatever you may have changed it to)? If so, what happens when you try? A screenshot would be nice. Try forcing a refresh in the browsers that don't work via Shift-F5. |
Thank you Eric. I did not know the user/password is browser specific. Although, when I created my ALLSKY OS and had a specific username/password created, and then used my specific browser (Brave) to access allsky.local with my user/password combo it worked. However; as I had stated above, no other browser would work. However/ if using the admin/secret combo in ANY browser, it does work. Appreciate your help! |
The WebUI username and password are NOT browser-specific. It's possible the non-working browsers has the old values cached. |
Keep in mind that "admin" and "secret" let you view the WebUI. You access the Pi itself (e.g., with |
@njrusty, Russ, |
Closing Issue - no response from user in 2 weeks. |
Environment
Bug Description
I reinstalled ALLSKY yesterday. For some reason, I was no longer able to access allsky.local so I decided to reinstall. Got everything up and running and use a specific user/password combination. Using my default web browser (Brave) I was able to access my allsky.local webpage and everything up and running.
However; when I tried to login into my allsky.local using Chrome, Firefox or Edge, the user/password screen appears but it will not allow me access. I definitely am entering my users/password correctly on all screens but these browsers not allowing access.
The text was updated successfully, but these errors were encountered: