If you can not open/load the images, documents or other files uploaded in Cyberin S3 Object Storage, please check the file url, access permission, endpoint, application configuration. Below are some troubleshooting steps that may help you resolve the issue.
An incorrect or incomplete URL may prevent a file from opening.
Save the file link in your app or website storage.
Verify the URL for the correct storage endpoint.
Verify space name and file path are correct
File name, extension & Case (Upper/lower case)
open this url in another tab of your browser and look for error message.
If the url is incorrect (wrong path, wrong file etc) then fix it and retry.
Access Denied error appears when you try to open the file that you do not have permission to access the file.
Make sure the file is public if you are going to use it publicly.
Your app authenticates when you request it or when you receive a pre-signed URL to access a private file.
The app allows you to upload files, but not download files. Check whether the credentials have permission to read objects.
Don’t open private files to fix an access problem.
If your app is configured with the wrong endpoint or space name it won’t find the file you are trying to get.
Some config details here:
endpoint Ensure that your app is targeting the proper S3 API endpoint.
Space name: Check you are in the right Space and the file is in the right Space.
Object key Check full path and filename
region: Make sure you also set your storage configuration as well as your endpoint and region.
After correcting any incorrect values, retry the request.
If the file is deleted, renamed or moved to another path, the url to the file may be wrong.
Open your Cyberin S3 Object Storage interface.
Navigate to the Space where the file should be stored.
Locate the file and verify its exact name and path.
If the file is missing, upload it again to the intended location.
Update the URL in your application if the file's path has changed.
Remember that filenames and object paths can be case-sensitive.
If files exist in your storage but do not load in your website or application, review how your app accesses your files.
It is the right url for the application file.
Verify that the application uses the correct S3 API endpoint.
Your requests must be authenticated with valid access keys.
The app has to be run against the required S3 compatible setup.
If you are loading images from a website, CDN (Content Delivery Network) ensure origin and file URLs are correct.
If files are not loading correctly, check URLs and access settings of the files loading correctly.
If a file still does not open, check the error returned by the browser.
Error or symptom
What to check
403 Forbidden / Access Denied
File permissions, credentials, and access method
404 Not Found
Space name, file path, filename, and whether the file exists
Connection error
Endpoint URL, network connectivity, and application configuration
Image does not display
Image URL, file permissions, file format, and website configuration
File loads inconsistently
Cached content, outdated URLs, and any configured CDN
You have a problem with a web site that will not open a file . Look at the failed request in the network tab of your browser’s dev tools. See the HTTP response and status code for details
after fixing permissions or config or url or the:
Save new conf.
Reload file url.
If the file is on a website refresh the page and check back for the image/file.
Ensure that the CDN you are using is not serving a stale cached response.
If the problem persists, record the exact error message and steps to reproduce it.
If the problem continues, please contact your storage administrator or Cyberin support with the following information:
Error message or HTTP status code
What kind of file will not open.
What were you up to?
Space name (if you don’t mind sharing)
The application name and endpoint configuration, excluding credentials.
The troubleshooting steps you have taken so far.
Never include your Secret Access Keys or other sensitive credentials in support requests.