Check whether the network connectivity between the local computer and OBS is normal. If the network is down, restore the network connectivity.
Check whether the account has passed real-name authentication. If not, perform real-name authentication first.
Log in to OBS Console.
On the top navigation menu, you can view the user authentication status.
Figure 1 Account authentication status
If you have not completed the real-name authentication, complete it by referring to Individual Real-Name Authentication Process. The real-name authentication takes effect 40 minutes later.
Check whether the account is in arrears or the account balance is insufficient. If this is the case, pay off the outstanding balance or top up the account.
Log in to OBS Console.
On the top navigation menu, click Billing. The Billing Center page is displayed.
On the Overview page, you can view the balance of the account.
If your account is in arrears, top up it by referring to Renewal Management.
If the object cannot be uploaded after the account is brought current, contact customer service.
Check whether the account has the required permissions. If the account does not have the permissions needed, grant them.
Log in to the management console
On the top navigation menu, click the username and select Identity and Access Management to log in to the IAM console and verify the permissions of the user.
On the Users page, search for the username.
Click the icon of a downward arrow on the left of the username to unfold details of the username, and check which user group does the user belong to. If the user is not added to any user group, click Modify and select a user group.
In the navigation pane on the left, click User Groups and find the user group to which the user belongs. Click the icon of a downward arrow on the left of the user group name to view user group permissions. Find OBS under the Project Name column and click View under the Operation column, to check whether the user group has the permission to create buckets. If not, create a user group, configure a policy that authorizes the user group the bucket creation permission, and add the user to the user group.
If the number of buckets created by the current user reaches 100, delete some unneeded buckets first.
If the name for the new bucket already exists, use another name and try again. Each OBS bucket name must be globally unique and cannot be changed.
The name of a deleted bucket cannot be reused immediately after the deletion. It can be reused for a bucket or a parallel file system at least 30 minutes later after the deletion.
If the failure is not caused by any of the preceding reasons, check the returned error code and find the reason.
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.