The Fix
pip install celery==4.4.0rc5
Based on closed celery/celery issue #4812 · 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%.
@@ -107,6 +107,7 @@ have been moved into a new ``task_`` prefix.
``CELERY_REDIS_PASSWORD`` :setting:`redis_password`
``CELERY_REDIS_PORT`` :setting:`redis_port`
+``CELERY_REDIS_BACKEND_USE_SSL`` :setting:`redis_backend_use_ssl`
``CELERY_RESULT_BACKEND`` :setting:`result_backend`
``CELERY_MAX_CACHED_RESULTS`` :setting:`result_cache_max`
Option A — Upgrade to fixed release\npip install celery==4.4.0rc5\nWhen NOT to use: This fix is not applicable if using a non-SSL Redis connection.\n\n
Why This Fix Works in Production
- Trigger: Update documentation for Redis Broker SSL
- Mechanism: Documentation did not include proper configuration details for SSL connections with Redis as a broker
- Why the fix works: Updated documentation for Redis Broker SSL to include proper configuration details. (first fixed release: 4.4.0rc5).
- 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
- Documentation did not include proper configuration details for SSL connections with Redis as a broker
- Production symptom (often without a traceback): Update documentation for Redis Broker SSL
Proof / Evidence
- GitHub issue: #4812
- Fix PR: https://github.com/celery/celery/pull/5387
- First fixed release: 4.4.0rc5
- Reproduced locally: No (not executed)
- Last verified: 2026-02-09
- Confidence: 0.85
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.56
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“@clokep I tried that as well celery is not able to recognize rediss:// and i believe it is still in development and will be available…”
“Hello, Could you please help me with this issue, consumer: Cannot connect to redis: Error while reading from socket: (104, 'Connection reset by peer'), My…”
“@nmakarun I believe you have to use rediss (with an extra "s" at the end).”
“@thedrow I am not sure what RC means and I am fairly new to celery.Could you please let know how to fix the url to…”
Failure Signature (Search String)
- Update documentation for Redis Broker SSL
- According to https://github.com/celery/celery/issues/4792#issuecomment-396744283 , the documentation regarding SSL connections when Redis is used as a broker should probably be
Copy-friendly signature
Failure Signature
-----------------
Update documentation for Redis Broker SSL
According to https://github.com/celery/celery/issues/4792#issuecomment-396744283 , the documentation regarding SSL connections when Redis is used as a broker should probably be updated to include the proper configuration details.
Error Message
Signature-only (no traceback captured)
Error Message
-------------
Update documentation for Redis Broker SSL
According to https://github.com/celery/celery/issues/4792#issuecomment-396744283 , the documentation regarding SSL connections when Redis is used as a broker should probably be updated to include the proper configuration details.
What Broke
Users experienced connection errors when attempting to use SSL with Redis broker.
Why It Broke
Documentation did not include proper configuration details for SSL connections with Redis as a broker
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install celery==4.4.0rc5
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/celery/celery/pull/5387
First fixed release: 4.4.0rc5
Last verified: 2026-02-09. Validate in your environment.
When NOT to Use This Fix
- This fix is not applicable if using a non-SSL Redis connection.
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 |
|---|---|
| 4.4.0rc5 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.