Box Extension Error Codes

The All-in-One WP Migration plugin communicates with your Box account and stores backups using the Box API. If there is a problem communicating with your Box and the files in your account, you may receive one of these errors.
Box cloud storage allocates a per-user quota to each user to distribute resources fairly. You may experience problems if you have a large number of other applications or systems connected to your Box.

What can you do about it?

Please see the list of error codes below for more information on each one:

Invalid Credentials
The All-in-One WordPress Migration Plugin is unable to connect to your Box. Please sign out of your Box account and sign back in to the Box Settings plugin on your WordPress Console.

The user does not have sufficient permissions for file
The All-in-One WP Migration Plugin is unable to access any files or folders on your Box. Please ensure that the file or folder you are attempting to access with the plugin is accessible via your Box account.
If this does not work, or if the file is on your Box drive, please sign out of your account and sign back in to the Box Settings page of the plugin on your WordPress Console.

Cannot be used within the domain
The All-in-One WP Migration Plugin is unable to connect to your Box. If you’re attempting to backup or migrate your site while logged in on a corporate domain, make sure you can access your Box account or contact the domain administrator.

File not found
The All-in-One WP Migration Plugin is unable to access any files or folders in your Box account. Please double-check that the file exists and that you can access it via your Box.

Backend Error
While processing the request, an unexpected error occurred with your Box storage. Please try once more. Please sign out of your Box account and re-sign in to the Box Settings page of the plugin in your WordPress Console.

Bad Request
The All-in-One WP Migration Plugin is unable to connect to your Box account. Please sign out of your Box account and sign back in to the Box Settings of the plugin on your WordPress Console.

User Rate Limit Exceeded
On your Box account, there have been too many API calls. After stopping drive sync and any other applications that connect to your Box and waiting 5 minutes, try again.

Rate Limit Exceeded
On your Box account, there have been too many API calls. After stopping drive sync and any other applications that connect to your Box and waiting 5 minutes, try again.

Sharing Rate Limit Exceeded
You have reached your Box account’s sharing rate limit. This could be related to emails or documents that you are publicly sharing from your Box. When performing backups/migrations, avoid sending large volumes of emails. Remove permissions from publicly accessible files in your Box storage.

The user has not granted access to the file
The All-in-One WP Migration Plugin is unable to access any files or folders on your Box. Please ensure that the file or folder you are attempting to access with the plugin is accessible via your Box account. If this does not work, or if the file is already on your Box storage, please sign out of your account and sign back in to the Box Settings page of the plugin on your WordPress Console.

Too Many Requests
There have been an excessive number of requests on your Box account. This could be related to documents you’re publicly sharing from your Box storage or other applications that use your account.

Here is a complete list of HTTP error codes:

*press control F to search this page

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

Code: 401 ‘Unauthorized’
The authorization token is not authorized. Authentication is required and has either failed or has yet to be provided.

Code: 402 ‘Payment Required’
You must pay for the product in order to proceed.

Code: 403 ‘Forbidden’
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’
Could not find the resource. Could not find the requested resource but it may be available in the future. Subsequent requests by the client are permissible.

Code: 405 ‘Method Not Allowed’
Method not allowed. The API operation does not allow the HTTP method.

Code: 406 ‘Not Acceptable’
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 Timed Out’
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 willing to wait.  Repeat the request without modifications at any later time.

Code: 409 ‘Conflict’
The conflict does not allow the request to process.

Code: 410 ‘Gone’
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’
Length required. The request did not specify the length of its content, which the requested resource requires.

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’
Request entity too large. This error occurs when the size of the upload is more than the allowed maximum.

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’
Unsupported media type. The request entity has a type which the server or resource does not support.

Code: 416 ‘Requested Range Not Satisfiable’
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’
Expectation failed. The server cannot meet the requirements of the Expect request-header field.

Code: 500 ‘Internal Server Error’
Internal server error. This is a generic error message, which is given when you encounter an unexpected condition and no other specific message is suitable.

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

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’
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’
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 Box API errors:

*press control F to search this page

Error: bad_digest
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
Required parameters supplied in the API request are either missing or invalid.

Error: cannot_make_collaborated_subfolder_private
Cannot move a collaborated subfolder to a private folder unless the new owner is explicilty specified. Set the owned field in the request to the ID of the user receiving the content.

Error: collaborations_not_available_on_root_folder
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
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
Cannot delete as the folder is not empty. Delete all content from the folder before attempting to delete it.

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

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

Error: invalid_grant
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
Limit is not a valid number. Add a valid numeric value for the supplied limit value.

Error: invalid_offset
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
You can change the status only if the collaboration is pending.

Error: invalid_upload_session_id
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
Item name invalid. Verify that the file’s name is valid. Box only supports file or folder names that are 255 characters or less. Does not support file names containing non-printable ascii, “/” or “\”, names with leading or trailing spaces, and the special names “.” and “..”.

Error: item_name_too_long
Item name is too long. Reduce the item’s name’s length. The maximum length of a file or folder name in Box is 255 characters or less.

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

Error: requested_page_out_of_range
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
Requested preview unavailable.

Error: sync_item_move_failure
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
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
User must accept custom terms of service before taking action. 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
User is already a collaborator. The user with whom you want to collaborate on an item has already done so. This request is unnecessary.

Error: access_denied_insufficient_permissions
Access denied as there is insufficient permission. This error is typically occurs when the necessary scopes for the API operation are not enabled.

Error: access_denied_item_locked
Access denied as the item is 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
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
File size exceeds the folder owner’s file size limit.

Error: forbidden
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
The shared item requires a password, but it was either incorrect or not supplied.

Error: storage_limit_exceeded
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
User needs to complete email confirmation.

Error: not_found
Could not find the resource.

Error: not_trashed
Did not trash item. The item that you intend to permanently delete is not in the trash. Send the item to the trash first.

Error: preview_cannot_be_generated
Cannot generate the preview. You are not able to generate a preview thumbnail for the specified file.

Error: trashed
Item is in the trash. The item that you are trying to access is in the trash and unavailable for modification. Move the item out of the trash and try again.

Error: conflict
A resource with this value already exists. This error may occur when the potential resource already exists. Check the extended error message in the response body for more details.

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

Error: name_temporarily_reserved
Another processing item is reserving the item name. 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
The operation blocked another ongoing operation. This error returns when trying to access a folder that another folder operation blocks, such as a move or copy. Try again at a later interval.

Error: recent_similar_comment
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
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
The upload session associated with the given upload session ID has expired and can no longer be accessed.

Error: upload_failed
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:
– You have exceeded  the maximum number of parts
– You have uploaded overlapping parts

Error: length_required
Requires a Content-Length header that was not provided.

Error: precondition_failed
It is a modified resource. Please retrieve the resource again and retry.

Error: sync_state_precondition_failed
It is a modified resource. 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. Could not resolve the given proxy host.

Couldn’t resolve host. Could not resolve the given remote host.

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 passes 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. Could not find a required zlib function.

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

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

Interface error. Could not use a specific outgoing interface. 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 return. They were used in an old libcurl version and are currently unused.

Leave A Comment?