Celery RabbitMQ docker instructions: incorrect port number

The Fix

pip install celery==4.4.0rc5

Based on closed celery/celery issue #5593 · PR/commit linked

Production note: This usually shows up under retries/timeouts. Treat it as a side-effect risk until you can verify behavior with a canary + real traffic.

Open PR/Commit

@@ -65,7 +65,7 @@ Or, if you want to run it on Docker execute this:
 .. code-block:: console
 
-    $ docker run -d -p 5462:5462 rabbitmq
+    $ docker run -d -p 5672:5672 rabbitmq

fix.md

Option A — Upgrade to fixed release\npip install celery==4.4.0rc5\nWhen NOT to use: This fix is not applicable if the documentation is not being used for RabbitMQ setup.\n\n

Why This Fix Works in Production

Trigger: RabbitMQ docker instructions: incorrect port number
Mechanism: The documentation incorrectly specified the RabbitMQ port as 5462 instead of the default 5672
Why the fix works: Corrected the RabbitMQ docker instructions by changing the port number from 5462 to 5672. (first fixed release: 4.4.0rc5).

Production impact:

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

The documentation incorrectly specified the RabbitMQ port as 5462 instead of the default 5672
Production symptom (often without a traceback): RabbitMQ docker instructions: incorrect port number

Proof / Evidence

GitHub issue: #5593
Fix PR: https://github.com/celery/celery/pull/5595
First fixed release: 4.4.0rc5
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.75

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“plz review https://github.com/celery/celery/pull/5595”

@auvipy · 2019-06-14 · source

Failure Signature (Search String)

RabbitMQ docker instructions: incorrect port number
- [x] I have included all related issues and possible duplicate issues in this issue

Copy-friendly signature

signature.txt

Failure Signature
-----------------
RabbitMQ docker instructions: incorrect port number
- [x] I have included all related issues and possible duplicate issues in this issue

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
RabbitMQ docker instructions: incorrect port number
- [x] I have included all related issues and possible duplicate issues in this issue

What Broke

Users were unable to connect to RabbitMQ due to incorrect port configuration.

Why It Broke

The documentation incorrectly specified the RabbitMQ port as 5462 instead of the default 5672

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install celery==4.4.0rc5

When NOT to use: This fix is not applicable if the documentation is not being used for RabbitMQ setup.

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/5595

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 the documentation is not being used for RabbitMQ setup.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
4.4.0rc5	Fixed

Related Issues

No related fixes found.

Cluster: celery:configuration-error Celery hub Celery best practices All hubs All clusters

Related clusters: Data consistency Duplicates Duplicate processing

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.

Celery RabbitMQ docker instructions: incorrect port number (Fix)