-
Notifications
You must be signed in to change notification settings - Fork 147
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
cannot log in #346
Comments
|
Did you start on 0.9.0 or 0.8.0? There are changes to the auth collections in 0.9.0, but everything should be migrated automatically. If you can log in to PocketBase, check if there is a user in the users table ( If the Beszel interface shows you logged in but no systems, try logging out and logging back in. |
I'm running into a similar issue but I can't log in anew to the main interface or the dashboard (PocketBase). For the main interface, with my primary browser (Firefox) that I normally have Bezel opened in a tab, I can still access the main interface. However, if I try a different browser (i.e. Brave) or a private window with my main browser, I can't log into the main interface. For the dashboard (PocketBase), I can still access it via a tab I already had opened and logged in on my main browser. However, if I try to open the dashboard in a new tab of my main browser, I can't log in. I also can't log into the dashboard in a private window of my main browser or in a different browser. This all appears to have started since I updated to 0.9.0 several days ago. I tried going back to 0.8.0 as a test but Beszel hub wouldn't start. |
I seem to have fixed my issue but I'm not sure how or why. One thing I did notice is my email notifications weren't working due to a DNS change I made recently. One clue was the I thought that may have been the fix so I reintroduced the issue (i.e. broke email server DNS) to verify, but I was still able to login. So I'm not sure what fixed my issue. |
@sansbyte Strange, I was just typing out a response but looks like it's not applicable anymore. Perhaps it was a token issue and the previous token expired. Or maybe you have rate limits on and the auth rate limit was being exceeded somehow? If anyone still has this issue, try resetting your password. |
I created a user, but I cannot log in, but can log in
/_/#/settings
compose.yml
The
/api/collections/users/auth-refresh
API returns400 Bad Request
, response is:The
/api/realtime
API returns403 Forbidden
, response is:The text was updated successfully, but these errors were encountered: