Hi, I have created a POC project to verify the singalR issue with multiple instace in azure and the POC is working fine with microsft signalR but in asp net zero application it is not working correctly.If you need I can share the POC project
Hi, our production application is running in release mode and I am 100% sure that AddAzureSignalR is executed
Hi @ismcagdas I have configured like this
#if DEBUG services.AddSignalR(); #else services.AddSignalR(options => { options.EnableDetailedErrors = true; }) .AddAzureSignalR(options => options.Endpoints = new ServiceEndpoint[] { new ServiceEndpoint(_appConfiguration["SignalR:PrimaryConnectionString"], EndpointType.Primary, "primary--signalrservice.service.signalr.net"), new ServiceEndpoint(_appConfiguration["SignalR:SecondaryConnectionString"], EndpointType.Secondary, "secondary-signalrservice.service.signalr.net"), });
#endif
Hi @ismcagdas We already using the Azure SignalR Service service but still we are getting the same issue
What is your product version? 11.0.0
What is your product type (Angular or MVC)? Angular
What is product framework type (.net framework or .net core)? .NET 6
Hi, We are using microsoft signalR service for real time communication, but the service wont work if we scale out the app service instance from one to two instance, while using single instacne it is working fine. for exp : Ideally the SignalR connection is established with the instance1. But the request API went to the other app service instance2. The instance2 won't be able to send this message because this specific server connection is not associated with it.
Please help us to resolve that issue we are created the ticket for the same in microsoft and ans was "With this, root cause of the issue is identified, and this issue is expected behavior as per your architecture/application design"
Thanks
What is your product version? 11.0.0
What is your product type (Angular or MVC)? Angular
What is product framework type (.net framework or .net core)? .NET 6
Hi, we are using azure front door to minmize the latency issue in our application but after enable the front door we found that front door is trying to access the URL HEAD /Ui/Login which basiclly return 405. You can see the application insights failure of last 6 hours where HEAD /Ui/Login is failing a alot. Can you help me to fixed that issue.
Thanks
Hi @ismcagdas, is there any update on the issue , and also yestarday I have sended you memory dump file via email so that it would help you guys to identiy the issue of high CPU usage
HI @ismcagdas any update on the issue
Hi @ismcagdas, sure will do it and send you in email
Hi @ismcagdas Yes, we are allowing user to access there tenant which they mapped with there custom domain
