'Microsoft.Cache' 502 Bad Gateway

Hi Mikael Jansson •,

Welcome to Microsoft Q&A forum.

As I understand, you are getting 'Microsoft.Cache' 502 Bad Gateway in Azure cache for Redis.

This looks like Network issue.

If you have a firewall configured for your Azure Cache For Redis, ensure that your client IP address is added to the firewall rules. You can check Firewall on the Resource menu under Settings on the Azure portal.

When you use a third-party firewall or proxy in your network, check that the endpoint for Azure Cache for Redis, *.redis.cache.windows.net, is allowed along with the ports 6379 and 6380. You might need to allow more ports when using a clustered cache or geo-replication.

If you've configured any networking or security resource to use your cache's public IP address, check to see if your cache's public IP address changed. For more information, see Rely on hostname not public IP address for your cache.

OR

Sometimes, your cache undergoes a planned or an unplanned server maintenance. Your application can be negatively affected during the maintenance. You can validate by checking the Errors (Type: Failover) metric on your portal. To minimize the effects of failovers, see Connection resilience.

Please let us know your existing cache configuration and result after checking above.

Awaiting your reply.

Thanks