Errors and troubleshooting
Check the HTTP status first. It tells you what kind of problem it is.
Statuses
| Status | Meaning | What to do |
|---|---|---|
400 |
The request is not valid, or something stops it for now. | Read the message. It names the problem: a bucket name that is not valid, a name that is already used, a file that does not exist, a page that is not valid, or one of the reasons below. |
401 |
The credential is missing or wrong. | Check the access key ID and secret. A wrong secret and a missing credential get the same answer. |
402 |
Uploads are paused because your storage balance is unpaid. | Top up your credits. |
403 |
The credential is valid but not allowed to do this. | See below. |
404 |
The file does not exist (file endpoints), or the bucket does not exist or is not yours (the /buckets endpoints). |
Check the bucket identifier and the file's name. |
411 |
The upload had no Content-Length. |
Send the file as bytes or a file, not as a stream of unknown length. |
413 |
The file is larger than 5 GB. | Upload a smaller file. See Limits. |
502 |
Storage could not complete the request. | Try again. If it keeps failing, contact support. |
An error answer comes in more than one shape. See Response formats for each one.
Messages you may see
Your credentials are missing or not valid. (401)
The access key ID and secret were not sent, or do not match. Use HTTP Basic authentication with the access key ID as the username and the secret as the password. A credential you have deleted stops working immediately. If you no longer have the secret, create a new credential.
This credential is read-only. (403)
You used a read-only credential for something that changes data: an upload, a delete, a new folder, a new bucket, or a change of visibility. Use a read & write credential for that. See Access levels.
You do not have access to this bucket. (403)
The file endpoints answer this when the bucket identifier belongs to another account, is mistyped, or names a bucket that is not ACTIVE. Use the bucket value that listing your buckets returns, not the name shown in the dashboard.
Bucket not found. (404)
The /buckets/... endpoints answer this when the bucket identifier does not exist or belongs to another account. The file endpoints answer the same mistake with 403 You do not have access to this bucket. Use the bucket value that listing your buckets returns.
Storage buckets are available on paid plans. (403)
Your account is on a free trial. Every endpoint under /buckets refuses trial accounts. The file endpoints do not check the plan. See Pricing and billing.
Buckets are managed from the Kuberns dashboard, not through this endpoint. (403)
You sent a PUT, POST, or DELETE to /{bucket} on its own. To create or delete a bucket, use POST /buckets or DELETE /buckets/{bucket}. See the API reference.
New uploads are paused because your storage balance is unpaid. Top up your credits to continue. (402 or 400)
You owe for storage, so uploads, new folders, and new buckets are paused. Reading, downloading, and deleting still work. Add credits to resume, and see If your credits run out for the deadline.
Run at least one service to create your first bucket. (400)
Your first bucket needs at least one running service. Start a service, or deploy one, then try again. Once you have a bucket, this no longer applies.
Use 3-40 lowercase letters, numbers and hyphens. (400)
The bucket name is not valid. Use only lowercase letters, numbers, and hyphens, 3 to 40 characters, starting and ending with a letter or a number.
You already have a bucket with this name. (400)
You have used that name before. Names must be unique among your own buckets. Choose another.
That file does not exist. (404 or 400)
The file name does not match. Names are case-sensitive and include the folder, for example reports/2026/summary.pdf. List the bucket to see the exact names. Download a file answers 404. Get visibility, Set visibility, and Get a link answer 400.
Common problems
The Create Bucket button is disabled
Hover over it to see why. It is either because you have no running service and no bucket yet, or because your account owes for storage. See Create and manage buckets.
A file I made public is private again
Uploading a file with the same name replaces it, and the replacement starts out private. Open the lock icon and select Make public again. See Uploading over an existing file.
A temporary link says it has expired
Temporary links for private files last a short time, ten minutes by default. Get a new link, or make the file public if the link needs to last.
A public link still works after I made the file private
Links are served from a global network that can keep a copy for a short time. It stops working within about a minute.
A bucket's size or file count looks out of date
These figures are refreshed periodically, so a file you just uploaded or deleted may not be counted yet. The list of files is always current.
My storage cost looks different from what I expected
Charges are based on GB-hours, so a file you keep for part of the month costs a part of the monthly price. See How the charge is worked out, and check Buckets → Analytics for each day's cost.