This topic describes common issues you may encounter while using ossutil and respective solutions.
When executing ossutil commands, the error "region must be set in sign version 4" is reported
Possible cause: The region ID was not specified in the configuration process of ossutil 2.0.
Solution: To avoid failures caused by missing configuration items when using ossutil, ensure that you configure the AccessKey ID, AccessKey Secret, and Region ID according to the steps below. Note that the configuration of region ID is mandatory, as the signature algorithm has been upgraded to V4. For information on how to retrieve your region ID, see OSS regions and endpoints.
Linux
Run the following command to start the configuration process:
ossutil config
Configure the path of the configuration file. You can press the Enter key to use the default path.
Please enter the config file name,the file name can include path(default /root/.ossutilconfig, carriage return will use the default file. If you specified this option to other file, you should specify --config-file option to the file when you use other commands):
By default, ossutil uses /root/.ossutilconfig as the configuration file.
Specify the AccessKey ID, AccessKey secret, and region ID based on the on-screen instructions.
Enter the AccessKey ID that you created.
Please enter Access Key ID [****************id]:LTAI****************
Enter the AccessKey secret that you created.
Please enter Access Key Secret [****************sk]:R6vg*********************
Enter the ID of the region in which your data is stored on OSS. The default region ID is cn-hangzhou.
Please enter Region [cn-hangzhou]:cn-hangzhou
In this example, the ID of the China (Hangzhou) region is used. For information about the IDs of other regions, see OSS regions and endpoints.
Windows
Run the following command to start the configuration process:
ossutil config
Configure the path of the configuration file. You can press the Enter key to use the default path.
Please enter the config file name,the file name can include path(default "C:\Users\issuser\.ossutilconfig", carriage return will use the default file. If you specified this option to other file, you should specify --config-file option to the file when you use other commands):
By default, ossutil uses C:\Users\issuser\.ossutilconfig as the configuration file.
Specify the AccessKey ID, AccessKey secret, and region ID based on the on-screen instructions.
Enter the AccessKey ID that you created.
Please enter Access Key ID [****************id]:LTAI****************
Enter the AccessKey secret that you created.
Please enter Access Key Secret [****************sk]:R6vg*********************
Enter the ID of the region in which your data is stored on OSS. The default region ID is cn-hangzhou.
Please enter Region [cn-hangzhou]:cn-hangzhou
In this example, the ID of the China (Hangzhou) region is used. For information about the IDs of other regions, see Regions and endpoints.
macOS
Run the following command to start the configuration process:
ossutil config
Configure the path of the configuration file. You can press the Enter key to use the default path.
Please enter the config file name,the file name can include path(default "/Users/user/.ossutilconfig", carriage return will use the default file. If you specified this option to other file, you should specify --config-file option to the file when you use other commands):
By default, ossutil uses /Users/user/.ossutilconfig as the configuration file.
Specify the AccessKey ID, AccessKey secret, and region ID based on the on-screen instructions.
Enter the AccessKey ID that you created.
Please enter Access Key ID [****************id]:LTAI****************
Enter the AccessKey secret that you created.
Please enter Access Key Secret [****************sk]:R6vg*********************
Enter the ID of the region in which your data is stored on OSS. The default region ID is cn-hangzhou.
Please enter Region [cn-hangzhou]:cn-hangzhou
In this example, the ID of the China (Hangzhou) region is used. For information about the IDs of other regions, see OSS regions and endpoints.