Troubleshooting

Most connection problems come from a mistyped value. Find the message Kelp shows below.

The signature doesn't match

The secret access key is wrong or incomplete. Copy it again from your provider and check that no spaces were added at either end. Also check that the region matches your bucket.

Access denied

The key works, but it isn't allowed to do this. Check the permissions or policy attached to the key in your provider's console.

No buckets are listed

Some keys can read objects but can't list buckets, for example Cloudflare R2 tokens limited to specific buckets. Give the key permission to list buckets, or create a new key with wider access.

Kelp can't reach the endpoint

Check the endpoint for typos and make sure it starts with https://. A company firewall or VPN may also block it. If the error mentions a host name that contains your bucket name, turn on path-style addressing for the connection.

The request time is too far off

Your Mac's clock is wrong. Open System Settings → General → Date & Time and turn on Set time and date automatically.

macOS won't open Kelp

If macOS says it can't check the app, open System Settings → Privacy & Security and choose Open Anyway.

Still stuck?

Open an issue on GitHub and include the message Kelp shows. Never include your secret key.