Qdrant Connection Refused (localhost:6333 / Docker)
Ongoing Docker, Linux, macOS, Windows Updated November 14, 2026Based on 4 user reportsHow we research
Quick answer
Connection refused usually means the container is not running, the ports are not published, or your app uses the wrong host. Check the health endpoint, publish 6333 and 6334, and use the service name inside Docker Compose.
Most likely fix: Check Qdrant is up
How to fix it
Try these in order — the most common fix is first.
1. Check Qdrant is up
- Run docker ps and look for the qdrant container
- Run curl http://localhost:6333/healthz
- Read docker logs <container> for startup panics
Did this fix it?2. Publish both ports
- Start with docker run -p 6333:6333 -p 6334:6334 qdrant/qdrant
- In Compose, add both ports mappings
Did this fix it?3. Fix the hostname
- Inside Docker Compose use http://qdrant:6333, not localhost
- On Mac/Windows try 127.0.0.1 instead of localhost
Did this fix it?4. Force REST or raise the timeout
- QdrantClient(url=..., prefer_grpc=False)
- QdrantClient(..., timeout=60) for slow operations
Did this fix it?
Symptoms
Python client or curl fails with "connection refused" or a timeout when connecting to Qdrant on localhost:6333.
Why it happens
- Container not running or crashed on startup
- Port 6333 (REST) or 6334 (gRPC) not published with -p
- App running in another container using localhost instead of the Qdrant service name
- Client using gRPC (port 6334) while only 6333 is open
- Large existing dataset delaying startup by tens of seconds
This guide also covers
- qdrant connection refused
- qdrant docker connection refused localhost 6333
- qdrant timeout python client
Still not working?
If Qdrant keeps failing, you're not alone. See every Qdrant problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
Other Qdrant errors
- Qdrant "Wrong input: Vector dimension error: expected dim, got"
- Qdrant "Not found: Collection doesn't exist" Error
- Qdrant Out of Memory (OOMKilled / High RAM Usage)
- Why Is Qdrant Search Slow? HNSW, Quantization and Segment Settings
- Qdrant Free Cluster Suspended or Deleted After Inactivity
- Qdrant Snapshot Restore Failed
- How to Cancel Qdrant Cloud and Delete a Cluster