Azure Redis Cache connection from .net 4.6.1

[sasankjonna]

I am trying to connect Azure Redis cache from a simple .net 4.6.1 console app and getting the below when I try do StringSet

StackExchange.Redis.RedisConnectionException: 'The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=SET, timeout: 5000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Initializing, in: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 1, serverEndpoint: sjrediscache.redis.cache.windows.net:6380, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: 5CG0251G81(SE.Redis-v2.6.116.40240), IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=0,Free=2047,Min=8,Max=2047), v: 2.6.116.40240 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)'

Here is my code, any suggestions of what can be done?

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12; // Connect to Azure Redis Cache string redisConnectionString = "sjrediscache.redis.cache.windows.net:6380,password=**=,ssl=True,abortConnect=False,sslProtocols=tls12"; redisConnection = ConnectionMultiplexer.Connect(redisConnectionString);

    // Perform operations on Redis Cache
    IDatabase db = redisConnection.GetDatabase();
    string cacheKey = "myKey";
    string cacheValue = "Hello, Redis!";

    // Set a value in the cache
    db.StringSet(cacheKey, cacheValue);

[mgravell]

It never connected. If you take the abortConnect=false away, it might give you an exception that says what failed. Alternatively, pass a something (Console.Out or a StringWriter, typically) into the optional "log" parameter when connecting, and see what it says in the verbose log

[sasankjonna]

It still says the same

The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=SET, timeout: 5000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 1, serverEndpoint: sjrediscache.redis.cache.windows.net:6380, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: 5CG0251G81(SE.Redis-v2.6.116.40240), IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=0,Free=2047,Min=8,Max=2047), v: 2.6.116.40240 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)'

[philon-msft]

If you try explicitly setting abortConnect=true, that may give you a better error message. And if you pass a TextWriter of some kind into the Connect() call, it will receive detailed logs on why the connection is failing.

[sasankjonna]

no luck, plz advice

[sasankjonna]

are there any firewall settings I need to be aware of?

[NickCraver]

@sasankjonna As Philo mentioned you should set abortConnect=true which isn't in your screenshot, and the aoc: 0 in the exception message confirms it's still not true. Still though, you're on a more recent version which is letting us know we simply couldn't connect ("Last Connection Exception: It was not possible to connect to the redis server(s)"), and yep, my money would be on firewall rules here.

[sasankjonna]

This is what I am seeing if I set abortConnect=true

[mgravell]

The abortConnect=true hack can be useful for guarding against transient connection faults, such as "redis server was mostly asleep until we poked it, so the first connect will often time out, but it is there really"; it can't help with fundamental connection problems. Given the mention of net461, I'm thinking "TLS"; I realise your app is net461, but: just while we investigate, is it possible to use the same connect code on net7, just to see if it connects? if net7 connects cleanly, then we can assume that we have working line of sight to the server, which means the difference is something net461-specific (such as: TLS); if net7 doesn't connect cleanly, then we should investigate things like "is the server up", "DNS", "firewalls", etc

[sasankjonna]

this is .net 6

[sasankjonna]

with abortconnect=false I see the below error

Unhandled exception. StackExchange.Redis.RedisConnectionException: The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=GET, timeout: 5000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Idle, in: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 1, serverEndpoint: sjrediscache.redis.cache.windows.net:6380, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: 5CG0251G81(SE.Redis-v2.6.116.40240), IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=0,Free=32767,Min=8,Max=32767), POOL: (Threads=10,QueuedItems=0,CompletedItems=69), v: 2.6.116.40240 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts) ---> StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). ConnectTimeout --- End of inner exception stack trace ---

[mgravell]

Ok, so: probably not TLS; ultimately the client needs to be able to open a connection to the server, and it doesn't look like that's working. The client can't fix network level problems, but if it was me, things I'd try:

• pass in something to the optional "log" parameter of Connect, and read (or tell us here) how far it got - for example whether it connected but couldn't understand the response vs couldn't connect at all
• temporarily enable the non-encrypted endpoint (usually :6379) and use redis-cli (or telnet, at push) to connect and interact with the server (this test ensures that the server is up and DNS / routing work)
• try redis-cli to the encrypted endpoint; I don't expect it to work, but it might help isolate what things do work

[sasankjonna]

I am able to connect and Set/Get values to same Azure redis instance using redis-cli but not from my .net code.

[sasankjonna]

Error :

