503 Service Unavaiable when scaling Azure up or down

Question

User-493622830 posted

We have been using Redis cache for scale out for sometime now well over a year. Our SignalR code hasn't changed for almost as long. About 4 months ago we started getting 503 errors when scaling. 

Not sure what changed that when we scale nodes up or down SingalR often throws Service Unavailable and our clients get a white screen of death.

We upgraded from ver 2.2.0 to 2.2.2 today and it didn't help.

Any help would be appreciated.

Answer 1

User-271186128 posted

Hi inetzombie,

Welcome to asp.net forum.

Which kind of service tiers you are using? Please try to use Standard or Premium tier. It support Staging environments and 99.95% SLA.

If already using Standard or Premium tier and you are using App service, I suggest you could refer to the following articles to troubleshoot the "503 service unavailable" error.

https://docs.microsoft.com/en-us/azure/app-service-web/app-service-web-troubleshoot-http-502-http-503

Best regards,
Dillion