Backblaze B2 Extension Error Codes

The All-in-One WP Migration plugin uses Backblaze B2 API to communicate with your account and store your backups. If there is an error communicating with your Backblaze B2 drive and the files that are stored in it, you might get one of these errors.
Backblaze B2 sets a per-user quota for each user to make sure that the resources available are shared fairly. If you have many other applications or systems connected to your B2 account you may encounter issues.

What can you do about it?

If the all-in-One WP Migration plugin cannot connect to your B2 drive, please sign out from your account and sign in again in the Backblaze B2 Settings page of the plugin on your WordPress Console.
Ensure that there are no other applications using your B2 drive at the same time as the All-in-One WP Migration extension. If you have other 3rd party applications or other services that are connected to your Backblaze B2 drive, consider stopping or uninstalling them. If you share large numbers of documents with other people or the public, consider an alternative solution to Backblaze B2.

Please see more specific detail about each error code below:

Invalid Credentials
The All-in-One WP migration plugin can not connect to your B2 cloud. Please sign out from your account and sign in again in the Backblaze B2 Settings of the plugin on your WordPress Console.

The user does not have sufficient permissions for file
The All-in-One WP migration plugin can not access a file or folder on your Backblaze B2. Please check that your account has permissions on the file or folder that you are trying to access with the plugin.
If this does not work, or if the file is stored on your drive, please sign out from your account and sign in again in the Backblaze B2 Settings page of the plugin on your WordPress Console.

Cannot be used within the domain
The All-in-One WP migration plugin can not access your Backblaze B2 cloud. If you are attempting to backup op or migrate your site whilst logged in on a corporate domain, please check that you are able to access your Backblaze B2 storage or contact the domain administrator.

File not found
The All-in-One WP migration plugin can not access a file or folder on your Backblaze drive. Please check that the file exists and that you can access it through your drive.

Backend Error
An unexpected error occurred with your B2 cloud while processing the request. Please try again. Please sign out from your account and sign in again in the Backblaze B2 Settings page of the plugin on your WordPress Console.

Bad Request
The All-in-One WP migration plugin can not connect to your Backblaze B2 account. Please sign out from your account and sign in again in the Backblaze B2 Settings of the plugin on your WordPress Console.

User Rate Limit Exceeded
There have been too many API calls on your drive. Try again after stopping drive sync and any other applications that connect to your drive and waiting for 5 minutes

Rate Limit Exceeded
There have been too many API calls on your drive. Try again after stopping drive sync and any other applications that connect to your drive and waiting for 5 minutes.

Sharing Rate Limit Exceeded
You have exceeded the sharing rate limit on your Backblaze B2 account. This can be related to emails or documents that you are sharing publicly from your drive Don’t send large volumes of emails when you are doing backups/migrations. Remove permissions on publicly available files in your drive.

The user has not granted access to the file
The All-in-One WP migration plugin can not access a file or folder on your Backblaze B2. Please check that your cloud account has permissions on the file or folder that you are trying to access with the plugin. If this does not work, or if the file is stored on your drive, please sign out from your account and sign in again in the Backblaze B2 Settings page of the plugin on your WordPress Console.

Too Many Requests
There have been too many requests on your Backblaze B2 account. This can be related to documents that you are sharing publicly from your drive or other applications that are using your B2 cloud.

 

Here is a complete list of HTTP error codes:

*press control F to search this page

Code: 400 ‘Bad Request’
There is a problem with a passed in request parameters – the JSON error structure returned will contain an error code and a human-readable error message describing the problem

Code: 401 ‘Unauthorized’
Returned while uploading, indicates the upload URL has expired; A new upload URL can be obtained from b2_get_upload_url or b2_get_upload_part_url
Returned from b2_authorize_account, indicates the account ID is wrong, the account does not have B2 enabled, or the application key is not valid
For all other APIs, there is a problem with the Authorization Token as indicated in the human-readable message. A new Authorization Token can be obtained from b2_authorize_account

Code: 403 ‘Forbidden’
You have a reached a storage cap limit, or account access may be impacted in some other way; see the human-readable message

Code: 404 ‘Not Found’
The requested resource doesn’t exist

Code: 405 ‘Method Not Allowed’
The HTTP method in the request is not allowed on the resource

Code: 406 ‘Not Acceptable’
This service doesn’t support the format requested in the Accept header. The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request

Code: 407 ‘Proxy Authentication Required’
Proxy authentication required. The client must first authenticate themselves with the proxy

Code: 408 ‘Request Timeout’
Request timed out. The server timed out waiting for the request. The client did not produce a request within the time that the server was prepared to wait. Repeat the request without modifications at any later time

Code: 409 ‘Conflict’
Indicates that the request could not be processed because of conflict in it

Code: 410 ‘Gone’
The requested resource is no longer available at the server

Code: 411 ‘Length Required’
A Content-Length based header is required on the request

Code: 412 ‘Precondition Failed’
The server does not meet one of the preconditions that the requester put on the request

Code 413 ‘Request Entity Too Large’
The request size exceeds maximum limit

Code 414 ‘Request-URI Too Long’
Request-URI too long. The URI provided was too long for the server to process

Code: 415 ‘Unsupported Media Type’
The content type of the request is a format that is not supported by the service

