Redis backplane using connection string doesn't seem to identify the redis endpoints #335
efreeman518
started this conversation in
General
Replies: 2 comments 5 replies
-
Mmh, this is really strange: this is the related line, and I normally use Redis via either the connection string or the multiplexer factory. Can you share the (redacted) connection string you're using? |
Beta Was this translation helpful? Give feedback.
3 replies
-
Yes Azure, public endpoint so no vnets or ip whitelist configured.
Distributed cache seems to work fine, it's only when configuring the
backplane the errors occur.
…On Wed, Nov 27, 2024, 5:41 PM Jody Donetti ***@***.***> wrote:
Ah, it's on Azure: did you allow connections to it? Depending from where
you are connectin from, you may need to enable vnets, specific ips, etc.
Also, only the backplane seems not to work or also the distributed cache?
—
Reply to this email directly, view it on GitHub
<#335 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3S3W7DCQBOKKJSALTAPIT2CZDBVAVCNFSM6AAAAABSTUPR3CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZZHE4DKNI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
.Net 9, latest C#
Have not determined if this is a bug, but watching the VS debug output with FusionCache configured with Redis backplane using the Redis connection string shows the Redis sdk complaining about no endpoints.
Instead of using a connection string, I tried building StackExchange.Redis.ConfigurationOptions, explicitly defining the 'Endpoints' which seems to be working. Code below.
Researching - I came across this article
https://markmcgookin.com/2020/01/15/azure-redis-cache-no-endpoints-specified-error-in-dotnet-core/
Beta Was this translation helpful? Give feedback.
All reactions