## 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.