API working RRS feed

  • Question

  • On the console screen of redis cache of azure. I write any syntax to retrieve data, sometimes, i get the following error:

    Connection Failure: If this issue persists, ensure your computer's firewall and proxy settings allow outbound TCP traffic to port 10225. Using the firewall feature on your cache may also block connections from the console if your IP address has not been whitelisted

    Thursday, May 30, 2019 7:12 AM

All replies

  • Hi Naresh,

    I believe you have to add the Portal's IP Address to the Allow List for the firewall of the cache instance. Do you currently have any firewall configuration in place?

    Thank you for any additional information you can provide with regard to behavior and reproducibility.


    Thursday, May 30, 2019 7:25 PM
  • I did some looking around and found the following:

    -They found that you have reached max number of connections because of which you were getting the error. Microsoft won’t be able to kill the connections, you will have to restart the applications that are using it and fix the connection leak.
    -Please refer to the article https://docs.microsoft.com/en-us/azure/azure-cache-for-redis/cache-dotnet-how-to-use-azure-redis-cache<https: ?url="https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fblob%2Fmaster%2Farticles%2Fredis-cache%2Fcache-dotnet-how-to-use-azure-redis-cache.md&data=02%7C01%7Canmaha%40microsoft.com%7C1fbdaa5685604030298008d5d5aec85b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636649869032053880&sdata=Epu6H1WmoRMuyK0q9tCBOndKfaseCSmIKog4kiIdbfA%3D&reserved=0" na01.safelinks.protection.outlook.com="" style="box-sizing:inherit;"> which explains about configuration of Connection Multiplexer
    One approach to sharing a ConnectionMultiplexer instance in your application is to have a static property that returns a connected instance, similar to the following example. This approach provides a thread-safe way to initialize only a single connected ConnectionMultiplexer instance. In these examples abortConnect is set to false, which means that the call succeeds even if a connection to the Azure Redis Cache is not established. One key feature of ConnectionMultiplexer is that it automatically restores connectivity to the cache once the network issue or other causes are resolve
    -I also recommend you to refer to the article: https://gist.github.com/JonCole/925630df72be1351b21440625ff2671f<https: ?url="https%3A%2F%2Fgist.github.com%2FJonCole%2F925630df72be1351b21440625ff2671f&data=02%7C01%7Canmaha%40microsoft.com%7C1fbdaa5685604030298008d5d5aec85b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636649869032063888&sdata=WtiggBuy2koOc8eFUyjVl7zjIvDBtck498rNPL%2FCOUc%3D&reserved=0" na01.safelinks.protection.outlook.com="" style="box-sizing:inherit;"> for best practices for Azure Redis.</https:></https:>

    I hope this helps.

    Friday, May 31, 2019 11:27 PM