Code: 416 ‘Requested Range Not Satisfiable’
The specified byte range is invalid or unavailable

Code: 417 ‘Expectation Failed’
Expectation failed. The server cannot meet the requirements of the Expect request-header field

Code: 429 ‘Too Many Requests’
B2 may limit API requests on a per-account basis

Code: 500 ‘Internal Error’
An unexpected error has occurred. The human-readable message is intended for Backblaze engineering use, to help isolate the problem

Code: 501 ‘Not Implemented’
The requested feature is not implemented

Code: 502 ‘Bad Gateway’
Bad gateway. The server was acting as a gateway or a proxy and received an invalid response from the upstream server.

Code: 503 ‘Service Unavailable’
The service is temporarily unavailable. The human-readable message identifies the nature of the issue, in general we recommend retrying with an exponential backoff between retries in response to this error

Code: 504 ‘Gateway Timeout’
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server

Code: 505 ‘HTTP Version Not Supported’
The server does not support the HTTP protocol version used in the request

 

Here is a complete list of Backblaze B2 API errors:

*press control F to search this page

Error: unauthorized
One of:

  • B2 has not been enabled for this account
  • User is in B2 suspend
  • Invalid authorization
  • Not authorized
  • Bucket is not authorized
  • Bucket does not have the specified file

Error: missing_phone_number
Account is missing a mobile phone number. Please update account settings

Error: bad_request
One of:

  • Invalid fileId: <fileId>. File id used for the request is not valid
  • No active upload for: <fileId>. Used file id is not valid for the upload request
  • No active upload for large file (<fileId>). Used file id is not valid for the large file/multipart upload request
  • Wrong host name for request
  • AccountId bad. Provided account id not valid
  • Account <accountId> does not exist
  • Not a valid file id: <fileId>
  • Invalid bucked id: <bucketId>
  • bucketName is required but nor provided
  • bucketName must be at least 6 characters long
  • bucketName can be at most 50 characters long
  • Bucket id <bucketId> does not exist
  • Bucket id <bucketId> is not a B2 bucket
  • bucketTypes cannot be empty. Must be provided either ‘allPublic’ or ‘allPrivate’ type
  • “all” cannot be requested with other bucket types
  • Invalid bucketTypes requested
  • Invalid characters in bucketName: must be alphanumeric or ‘-‘
  • No Authorization header in the request
  • Snapshot buckets are reserved for Backblaze use
  • Allow snapshot header must be specified when deleting a file from a snapshot bucket
  • Application key does not exist. Please provide valid application key to access the account
  • Part <partNumber> found sha1 is different from expected (in upload requests for large files)
  • Part number is smaller than minimum part size for upload (in upload requests for large files)
  • Last part cannot be empty (in upload requests for large files)
  • File names must not start with ‘/’
  • File names must not end with ‘/’
  • File names must not contain ‘\’
  • File names must not contain DELETE
  • File names must not contain ‘//’
  • File names must contain at least one character
  • File names in UTF8 must be no more than 1000 bytes
  • File names segment must not be more than 250 bytes
  • File names must not start with the given delimiter
  • File is too big
  • fileNamePrefix must be specified
  • validDurationInSeconds must be >= 0
  • validDurationInSeconds cannot be greater than a week
  • Prefix must be 1 or more characters long
  • Delimiter must be within acceptable list
  • Timed out while iterating and skipping files
  • Maximum number of file info entries is 10
  • File info name too long: <name>
  • File info value too long: <value>
  • Total size of file name and file info headers is <totalSize>, which is over the max of 7000
  • File names segment must not be more than 250 bytes
  • Cannot change a bucket to a snapshot bucket
  • bucket_not_updated
  • Request path is null
  • Missing header: X-Bz-Part-Number
  • Part number must be in the range 1 – 10000
  • Not a valid part number: <headerValue>
  • Request path should look like: /b2api/v1/b2_upload_part/<fileId>/
  • Invalid file id in path. Provided file id in the request is invalid
  • Invalid tome id in path
  • Not a valid hex sha1: <contentSha1> (in upload requests for large files)

Error: cap_exceeded
Usage capabilities exceeded

Error: method_not_allowed
Only POST is supported, not <method>

Error: request_timeout
The service timed out reading the uploaded file

Error: conflict
The ifRevisionIs test failed

Error: missing_auth_token
Authorization token is missing.

Error: expired_auth_token
Authorization token has expired

Error: already_hidden
File already hidden: <fileName>

Error: bad_auth_token
One of:

  • Invalid authorization token
  • Authorization token for wrong cluster

Error: too_many_buckets
The account is already at the maximum bucket count

Error: duplicate_bucket_name
Bucket name is already in use

Error: bad_bucket_id
Bucket <bucketId> does not exist

Error: file_not_present
File not present: <fileName> <fileId>

Error: not_found
One of:

  • File state deleted
  • File state none
  • File state unknown

Error: no_such_file
File not present: <fileName>

Error: range_not_satisfiable
The Range header is the request is outside the size of the file

Error: service_unavailable
One of:

  • No uploads available in vault <vaultId>
  • Various reasons

Error: invalid_bucket_id
Invalid bucketId: <bucketId>

Error: out_of_range
maxFileCount out of range: <maxFileCount>

Error: invalid_file_id
Invalid startFileId: <startFileId>

Leave A Comment?