Box Extension Error Codes

The All-in-One WP Migration plugin uses Box API to communicate with your Box account and store your backups. If there is an error communicating with your Box and the files that are stored in your account, you might get one of these errors
Box cloud storage 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 Box you may encounter issues.

What can you do about it?

If the all-in-One WP Migration plugin cannot connect to your Box storage, please sign out from your Box account and sign in again in the Box Settings page of the plugin on your WordPress Console.
Ensure that there are no other applications using your Box cloud 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 Box, consider stopping or uninstalling them. If you share large numbers of documents with other people or the public, consider an alternative solution to Box.

Please see more specific detail about each error code below:

Invalid Credentials
The All-in-One WP migration plugin can not connect to your Box. Please sign out from your Box account and sign in again in the Box 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 Box. Please check that your Box 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 Box drive, please sign out from your account and sign in again in the Box 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 Box. 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 Box account or contact the domain administrator.

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

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

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

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

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

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

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 Box. Please check that your Box 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 Box storage, please sign out from your account and sign in again in the Box Settings page of the plugin on your WordPress Console.

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

Here is a complete list of HTTP error codes:

*press control F to search this page

Code: 400 ‘Bad Request’
Message: Unable to perform Box request

Code: 401 ‘Unauthorized’
Message: Authorization token is not authorized – authentication is required and has failed or has not yet been provided.

Code: 402 ‘Payment Required’
Message: Payment for the product is required in order to proceed.

Code: 403 ‘Forbidden’
Message: Forbidden access. The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.

Code: 404 ‘Not Found’
Message: The resource could not be found. The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

Code: 405 ‘Method Not Allowed’
Message: Method not allowed. The HTTP method used for the API operation is not allowed.

Code: 406 ‘Not Acceptable’
Message: 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’
Message: Proxy authentication required. The client must first authenticate themselves with the proxy.

Code: 408 ‘Request Timed Out’
Message: 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’
Message: Indicates that the request could not be processed because of conflict in it.

Code: 410 ‘Gone’
Message: Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future.

Code: 411 ‘Length Required’
Message: Lenght required. The request did not specify the length of its content, which is required by the requested resource.

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

Code: 413 ‘Request Entity Too Large’
Message: Request entity too large. This error is produced when the size of the upload is more than the allowed maximum.

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

Code: 415 ‘Unsupported Media Type’
Message: Unsupported media type. The request entity has a type which the server or resource does not support.

Code: 416 ‘Requested Range Not Satisfiable’
Message: Requested range not satisfiable. The client has asked for a portion of the file, but the server cannot supply that portion.

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

Code: 500 ‘Internal Server Error’
Error: internal_server_error
Message: Internal server error. A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

Code: 501 ‘Not Implemented’
Message: Not implemented. The server either does not recognize the request method, or it lacks the ability to fulfil the request.

Code: 502 ‘Bad Gateway’
Error: bad_gateway
Message: 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’
Error: unavailable
Message: Unavailable. Please check Box API status page for information: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

Code: 504 ‘Gateway Timeout’
Message: 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’
Message: The server does not support the HTTP protocol version used in the request.

Here is a complete list of Box API errors:

*press control F to search this page

Error: bad_digest
Message: The specified Content-MD5 did not match what we received. While uploading a file, a Content-MD5 header with the SHA-1 hash of the file can be supplied to ensure that the file is not corrupted in transit. The SHA-1 hash that was supplied in the request did not match what was received in the upload. Supply a valid SHA-1 hash of the uploaded file.

Error: bad_request
Message: Required parameters supplied in the API request are either missing or invalid.

Error: cannot_make_collaborated_subfolder_private
Message: Cannot move a collaborated subfolder to a private folder unless the new owner is explicilty specified. Specify the ID of the user that the content should be transferred to by setting the field in the request.

Error: collaborations_not_available_on_root_folder
Message: Root folder cannot be collaborate. You cannot set collaborators on a user’s root folder (folder ID 0). Use a different folder ID than the root folder.

Error: cyclical_folders_structure
Message: Folder move creates cyclical folder structure. The folder ID specified in the folder move would create a cyclical folder structure (e.g. moving a folder to a sub-folder within itself). Change the folder ID for the folder move request.

Error: folder_not_empty
Message: Cannot delete – folder not empty. Delete all content from the folder before attempting to delete it.

Error: invalid_collaboration_item
Message: Item type must be specified and set to ‘folder’.

Error: invalid_grant
Message: The authorization code supplied in the API request is issing or
no longer valid. Possible solutions are:
– Verify that the access token is added correctly in the request
– If correctly set, the access token may have expired. Attempt to refresh the access token
or fetch a new one.

