'Do I need to add or rule or add Redis to VNet in Azure?
I enabled VNet integration on an Azure App Service and now when I attempt to connect to Redis, I receive this error message. However, I can connect without issues using Another Redis Desktop Manager.
"No connection is available to service this operation: It was not
possible to connect to the redis server(s); ConnectTimeout; IOCP:
(Busy=0,Free=1000,Min=2,Max=1000), WORKER:
(Busy=5,Free=32762,Min=2,Max=32767), Local-CPU: n/a
Do I need to add a rule to the VNet to allow the connection to Redis or does Redis need to be on the same VNet?
Currently, I'm using a Standard version in Azure and looks like I would need to create a new instance with Premium.
Solution 1:[1]
To resolve this "No connection is available to service this operation: It was not possible to connect to the redis server(s); ConnectTimeout error, try the following ways:
Downgrade
StackExchange.Redistov2.1.58Use the
Primary connection string (StackExchange.Redis)from Azure Access Keys as the parameter toConnectionMultiplexer.Connect()instead of creating aConfigurationOptionsparameter using the Endpoint and Password separately.If you are using a secure TLS connection set the
ssl=True,sslprotocols=tls12in your configuration to the latest version.
You can refer to RedisConnectionException: No connection is available to service this operation
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 |
