We discovered a quite bizarre behavior yesterday afternoon on one of our azure app services.
The app loads, gets redirected to our Identity Server and then back to the app and suddenly the app keeps loading forever, leaving every request on pending. Some request get an status code of 200, but no response at all.
We have the very same deployment on different servers (like test, stage, etc.) as every other app service is running normally, which is rather interesting.
We can call our own API via Swagger/Postman without any issue, leaving us with an even bigger question mark.
The negotiate request is for our SignalR service, we already tried to remove it temporarily from our frontend, but it didn't had any impact at all.
Has anyone ever experienced such a behavior?
Tech Stack: Angular, .NET App Service, SignalR, Azure MS SQL
There is a similar topic on the microsoft site, but removing signalr compeltely for testing didn't solve our issue.
We discovered a quite bizarre behavior yesterday afternoon on one of our azure app services.
The app loads, gets redirected to our Identity Server and then back to the app and suddenly the app keeps loading forever, leaving every request on pending. Some request get an status code of 200, but no response at all.
We have the very same deployment on different servers (like test, stage, etc.) as every other app service is running normally, which is rather interesting.
We can call our own API via Swagger/Postman without any issue, leaving us with an even bigger question mark.
The negotiate request is for our SignalR service, we already tried to remove it temporarily from our frontend, but it didn't had any impact at all.
Has anyone ever experienced such a behavior?
Tech Stack: Angular, .NET App Service, SignalR, Azure MS SQL
There is a similar topic on the microsoft site, but removing signalr compeltely for testing didn't solve our issue.
https://learn.microsoft.com/en-us/answers/questions/2144614/app-service-returns-nothing-but-no-changes-done
We found a rather unusual solution. Although no error or warning was logged in Application Insights, a restore of our main database did the trick and solved our issue.
It could be a coincidence or not, but restarting any of the used services didn't solve the issue. Only a full restore of the db solved our problem. We never had such a problem in the past, usually if something is wrong with the db we see it in the logs or some specific requests fail, but never the whole app without any trace.