Milvus Connection Refused / Timeout (19530)
Workaround available Docker, Windows, Linux, macOS Updated November 15, 2026Based on 3 user reportsHow we research
Quick answer
The server is not running, not ready or the port is blocked. Start it, publish 19530 and wait until healthy.
Most likely fix: Check the server
How to fix it
Try these in order — the most common fix is first.
1. Check the server
- Run docker ps and confirm Milvus is up
- Inspect logs for etcd or storage errors
Did this fix it?2. Publish and open the port
- Run with -p 19530:19530
- Open 19530 (gRPC) and optionally 9091 (HTTP) in the firewall
Did this fix it?3. Connect correctly
- MilvusClient(uri="http://localhost:19530")
- On Windows use Docker Desktop with WSL 2
Did this fix it?
Symptoms
Fail connecting to server on localhost:19530. Timeout; connection refused.
Why it happens
- Container stopped or still starting
- Port 19530 not published
- Firewall blocks remote access
- Wrong URI
This guide also covers
- milvus connection refused
- milvus connect timeout 19530
Still not working?
If Milvus keeps failing, you're not alone. See every Milvus 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 Milvus errors
- Milvus "collection not loaded" Error
- Milvus Query Node Out of Memory (OOM)
- Milvus "field dimension mismatch" Error
- Milvus etcd and MinIO Dependency Errors
- Why Is Milvus Search Slow?
- Milvus "index not exist" Error
- Milvus Search Returns Empty Results After Insert
- How to Cancel Zilliz Cloud (Milvus) Subscription