Hello,
I am receiving a 'Could not find localization source: AbpWeb' warning/error when impersonating a user on the console (which appears with an Internal Server Error popup).
This error:
- Appears on the environments that were deployed via Openshift, however, I cannot reproduce it on my local machine.
- Doesn't appear consistently when I impersonate a user, nor does it happen to the same user(s) I impersonate.
- Sometimes also occurs when returning back to the main account.
- Can be reproduced on both Edge and Chrome, as well as using an InPrivate session in Edge.
- Can be reproduced by users who have not recently logged into the application on our environments also can reproduce this error.
- Doesn't stop me from actually impersonating a user - I am able to still go through with the impersonation successfully and return back to the main account.
The website logs and audit logs both show the same error: 'Abp.UI.UserFriendlyException: Impersonation token is invalid or expired!', which traces back to the ImpersonationManager.GetImpersonatedUserAndIdentity method.
We have tried:
- Cleared our browsers and cache
- Cleared the AbpToken table
- Redis was turned off, so that was turned on again and our environments were restarted
Additionally, we recently did an update, and this error appears for the environments that were updated from ASP.Net Zero version 11.1.0 to ASP.Net Zero version 13.0.0, and cannot be reproduced on an environment that uses the old application version, which uses ASP.Nero Zero version 11.1.0.
Using ASP.Net Zero version 13.0.0, using Angular and .NET Core.
Any advice on how to address the error?
Thank you in advance.
2 Answer(s)
-
0
Hi,
Do you host a single instance of your app or multiple instances ? If it is multiple instances, please take a look at https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Clustered-Environment
-
0
Hi,
Do you host a single instance of your app or multiple instances ? If it is multiple instances, please take a look at https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Clustered-Environment
We were able to sort out the issue - there was a duplicate call being made which appeared when we upgraded our application from ASP.Net Zero v11 to v13.
Thank you for the reply!
