And I would fire you myself. This is not a notmal; employee behavior. No one wants you,Update : Actually it rebooted with no problems. Win for Linux lol.,It's a retry mechanisme ! Ahahaha,@Chewbanacas Oh yes, lol. When you just get a white page, you F5, still a white page, well, you notice.
Except for users who, by chance, were on a non-loaded server, and they were like, "Everything is fine!",@retoor Outbound yes, but not "calls."
Connections.
So when a user connects to the platform, there is 1 connection created from the platform to the API server (I simplify a bit). During this user's usage (any API calls), everything goes through this 1 channel.
The limit was 128 channels opened, not 128 parallel requests.
The RIGHT solution is " Only have 1 chanel for ALL connected users.,@iSwimInTheC Brief version, very simplified:
`services.AddScoped<HttpClient>()`
Vs what it SHOULD BE:
`services.AddSingleton<HttpClient>()`,@retoor Ok, I simplified a lot.
‘Connection’ in this context is an outbound SNAT connection, which is different from opening a socket.
SD, even if our “blazor” server and “ApiServer” are both living inside the same Azure subscription, they use outside connection, which is limited.
More info:
https://learn.microsoft.com/en-us/...,Did they fix it?
