3rd Party Softwares

Overview

The table below shows the supported user-side tools and versions in vStorage. We recommend using the listed versions of these client tools to avoid errors across all features provided:

No	Tools	Protocol	Operating System	Best Support Versions	Region
1	S3cmd	S3	Windows, Linux	2.3.0	All regions.
2	Cyberduck	S3	Windows, MacOS	7.7.2	All regions.
3	Swift	Windows, Linux	7.7.2	All regions.
4	Rclone	S3	Windows, Linux	1.62.2	All regions.
5	Swift	Windows, Linux	1.62.2	All regions.
6	SwiftClient	Swift	Windows, Linux	4.3.0	All regions.
7	S3 Browser	S3	Windows, Linux	10.9.9	All regions.
8	MinIO Client (MC)	S3	Windows, Linux	RELEASE.2023-05-26T23-31-54Z	All regions.

---

List of common errors encountered during the use of user-side tools (3rd party software, client tool)

No	Error Code	Error Description	Solution
1	401 Unauthorized	Wrong login information.	Verify the vStorage credentials information (Swift username/password, token, S3 keys) used for authenticating access to the vStorage service. To work with vStorage credentials, please refer to vStorage Credentials.
2	413 Request Entity Too Large	vStorage project has run out of quota	Resize project. To resize quota of a project, please refer to Resize a project.
3	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 settings related to project or container access, please refer to Working with containers. Check the permissions and policies granted to the Swift user and s3 key on the project or container. To change settings related to permissions or access policies, please refer to Identity and Access Management.
4	401 Authorization Failure	Wrong token	Check the authentication information used to create the token, ensuring the authentication information (vStorage credentials) is correct. To work with vStorage credentials, please refer to vStorage Credentials.
5	N/A	Usage on vStorage Portal is different from the usage displayed on the 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 files displayed on the local computer may be due to a number of reasons related to information retrieval and synchronization. information, caching, etc. of vStorage system and other systems. Therefore, the user-side tool can be used to accurately check the actual storage capacity information on the vStorage service. Check the project's storage capacity information, view the "bytes" parameter and "container segment (container+/_segments)" information using the Swift Client tool according to the following 2 commands: swift stat swift list To better understand how Swift Client works, please refer Swift Client.
6	N/A	The container list on vStorage Portal is different from the container list displayed on user-side tools	vStorage service supports many user interaction interfaces such as: UI: vStorage Portal, Cyberduck, S3 Browser CLI: Aws CLI, mc, s3cmd, etc. APIs: vStorage APIs, vStorage Restful APIs, vStorage S3 APIs SDK: MinIO SDK, AWS SDK for Java, Python, Golang, C#, NodeJS, etc. Each of these user interfaces will choose to display vStorage resources (projects, containers, objects, versions, metadata, etc.) for different purposes, so there may be differences in the list of options. vStorage resources are listed and displayed. Most user interfaces have differences in listing and displaying containers. Some show container segment, container version, etc and some don't. To better understand the types of containers in the vStorage storage system, please refer to Containers overview..
7	N/A	The list of features on vStorage Portal is different from the list of features on the user-side tools	vStorage service supports many user interaction interfaces such as: UI: vStorage Portal, Cyberduck, S3 Browser CLI: Aws CLI, mc, s3cmd, etc. APIs: vStorage APIs, vStorage Restful APIs, vStorage S3 APIs SDK: MinIO SDK, AWS SDK for Java, Python, Golang, C#, NodeJS, etc. 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 provided by the service cannot be guaranteed. vStorage provides.
8	403 Forbidden	Cannot delete object on container	Check the settings related to access and manipulation of that object, refer to section #3. Check if the object is stored on containers belonging to the archive project? If so, please refer to the regulations regarding deleting objects on archive projects đây.
9	N/A	In the middle of uploading, an error occurred	In the middle of uploading an object, an error occurs. The cause may be due to: Disconected Out of quota Upload more than 1000 segments (segment size is too small) Upload a single file larger than 5 GB (do not split the file into small segments) Check these causes for corresponding solutions.
10	N/A	The storage capacity on the vStorage service does not match the total capacity of the objects that need to be saved	When you use user-side tools to upload large files (multipart upload), the file is divided into multiple segments to upload to the vStorage system. During the file download process, some segments may be uploaded, some segments may not be uploaded due to errors such as network problems, upload > 1000 segments, your user tool stops running, hanging, etc. The file is then considered an unsuccessful upload, uploaded segments are considered incomplete segments or junk segments and are taking up your storage space. You can choose a number of user-side tools that support cleaning these junk segments to clean them up and free up storage space. List of user tools that support cleaning junk segments and cleaning instructions, please refer to 3rd Party Softwares. At this time, vStorage does not support the feature of cleaning up these junk segments. We are considering a solution for future support. Currently, if there is a problem related to garbage segments, we recommend that you use the garbage cleaning solution of client tools.

Using 3rd Party Software

To use 3rd party software, you need to provide authentication information for these tools to access the vStorage storage service. You can use the Service Account identity to authenticate when accessing vStorage resources through the mentioned tools. To use a Service Account, you need to initialize S3 keys and a Swift account through the vIAM service, please refer to Service Account.

After initializing S3 keys and a Swift account through the vIAM service, collect the following information to use as authentication details when accessing the vStorage service. If you don't have this information, please contact your VNG Cloud account administrator.

• Information for S3 key includes access key, secret key, project, and restriction by IAM (if applicable).

• Information for the Swift account includes username, password, project, and restriction by IAM (if applicable).

• Service Account details include username, Client ID, and Client Secret.

You can find the configuration information for a created Service Account on the vIAM system. For more information, see [IAM for vStorage]