Connection errors¶
I get "Access Denied" or a signature error¶
Usually a wrong or mistyped key. Re-copy your access key and secret key from the welcome email — watch for trailing spaces. Confirm both belong to the same service. See Endpoint & credentials.
I get a certificate / SSL error¶
You're almost certainly connecting by IP or to the wrong host. Use the exact hostname
from your welcome email with https:// — the TLS certificate matches the hostname, not
an IP. See TLS & HTTPS.
I get a DNS resolution error for bucket.endpoint¶
That's virtual-host addressing trying to resolve a bucket-prefixed hostname. Switch your client to path-style. See Path-style vs virtual-host.
Connection times out or is refused¶
First, check your whitelist IP. Your endpoint only accepts the single IP you set in the client area. If your public IP has changed (home ISP, VPN, a different server), connections are refused until you update it. Confirm your current public IP at ifconfig.me and make sure it matches your whitelist IP. Also check that outbound HTTPS (port 443) isn't blocked by a local firewall or proxy.
I set everything correctly but still can't connect¶
The usual culprit is the whitelist IP not matching your current public IP — it's easy to miss after a reconnect or when connecting from a new machine. Update the whitelist IP in the client area to your current IP, or run the auto-detect API call from the machine that needs access to set it automatically.
"Could not connect to the endpoint URL"¶
The endpoint is malformed or missing the scheme. It must be a full https://... URL.
Re-paste it exactly from the welcome email.
My region setting causes errors¶
ZenDRIVE doesn't need an AWS region. If your client demands one, set us-east-1 as a
placeholder — the endpoint URL is what routes requests.
It worked yesterday and now fails¶
Confirm your service is active and the invoice is current in the client area, and that your keys haven't been rotated. If all looks right, contact support@clearstreamer.com.
Nothing here fixed it¶
Email support@clearstreamer.com with the exact error text, your client and version, and which service you're using — see Getting support.