Signal R 502 Bad Gateway

Question

Hi.

After receiving a 502 on a call to SignalR I tried using the Signal R Live Trace Tool on the Azure portal. There, too, I received a 502 immediately upon launching the tool.

How do I start to diagnose this?

Thank you!

Answer 1

@glennoleum We understand you are encountering 502 bad gateway errors on your Azure SignalR service.

502 errors are rather generic so it would be best to enable logging for further diagnostics,
 
if the issue reoccurs again, please enable server side and client side signalR tracing to see if there are more error details logged in during the time of issue. This will help us to find out more details on the issue.
 
To enable server-side logging,
Enable server-side logging for ASP.NET Core SignalR | Microsoft Learn
 
To enable client-side logging
How to enable client-side log | Microsoft Learn

This should provide you greater detail into the errors that you are receiving and assist you to locate the root cause of the 502 errors.

Please share with us the outcome of your logging.