Unhandled exception. StackExchange.Redis.RedisConnectionException: The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=SET, timeout: 5000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Initializing, in: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 1, serverEndpoint: sjrediscache.redis.cache.windows.net:6379, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: 5CG0251G81(SE.Redis-v2.6.122.38350), IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=0,Free=32767,Min=8,Max=32767), POOL: (Threads=12,QueuedItems=0,CompletedItems=65,Timers=4), v: 2.6.122.38350 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts) ---> StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). ConnectTimeout --- End of inner exception stack trace --- at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor1 processor, ServerEndPoint server, T defaultValue) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 2093 at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor1 processor, ServerEndPoint server, T defaultValue) in //src/StackExchange.Redis/RedisBase.cs:line 62 at StackExchange.Redis.RedisDatabase.StringSet(RedisKey key, RedisValue value, Nullable`1 expiry, Boolean keepTtl, When when, CommandFlags flags) in //src/StackExchange.Redis/RedisDatabase.cs:line 3164 at AzureRedis.Program.Main(String[] args) in C:\Users\Jonnasn1\source\repos\AzureRedis\AzureRedis\Program.cs:line 19

[NickCraver]

@sasankjonna I see in your exception that you're connecting to :6379 but your connection string in earlier screenshots is :6380. Given this is most likely some configuration mismatch, let's be sure to double check your endpoint please.

:6379 is the default for non-SSL, but :6380 is the SSL endpoint.

[sasankjonna]

Yes, initially I tried to connect to 6380. Later I disabled SSL and been trying to connect to 6379. Ofcourse with no luck. Whom to contact for proper support on this?

[NickCraver]

AFAIK, this is normal Azure Portal support path (cc @philon-msft on the routing question) - I have little insight into those paths, just maintain the client as able.

[sasankjonna]

I am really at dead-end coz a simple POC code is not able to connect to Azure Redis.

[philon-msft]

Yes I'd recommend going through 'Help > Support + Troubleshooting' in the Azure Portal

[NickCraver]

@sasankjonna Did you get going here?

[NickCraver]

Closing out to cleanup here

[Mrudula-Nemani]

Error :

Unhandled exception. StackExchange.Redis.RedisConnectionException: The message timed out in the backlog attempting to send because no connection became available (5000ms) - Last Connection Exception: It was not possible to connect to the redis server(s). ConnectTimeout, command=SET, timeout: 5000, inst: 0, qu: 1, qs: 0, aw: False, bw: SpinningDown, rs: NotStarted, ws: Initializing, in: 0, last-in: 0, cur-in: 0, sync-ops: 1, async-ops: 1, serverEndpoint: sjrediscache.redis.cache.windows.net:6379, conn-sec: n/a, aoc: 0, mc: 1/1/0, mgr: 10 of 10 available, clientName: 5CG0251G81(SE.Redis-v2.6.122.38350), IOCP: (Busy=0,Free=1000,Min=8,Max=1000), WORKER: (Busy=0,Free=32767,Min=8,Max=32767), POOL: (Threads=12,QueuedItems=0,CompletedItems=65,Timers=4), v: 2.6.122.38350 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts) ---> StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(s). ConnectTimeout --- End of inner exception stack trace --- at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor1 processor, ServerEndPoint server, T defaultValue) in /_/src/StackExchange.Redis/ConnectionMultiplexer.cs:line 2093 at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor1 processor, ServerEndPoint server, T defaultValue) in //src/StackExchange.Redis/RedisBase.cs:line 62 at StackExchange.Redis.RedisDatabase.StringSet(RedisKey key, RedisValue value, Nullable`1 expiry, Boolean keepTtl, When when, CommandFlags flags) in //src/StackExchange.Redis/RedisDatabase.cs:line 3164 at AzureRedis.Program.Main(String[] args) in C:\Users\Jonnasn1\source\repos\AzureRedis\AzureRedis\Program.cs:line 19

I am also facing the same error, can someone help me how to solve this.

[mgravell]

"It was not possible to connect to the redis server(s)." - I can't solve that from here; you'd need to check:

• is the server running?
• is it running in "protected" mode? i.e. is it accepting external connections?
• does DNS to the server work?
• can the client at the raw level connect to the server?
• do you have the security credentials (if any) correct?
• are you connecting to the correct port, in particular the correct port for your TLS/non-TLS configuration?

The quickest way to answer most of these is to use redis-cli from the intended client machine; can you connect? If you can't connect with redis-cli, all bets are off. Note that if the server is behind TLS, you need to use recent versions of redis-cli, and in particular the long out-of-date Windows port of redis-cli lacks this, IIRC.

It is not sufficient to use redis-cli on the server itself; that misses most of the places things can be broken.