Error: invalid_grant
Message: Current date time must be before the expiration date time listed in the ‘exp’ claim.
This error occurs when the Unix time on your local machine and the Box server are out of sync.
To fix this error, update the Unix time on your machine to match the Unix time from this site, then try the request again.

Error: invalid_limit
Message: Limit is not a valid number. Add a valid numeric value for the supplied limit value.

Error: invalid_offset
Message: Offset is not a valid number. Add a valid numeric value for the supplied offset value.

Error: invalid_request_parameters
Message: Invalid input parameters in request. Invalid parameters were sent in the API request.

Error: invalid_status
Message: You can change the status only if the collaboration is pending.

Error: invalid_upload_session_id
Message: The upload session ID provided in the URL is not a valid format. The session ID supplied when making a chunked upload API request was invalid. Use the same session ID from the session that was created.

Error: item_name_invalid
Message: Item name invalid. Verify that the file’s name is valid. Box only supports file or folder names that are 255 characters or less. File names containing non-printable ascii, “/” or “\”, names with leading or trailing spaces, and the special names “.” and “..” are also unsupported.

Error: item_name_too_long
Message: Item name is too long. Shorten the length of the name that is being supplied for the item. The maximum length of a file or folder name in Box is 255 characters or less.

Error: password_reset_required
Message: User needs to reset password. The user has not yet completed Box account setup steps.

Error: requested_page_out_of_range
Message: Requested representation page out of range. The range header supplied does not fit within the size of the specified item. Adjust the bounds to fit within the size of the item and try again.

Error: requested_preview_unavailable
Message: Requested preview unavailable.

Error: sync_item_move_failure
Message: Cannot move a synced item. The item is set to be synced by the Box sync clients and cannot be moved.

Error: task_assignee_not_allowed
Message: Assigner does not have sufficient privileges to assign task to assignee. The user who is attempting to assign the task does not have the appropriate permissions to do so. Adjust the user permissions to allow the assignment of tasks.

Error: terms_of_service_required
Message: User must accept custom terms of service before action can be taken. The admin of your Box account has set custom terms of service and the user has not logged in to accept the terms yet. The user will need to accept the terms of service, or the admin will have to disable them, in order to proceed.

Error: user_already_collaborator
Message: User is already a collaborator. The user that you are attempting to collaborate in on an item is already collaborated on that item. This request is not needed.

Error: access_denied_insufficient_permissions
Message: Access denied – insufficient permission. This error is typically produced when scopes that are needed for the API operation were not enabled.

Error: access_denied_item_locked
Message: Access denied – item locked. You are attempting to access a locked fitem without appropriate permissions to access it. Unlock the item first, then try to access it again.

Error: access_from_location_blocked
Message: You’re attempting to log in to Box from a location that has not been approved by your admin. Please talk to your admin to resolve this issue.

Error: file_size_limit_exceeded
Message: File size exceeds the folder owner’s file size limit.

Error: forbidden
Message: Client does not have permission to upload to this session. Only the user who initiated the upload session may upload to it.

Error: incorrect_shared_item_password
Message: A password is required for the shared item, but it was either incorrect or not supplied.

Error: storage_limit_exceeded
Message: Account storage limit reached. The storage limit of the account has been reached. Either upgrade your account or permanently delete content to continue. Content that is simply moved to the trash will still count towards the account total until it is permanently deleted.

Error: user_email_confirmation_required
Message: User needs to complete email confirmation.

Error: not_found
Message: The resource could not be found.

Error: not_trashed
Message: Item is not trashed. The item that is to be permanently deleted is not in the trash. Send the item to the trash first.

Error: preview_cannot_be_generated
Message: Preview cannot be generated. You are not able to generate a preview thumbnail for the
specified file.

Error: trashed
Message: Item is trashed. The item that is to be accessed is in the trash and unavailable for modification. Move the item out of the trash and try again.

Error: conflict
Message: A resource with this value already exists. This error may be produced when the resource to be created already exists. Check the extended error message in the response body for more details.

Error: item_name_in_use
Message: Item with the same name already exists. This error is produced when a resource with the same name already exists. Ensure that the resource name being added / modified is unique.

Error: name_temporarily_reserved
Message: The item name is reserved by another processing item. Wait and then retry the request, or wait and check the parent folder to see if the name is in use. Two duplicate requests have been submitted at the same time.

Error: operation_blocked_temporary
Message: The operation is blocked by another ongoing operation. This error is returned when trying to access a folder that is blocked by another folder operation, such as a move or copy. Try again at a later interval.

Error: recent_similar_comment
Message: A similar comment has been made recently. A similar comment was recently made, and the API has flagged it as a potential duplicate. Verify that the comment was indeed made, or modify the comment content and try again.

Error: user_login_already_used
Message: User with the specified login already exists. A user with the same email already exists. Either refer to the existing user or specify a different email.

