Last post Jun 27, 2017 04:19 AM by Zhi Lv - MSFT
Jun 26, 2017 08:04 PM|inetzombie|LINK
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.
Jun 27, 2017 04:19 AM|Zhi Lv - MSFT|LINK
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%
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.