Milvus Connection Refused / Timeout (19530)

Share
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. 1. Check the server

    1. Run docker ps and confirm Milvus is up
    2. Inspect logs for etcd or storage errors
    Did this fix it?
  2. 2. Publish and open the port

    1. Run with -p 19530:19530
    2. Open 19530 (gRPC) and optionally 9091 (HTTP) in the firewall
    Did this fix it?
  3. 3. Connect correctly

    1. MilvusClient(uri="http://localhost:19530")
    2. 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 us
Fixed it? Share this guide

The same problem in other apps

All not loading, error messages & connection guides →

Other Milvus errors