The Fix
pip install redis==7.1.0
Based on closed redis/redis-py issue #3694 · PR/commit linked
Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.
@@ -1042,6 +1042,7 @@ class ConnectionPool:
is specified. Use :py:class:`~redis.UnixDomainSocketConnection` for
unix sockets.
+ :py:class:`~redis.SSLConnection` can be used for SSL enabled connections.
Any additional keyword arguments are passed to the constructor of
Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: This fix is not applicable if the library version does not support SSLConnection.\n\n
Why This Fix Works in Production
- Trigger: Documentation Wrong: Redis-py 6.2.0 ssl=True does not exist (Named in documentation), it became connection_class=redis.SSLConnection
- Mechanism: Adds documentation to clarify the use of the SSLConnection class for SSL-enabled connections in the Redis connection pool.
- Why the fix works: Adds documentation to clarify the use of the SSLConnection class for SSL-enabled connections in the Redis connection pool. (first fixed release: 7.1.0).
- If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.
Why This Breaks in Prod
- Production symptom (often without a traceback): Documentation Wrong: Redis-py 6.2.0 ssl=True does not exist (Named in documentation), it became connection_class=redis.SSLConnection
Proof / Evidence
- GitHub issue: #3694
- Fix PR: https://github.com/redis/redis-py/pull/3710
- First fixed release: 7.1.0
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.95
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.60
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“Hi @EverybodyGetsHurt, thanks for bringing this to our attention! We will update the docs soon.”
“Hi @EverybodyGetsHurt, The ssl option is available during client initialization in both the sync and async clients, so the documentation for client setup is correct”
Failure Signature (Search String)
- Documentation Wrong: Redis-py 6.2.0 ssl=True does not exist (Named in documentation), it became connection_class=redis.SSLConnection
- I've been busy for a week to try and deploy Redis memorystore in google cloud, with AUTH+SSL, and using it from an App Engine.
Copy-friendly signature
Failure Signature
-----------------
Documentation Wrong: Redis-py 6.2.0 ssl=True does not exist (Named in documentation), it became connection_class=redis.SSLConnection
I've been busy for a week to try and deploy Redis memorystore in google cloud, with AUTH+SSL, and using it from an App Engine.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
Documentation Wrong: Redis-py 6.2.0 ssl=True does not exist (Named in documentation), it became connection_class=redis.SSLConnection
I've been busy for a week to try and deploy Redis memorystore in google cloud, with AUTH+SSL, and using it from an App Engine.
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install redis==7.1.0
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/redis/redis-py/pull/3710
First fixed release: 7.1.0
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix is not applicable if the library version does not support SSLConnection.
Did This Fix Work in Your Case?
Quick signal helps us prioritize which fixes to verify and improve.
Prevention
- Add a TLS smoke test that performs a real handshake in CI (include CA bundle validation and hostname checks).
- Alert on handshake failures by error string and endpoint to catch cert/CA changes quickly.
Version Compatibility Table
| Version | Status |
|---|---|
| 7.1.0 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.