Error: session_expired
Message: The upload session associated with the given upload session ID has expired and can no longer be accessed.

Error: upload_failed
Message: The upload session is in an unrecoverable failed state and cannot continue. This or other requests have resulted in the upload session reaching a bad state (e.g. parts overlapping).
Possible situations where this may arise:
– Maximum number of parts has been exceeded
– Overlapping parts have been uploaded

Error: length_required
Message: Content-Length header was required, but not provided.

Error: precondition_failed
Message: The resource has been modified. Please retrieve the resource again and retry.

Error: sync_state_precondition_failed
Message: The resource has been modified. Please retrieve the resource again and retry.

Here is a complete list of cURL error codes:

All fine. Proceed as usual.

The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn’t use, it can be a misspelled protocol string or just a protocol libcurl has no code for.

Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn’t get done at init time.

The URL was not properly formatted.

A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl.

Couldn’t resolve proxy. The given proxy host could not be resolved.

Couldn’t resolve host. The given remote host was not resolved.

Failed to connect() to host or proxy.

The server sent data libcurl couldn’t parse. This error code is used for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0.

We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.

While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.

After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned.

During an active FTP session, while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.

libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed.

FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code is passed back.

An internal failure to lookup the host used for the new connection.

A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.

Received an error when trying to set the transfer mode to binary or ASCII.

This was either a weird reply to a ‘RETR’ command or a zero byte transfer complete.

When sending custom “QUOTE” commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.

This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400.

An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.

Failed to start the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server’s explanation for this.

There was a problem reading a local file or an error returned by the read callback.

A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs.

Operation timeout. The specified time-out period was reached according to the conditions.

The FTP PORT command returned an error. This mostly happens when you haven’t specified a good enough address for libcurl to use. See CURLOPT_FTPPORT.

he FTP REST command returned an error. This should never happen if the server is sane.

The server does not support or accept range requests.

This is an odd error that mainly occurs due to internal confusion.

A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.

The download could not be resumed because the specified offset was out of the file boundary.

A file is given with FILE:// couldn’t be opened. Most likely because the file path doesn’t identify an existing file. Did you check file permissions?

LDAP cannot bind. LDAP bind operation failed.

LDAP search failed.

Function not found. A required zlib function was not found.

Aborted by callback. A callback returned “abort” to libcurl..

Internal error. A function was called with a bad parameter.

Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections’ source IP address with CURLOPT_INTERFACE.

Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.

An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the program that uses libcurl. The error buffer might contain more specific information about which exact option it concerns.

A telnet option string was Illegally formatted.

Nothing was returned from the server, and under the circumstances, getting nothing is considered an error.

The specified crypto engine wasn’t found.

Failed to set the selected SSL crypto engine as default!

Failed sending network data.

Failure with receiving network data.

problem with the local client certificate.

Couldn’t use the specified cipher.

The remote server’s SSL certificate or SSH md5 fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

Unrecognized transfer encoding.

Invalid LDAP URL..

Maximum file size exceeded.

Requested FTP SSL level failed.

When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed.

Initiating the SSL Engine failed.

The remote server denied curl to login (Added in 7.13.1)

File not found on TFTP server.

Permission problem on TFTP server.

Out of disk space on the server.

Illegal TFTP operation.

Unknown TFTP transfer ID.

File already exists and will not be overwritten.

This error should never be returned by a properly functioning TFTP server.

Character conversion failed.

The caller must register conversion callbacks.

Problem with reading the SSL CA cert (path? access rights?)

The resource referenced in the URL does not exist.

An unspecified error occurred during the SSH session.

Failed to shut down the SSL connection.

The socket is not ready for send/recv to wait till it’s ready and try again. This return code is only returned from curl_easy_recv and curl_easy_send (Added in 7.18.2)

Failed to load CRL file (Added in 7.19.0)

Issuer check failed (Added in 7.19.0)

The FTP server does not understand the PRET command at all or does not support the given argument. Be careful when using CURLOPT_CUSTOMREQUEST, a custom LIST command will be sent with PRET CMD before PASV as well. (Added in 7.20.0)

Mismatch of RTSP CSeq numbers.

Mismatch of RTSP Session Identifiers.

Unable to parse FTP file list (during FTP wildcard downloading).

Chunk callback reported an error.

(For internal use only, will never be returned by libcurl) No connection available, the session will be queued. (added in 7.30.0)

Failed to match the pinned key specified with CURLOPT_PINNEDPUBLICKEY.

The status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS

Stream error in the HTTP/2 framing layer.

An API function was called from inside a callback.

An authentication function returned an error.

These error codes will never be returned. They were used in an old libcurl version and are currently unused.

Leave A Comment?