- Joined
- Jul 14, 2022
- Messages
- 1
- Reaction score
- 1
Hi there,
Has anybody experienced a problem logging in after the latest update?
Automatic update is turned on in our instance and it auto-updated recently.
A prompt also showed up on our user clients (web/app) asking them if they want to refresh because there is an update. If the user selects yes, the user will not be able to log in again.
I have checked the console logs and network tab of the browser and it looks like it is returning an error 401 after the token has been received. It is not because of an incorrect password because it says on the login page if the username and password are incorrect. This issue doesn't show any error on the webpage.
I have attached screenshots for more info.
1st screenshot is when you try to log in with an incorrect password. Of course, the user won't be able to obtain a token so it returned error 401.
2nd screenshot is with the correct credentials. As you can see, it was able to obtain a token but I think when it is trying to validate the token, it is getting error 401.
Has anybody experienced a problem logging in after the latest update?
Automatic update is turned on in our instance and it auto-updated recently.
A prompt also showed up on our user clients (web/app) asking them if they want to refresh because there is an update. If the user selects yes, the user will not be able to log in again.
I have checked the console logs and network tab of the browser and it looks like it is returning an error 401 after the token has been received. It is not because of an incorrect password because it says on the login page if the username and password are incorrect. This issue doesn't show any error on the webpage.
I have attached screenshots for more info.
1st screenshot is when you try to log in with an incorrect password. Of course, the user won't be able to obtain a token so it returned error 401.
2nd screenshot is with the correct credentials. As you can see, it was able to obtain a token but I think when it is trying to validate the token, it is getting error 401.