If you are having trouble uploading files to Cyberin S3 Object Storage, check the file size, network connection, access permissions, credentials, and endpoint configuration. Troubleshoot the cause of the upload problem and fix the problem by following the steps that follow.
The file may be too big to upload. Some storage services, applications or upload methods have size limitations.
Please verify the size of the file you are uploading.
Check the file size limit in your storage panel or app.
Verify that the application you are attempting to open is of the correct file type.
If there is a size limit for the app, try uploading a smaller test file.
If large files are failing but smaller files are uploading fine, check that the application supports multipart uploads and the application’s upload configuration is correct.
An unstable network connection can interrupt an upload before it is complete.
Ensure you have a good internet connection.
If necessary, reconnect to the network and try uploading again.
If you can try uploading on some other reliable network.
Do not close the tab or application until the upload is finished.
If the uploads are failing at different points check if your network/application is timing out during the upload.
If the upload generates an authentication error, or Access Denied message, verify the credentials used to connect to S3 Object Storage.
Check that the Access Key ID is correct.
Confirm that the matching Secret Access Key is being used.
Remove any accidental spaces or incorrect characters.
If the credentials were regenerated, update the application with the current values.
Never place your Secret Access Key into screenshots, public repositories, or support requests.
Valid credentials do not necessarily have permission to upload files.
Verify that the access key or user account has the required write permissions for the intended Space.
If you can view or download existing files but cannot upload new ones, ask your storage administrator to check the permissions associated with the upload operation.
Do not make the Space public to resolve an upload permission error. Public access and upload authorization are separate settings.
An incorrect endpoint or Space name can prevent the application from uploading files to the intended storage location.
Check these configuration details:
Endpoint: Ensure the application uses the correct S3 API endpoint for your storage service.
Space name: Verify that the destination Space exists and its name is entered correctly.
Region: Confirm that the endpoint and region settings match your storage configuration.
Object key: Check the destination path and filename if the application allows you to specify them.
Save any corrections and retry the upload.
If the upload fails through a website, plugin, SDK, or other application, review its storage settings.
Confirm that the application supports your S3-compatible storage service.
Verify that the endpoint and authentication settings are correct.
Check whether the application has its own file size or request timeout limit.
If multipart uploads are used, verify that the application supports the required upload operations.
Check the application's logs for the exact error message.
If the same file uploads successfully through the Cyberin storage panel but fails through an application, investigate the application's configuration and upload process.
The error message can help you determine which setting needs attention.
Error or symptom | What to check |
|---|---|
Access Denied / 403 | Credentials and upload permissions |
Authentication or signature error | Access key, secret key, region, and signature configuration |
Space or object not found | Space name, endpoint, and destination path |
File too large | Storage, application, or upload-method size limits |
Connection timeout | Network stability, request timeout, and upload duration |
Upload stops before completion | Network interruptions, application errors, and multipart upload configuration |
Use the actual error message returned by your storage panel or application to guide your troubleshooting.
Then fix the proper settings:
Save the config.
Try uploading again.’
Please wait while upload is completed.
Make sure the file is in the Space you want it in.
If it fails to upload again, please make a note of the message indicating the error and where it fails.
If your previous upload ended up with a partial or incomplete object, check its status before you try again, especially if your application uses multipart uploads.
If the issue persists, contact your storage administrator or Cyberin support with the following details:
The exact error message or error code.
The approximate file size and file type.
Whether all files fail or only specific files.
The application or tool used for uploading.
The configured endpoint and region, excluding credentials.
The troubleshooting steps you have already taken.
Do not include your Secret Access Key or passwords, or any other sensitive credentials, in support requests.