Mega Extension Error Codes

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

What can you do about it?

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

Please see more specific detail about each error code below:

Invalid Credentials
The All-in-One WP migration plugin can not connect to your Mega account. Please sign out from your account and sign in again in the Mega 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 Mega drive. Please check that your Mega 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 Mega 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 Mega drive. 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 Mega 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 Mega drive. Please check that the file exists and that you can access it through your drive.

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

Bad Request
The All-in-One WP migration plugin can not connect to your Mega account. Please sign out from your account and sign in again in the Mega 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 Mega 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 Mega drive. 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 Mega Settings page of the plugin on your WordPress Console.

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

Here is a complete list of HTTP error codes including their meaning in Mega API:

*press control F to search this page

Code: 400 ‘Bad Request’
Message: Cannot process the request because it is malformed or incorrect.

Code: 401 ‘Unauthorized’
Message: Required authentication information is either missing or not valid for the resource.

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

Code: 403 ‘Forbidden’
Message: Access is denied to the requested resource. The user might not have enough permission.

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

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

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

Code: 408 ‘Request Timeout’
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: The current state conflicts with what the request expects. Request could not be processed because of the conflict.

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

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

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: The request size exceeds maximum limit.

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: The content type of the request is a format that is not supported by the service.

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

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

Code: 422 ‘Unprocessable Entity’
Message: Cannot process the request because it is semantically incorrect.

Code: 429 ‘Too Many Requests’
Message: Client application has been throttled and should not attempt to repeat the request until an amount of time has elapsed.

Code: 500 ‘Internal Server Error’
Message: There was an interntal error while processing the request.

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

Code: 502 ‘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’
Message: The service is temporarily unavailable. You may repeat the request after a delay. There may be a Retry-After header.

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.

Code: 507 ‘Insufficient Storage’
Message; The maximum storage quota has been reached.

Code: 509 ‘Bandwidth Limit Exceeded’
Message: Your app has been throttled for exceeding the maximum bandwidth cap. Your app can retry the request again after more time has elapsed.

Leave A Comment?