Ends in:
1 DAY
9 HRS
44 MIN
50 SEC
Ends in:
1 D
9 H
44 M
50 S

Activities of "okains"

Hi,

Unfortunately, same AbpRemoteCallException. Ran everything locally, worked fine. I think probably removing the WebAssembly code is the right thing to do, it could cause other problems but unfortunately it didn't help with this one:

Volo.Abp.Http.Client.AbpRemoteCallException: Unauthorized , what is the root cause of this exception ( other than obviously not being properly logged in ) , is there any way to dig into this and determine what we need to look at a bit more closer?

Thanks,

Kariom

OK great, yeah I wasn't sure if you could hear me during the ZOOM call. I was following what you did, makes sense. Let me test this out locally, then deploy to our test environment and I will let you know how it goes.

ok

Hi,

I am in UTC + 6.5, free for the next few hours if you want to send a meeting link. We could try at 12pm my time , 1:30pm your time if that works?

This only occurs in a production environment, locally everything is fine. May be helpful to run through the code though to see if there is anything obvious that could be causing this.

Thanks,

Karim

Hi,

Yes of course, anything you need to do. Though this is deployed to an Azure App Service x 3, Auth / API / Blazor, and that is where I am having the problems. Let me know what you need from me and I will provide to you.

Thanks,

Karim

As discussed, waiting on another support ticket to clear on this then I will run load testing, please keep open just in case these issues occur again during load testing. Once I get through the other support ticket, and the testing, I will close.

Thanks,

Karim

Hi,

Yeah I have already gone through that process. If I comment out that code then it just throws the AbpRemoteCallException : Unauthorized the next time I make a call into the Service layer.

It seems to be logging in / authenticating fine for a period of time, a few seconds, then losing auth. Here is a video showing this:

https://1drv.ms/v/s!AkJmGuHQuob7kqpdeMB_g8HYqKIW_w?e=c8Krme

I don't understand what would cause us to lose authentication after a few seconds like this, that is the original question.

Thanks,

Karim

Hi,

All log levels are at DEBUG. I stopped all 3 services, cleaned out the logs, then re ran all, logged in and got the Auth exception again. Currently the AUTH / API projects are running fine, no errors, just dealing with this UNAUTHORIZED error in the Blazor Project.

Here are the logs from just now:

https://1drv.ms/u/s!AkJmGuHQuob7kqpAq6Pb-Ro49fpzjQ?e=y7mA7e

Thanks,

Karim

Hi,

I have added this code into all 3 projects, still getting the same error as before. Is there anything configuration or db related that would cause this? Any other ideas on a way forward here? I need to demo to our client and this is becoming a serious problem for us now.

I had been travelling last week and wasn't available much but I will be very much available now to implement any and all possible solutions to this quickly.

Thanks,

Karim

Hi,

Sorry for late reply, was travelling. I will add this in and do some further testing, if the db issues are no longer in the logs then that will be great. My only concern is that there is a lot of extra code / configuration to get to this point and that might have other unintended effects. I am going to be doing some heavy load testing on this app next week so I want to make sure we haven't introduced any issues that might come up during testing.

For now please keep this ticket open until I can finish my testing and confirm that things are OK.

Thanks,

Karim

Showing 11 to 20 of 164 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on December 05, 2024, 12:19