Repository navigation
[Bug]: ioredis is IPv4 only, add IPv6 support #15290
Copy link
Copy link
Open
Labels
🐛 bugSomething isn't workingSomething isn't working🗺️ Backend Infracodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Backend Platformcodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Cache & Storagecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Concurrency Cachecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Platform Securitycodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
Description
Activity
I've opened the PR for this: #15309
Sets on the shared ioredis options in — the resolver tries IPv4 first, then IPv6, so IPv6-only clusters connect while IPv4 behavior is unchanged. Applied to both single-node and cluster clients.
Reacted by Nicholas Dziuba- added🗺️ Concurrency Cachecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
on Sep 24, 2026 - added🗺️ Backend Platformcodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Cache & Storagecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Backend Infracodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
on Oct 1, 2026 - added a commit that references this issue
on Oct 5, 2026 - added🗺️ Platform Securitycodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
on Oct 9, 2026
Metadata
Metadata
Assignees
Labels
🐛 bugSomething isn't workingSomething isn't working🗺️ Backend Infracodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Backend Platformcodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Cache & Storagecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Concurrency Cachecodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)🗺️ Platform Securitycodegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)codegraph: the taxonomy area this belongs to (classifier, confidence ≥ 0.9)
What happened?
ioredisdefaults to IPv4. On an IPv6 single-stack cluster this causesENOTFOUNDbecause the Redis service has no A record. Allow either addressfamily so REDIS_URI-based connections can resolve IPv6-only services.
Changing
Redis.defaultOptions.family = 0allows for both.My current workaround is:
Version Information
Current Version
Steps to Reproduce
Start Librechat against a Redis DNS Record without an A Record.
What browsers are you seeing the problem on?
No response
Relevant log output
Screenshots
No response
Code of Conduct