3rd party softwares

Overview

vStorage supports the following client tools and their respective versions. We recommend that you use the versions listed in this table of client tools to avoid errors on all the features we provide:

List of common errors when using 3rd party software, client tools

401 Unauthorized	Wrong login information.	Verify the vStorage credentials information (token, s3 keys) used for authenticating access to the vStorage service. To work with vStorage credentials, please refer to here.
413 Request Entity Too Large	vStorage project has run out of quota	Resize project. To resize quota of a project, please refer to here.
403 Forbidden	Not have access	Check the settings related to project or container access (CORS, ACLs, IP Range ACL, public container, etc.) on vStorage portal. To change the settings related to project or bucket access, please refer here. Check the permissions and policies granted to the s3 key on the project or bucket. To change the settings related to permissions or access policies, please refer here.
401 Authorization Failure	Wrong token	Check the credentials used to generate the token, make sure the credentials (vStorage credentials) are correct. To work with vStorage credentials, please refer here.
N/A	Usage on vStorage Portal is different from usage displayed on local machine	vStorage Portal uses storage base = 1024 (1 KB = 1024 B). The fact that at some times the total capacity (usage) displayed on the vStorage portal is different from the total size of the files displayed on the local computer may be due to a number of reasons related to information retrieval, information synchronization, caching, etc. of the vStorage system and other systems. Therefore, the client tool can be used to accurately check the actual storage capacity information on the vStorage service.
N/A	The bucket list on vStorage Portal is different from the bucket list displayed on the client tools	The vStorage service supports multiple user interaction interfaces such as: UI: vStorage Portal, Cyberduck, S3 Browser CLI: Aws CLI, mc, s3cmd, v.v. API: vStorage APIs, vStorage Restful APIs, vStorage S3 APIs SDK: MinIO SDK, AWS SDK cho các ngôn ngữ Java, Python, Golang, C#, NodeJS, v.v. Each of these user interfaces will choose to display vStorage resources (projects, buckets, objects, versions, metadata, etc.) for different purposes, so there may be differences in the list of vStorage resources listed and displayed. Most user interfaces have differences in listing and displaying buckets. Some show bucket versions, etc. and some do not. To better understand the bucket types in vStorage, please refer here.
	The list of features on vStorage Portal is different from the list of features on the client tools.	The vStorage service supports multiple user interaction interfaces such as: UI: vStorage Portal, Cyberduck, S3 Browser CLI: Aws CLI, mc, s3cmd, v.v. API: vStorage APIs, vStorage Restful APIs, vStorage S3 APIs SDK: MinIO SDK, AWS SDK cho các ngôn ngữ Java, Python, Golang, C#, NodeJS, v.v. Each of these user interfaces will choose to provide features for different purposes. In addition, because the purpose of most user interfaces is to support many different hosting providers, 100% compatibility with the features offered by the vStorage service is not guaranteed.
403 Forbidden	Cannot delete object on bucket	Check the settings related to access and manipulation of that object, refer to #3. Check if the object is stored in a bucket belonging to the archive project. If so, please refer to the rules regarding deleting objects in the archive project here.
N/A	Error occurred while uploading	When an error occurs while uploading an object, the cause may be: Network failure Out of quota Upload more than 1000 segments (segment size too small) Upload single files over 5GB (do not split files into small segments) Check these causes for corresponding solutions.
N/A	The storage capacity on the vStorage service does not match the total capacity of the objects to be stored.	When you use the client tools to upload large files (multipart upload), the file is divided into multiple segments to upload to the vStorage system. During the file upload process, some segments may be uploaded, some segments may not be uploaded due to errors such as network problems, uploading > 1000 segments, your client tools are stopped, hanged, etc. The file is then considered as an unsuccessful upload, the uploaded segments are considered as incomplete segments or garbage segments and are taking up your storage space. You can choose some client tools that support cleaning these garbage segments to clean them up and free up storage space. For a list of user-side tools that support cleaning garbage segments and cleaning instructions, please refer to the user manual of each tool in this section. At the moment, vStorage does not support the garbage segment cleaning feature. We are looking into solutions to support it in the future. For now, if you have problems with garbage segments, we recommend using the garbage cleaning solution provided by the client tools.