Skip to main content
Start with the organization, endpoint, and credential pair. Then use the section that matches the failed operation.

Object Storage is missing

Hivenet Object Storage is generally available to all organizations. Check the organization selected in the console, then contact Support if Object Storage is still missing from the expected organization.

Activation is unavailable

Read and select the acknowledgment checkbox before selecting Activate Object Storage. If you previously activated storage and left the credentials screen, activation remains in place. Open My keys and follow lost-secret recovery.

Buckets are visible but actions are disabled

You need an active key of your own to use bucket and object actions in the console. Joining an organization does not create one for you. If My keys is empty, select New key, save both credential values, and confirm that you have saved them. An active key is required, but your organization’s access mode can still restrict actions. For self-service storage, also check for an Add credits warning. At zero or negative balance, writes are blocked and the console’s bucket view is locked. Your organization’s configuration determines whether storage becomes Read only or Disabled. A configured S3 client can list and download objects in Read only mode; these actions are blocked in Disabled mode. Add enough credits to clear outstanding debt and leave a positive balance, or ask the organization Owner to do so. If access remains restricted after the balance becomes positive, refresh the console and contact support if the problem continues. See Usage and billing and Access keys.

You cannot create or revoke a key

  • Two keys already exist: Revoke an unused key to free a slot. Update its clients first.
  • Only one key exists: The console blocks revoking it. Create and save a replacement, update clients, and then revoke the old key.
  • The secret is missing: View cannot reveal it again. Create a replacement pair.
See Access keys for the full rotation procedure.

Authentication or signature errors

For InvalidAccessKeyId, SignatureDoesNotMatch, or access errors:
  1. Confirm the endpoint is https://eu.s3.hivenet.com.
  2. Set the signing region to Europe, with the same capitalization.
  3. Explicitly enable path-style addressing.
  4. Use the matching access key ID and secret from the intended organization.
  5. Check for truncated values, extra whitespace, or an old credential in the application’s environment or profile.
  6. Confirm that the key has not been revoked.
The old eu.s3.public.hivenet.com endpoint is deprecated. Use the current EU endpoint above and confirm that the expected buckets are listed. US access is planned separately; see Connection settings. If reads work but uploads or deletes fail, check the credit balance and access mode before replacing credentials. For time-related signature errors, check that the client machine’s clock is correct. Object Storage credentials sign S3 requests. Do not send them as an Inference API bearer token.

A revoked key still works

Verify the result using a fresh request with that specific key. A removed row in My keys is not proof that every request path has stopped accepting it. If it still works, contact support with the revocation time, the failing request details, and a redacted key identifier. Do not send the secret or a complete signed URL.

The client uses a bucket subdomain or reaches AWS

Set path style explicitly: Use the Hivenet base endpoint and pass the bucket separately. Include --endpoint-url https://eu.s3.hivenet.com on AWS CLI requests. See Connection settings.

Bucket creation fails

For self-service storage, check that the organization has a positive balance and full access. Bucket creation is blocked in both Read only and Disabled modes. Use 3–63 lowercase letters, numbers, and hyphens. Start and end with a letter or number, and do not use dots. If the name is already in use in the region, choose another. The console shows the backend rejection beside the field. Do not assume bucket names are available because your organization has not used them.

An upload fails

Check the file’s name and size before retrying.
  • Out of credits: Uploads are blocked in both Read only and Disabled modes. Add credits to restore full access.
  • Invalid name: Follow the object naming rules.
  • File too large: Follow the file-size validation shown in the console. The console handles multipart uploads automatically for larger files. For large batches or unattended transfers, use a client with multipart support. The API supports objects up to 5 TB through multipart uploads. See File size and large transfers.
  • Only some files uploaded: Use Retry failed files and check the resulting object list.
  • You cannot add more files: Resolve failed uploads by retrying them or closing the dialog before adding more.
  • Page reloaded: In-progress uploads stop, while completed files remain stored. Check the object list and retry the missing files.
  • Connection interruption: Reopen the bucket to see what was stored, then retry the missing files.
  • An older file changed: Uploading to the same key replaces the object.
If a browser request is blocked by CORS, capture the failed request’s time, method, and status for support. Do not change bucket policies or expose credentials to work around it.

An object cannot be downloaded

Copy the exact object key, including its prefix and capitalization. Check that it still exists. A deleted object returns a not-found response. If the console list is stale, refresh it. At a zero or negative balance, the console’s bucket view is locked. In Read only mode, you can download existing objects through a configured S3 client. In Disabled mode, authenticated object reads are blocked. Either mode can apply when credits run out, depending on your organization’s configuration. Add enough credits to leave a positive balance, then retry. Contact support if access remains restricted. For console downloads, check the browser’s download list. Use AWS CLI or rclone for multiple objects. Check that the URL was copied in full, that it has not expired, and that the object still exists. An access-mode change, including running out of credits, does not revoke an existing link. If you are authorized to share the object, generate a new link with an appropriate expiry. See Share objects. Do not include the complete share URL in a public issue or support screenshot.

A bucket will not delete

In Read only or Disabled mode, you cannot delete stored data. Restore full access before trying to empty or delete a bucket. BucketNotEmpty means objects remain. Keep the console tab open during emptying. Stop emptying lets the running batch finish and prevents the next batch from starting. Wait for the result, check the remaining object count, and retry against the objects that remain. A lost connection can leave the outcome uncertain. Refresh first; do not assume nothing was deleted. See Empty or delete a bucket.

Usage or cost looks unexpected

Check the billing period and your organization’s rate. Self-service storage draws hourly from the same balance as Compute and inference. The €50 monthly minimum applies only to invoiced customers. Stored data continues to accrue charges while access is restricted, so a zero balance can become negative. A top-up first pays that outstanding amount. Distinguish actual cost so far from the end-of-month estimate. Storage used measures the current amount stored. The usage API reports KiB-hours, which measure accumulated storage usage over time. Billing converts this meter to decimal TB-hours and uses the actual hours in the calendar month. See How storage is metered for units and rounding. Transfer data is aggregated hourly. It is not a real-time activity log. See Usage and billing.

Contact support

Use Chat with us in the console or your Hivenet contact. Include:
  • Organization, operation, and approximate time with time zone.
  • Client name and version.
  • Error code, status, and request ID if available.
  • Whether the same operation works in the console or another client.
Remove secrets, signed query strings, and sensitive object names from logs before sharing them.