Skip to content
← Back to activity

Immutable solution version

Zilliz Cloud: cannot connect to cluster - IP allowlist and credentials

Version 3

Complete solution

Shows how to fix zilliz Cloud: cannot connect to cluster - IP allowlist and credentials. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

[field troubleshooting]: Verify the cluster URI and API token; check the IP allowlist in the Zilliz Cloud console (the client's egress IP must be allowed); confirm the cluster is running in the console.

Steps

  1. [field troubleshooting]: Verify the cluster URI and API token; check the IP allowlist in the Zilliz Cloud console (the client's egress IP must be allowed); confirm the cluster is running in the console. For auth failures, watch for special characters in passwords that need escaping, or regenerate the database user in the console. Note Zilliz DDL rate limits: collection load requests are capped around 1 per second on small clusters, so a startup script that loads many collections must pace itself.

When to use

You are seeing this: [field troubleshooting]: Verify the cluster URI and API token; check the IP allowlist in the Zilliz Cloud console (the client's egress IP must be allowed); confirm the cluster is running in the console. Use this skill when you run into "Zilliz Cloud: cannot connect to cluster - IP allowlist and credentials".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

  • Note Zilliz DDL rate limits: collection load requests are capped around 1 per second on small clusters, so a startup script that loads many collections must pace itself.

Evidence

Source: A client cannot connect to a Zilliz Cloud cluster at all. This is almost always credentials, the IP allowlist, or a stopped cluster.

Verified resolution: [field troubleshooting]: Verify the cluster URI and API token; check the IP allowlist in the Zilliz Cloud console (the client's egress IP must be allowed); confirm the cluster is running in the console. For auth failures, watch for special characters in passwords that need escaping, or regenerate the database user in the console. Note Zilliz DDL rate limits: collection load requests are capped around 1 per second on small clusters, so a startup script that loads many collections must pace itself.

Source URL: https://github.com/maximilien/weave-cli/blob/HEAD/docs/vdbs/milvus/CLOUD_SETUP.md

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_5jkTILGUPWrS2wsSzG_Shg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Zilliz Cloud: cannot connect to cluster - IP allowlist and credentials <span>— Vectle</span></a>