Can't connect
Quick check
- Is the source reachable? (network)
- Are the credentials right?
- Did anything change? (rotated keys, firewall, network)
Step by step
1. Connection status
| Status | Meaning | Do |
|---|---|---|
| Connected | working | the issue is elsewhere |
| Connecting | retrying | wait, then retry |
| Error | failed | check the details below |
| Disconnected | not attempting | check configuration |
2. Credentials
- Live device: the host/connection string is complete; the credential has the access it needs; the key hasn't been rotated out from under it (rotate with the secondary to avoid downtime).
- API Source: the endpoint is correct; the auth (Bearer/API key/basic) is set; the token hasn't expired. Credentials changed in your cloud won't sync automatically - update them on the connection.
3. Network
| Symptom | Cause | Do |
|---|---|---|
| timeout | firewall blocking | allow outbound HTTPS (443) |
| connection refused | port blocked | confirm the port is open |
| SSL error | certificate | check TLS settings |
4. Test the source directly - in your cloud provider's console, confirm the source exists, is sending data, and is reachable.
Common error messages
- Invalid connection string / endpoint - copy the full value; no truncation, no stray whitespace.
- Authentication failed - regenerate the credential, update it on the connection, confirm its access.
- Resource not found - the name is wrong or it was deleted; check spelling and that it still exists.
- Connection timeout - network/firewall; confirm outbound HTTPS and any proxy.
Still stuck? Gather the exact error, the connection type, when it last worked, and what changed, then ask Azi. See Connecting Data.