Troubleshooting

The issue occurred due to insufficient Google Drive space. Please free up Google Drive and make sure that there is enough Google Drive space to store backups.

In this case, go to WordPress admin dashboard of target site > WPvivid plugin > Settings > Advanced settings and decrease the value of 'Chunk size' to 512 KB and save changes. Then perform an auto-migration task again. Alternatively, you can migrate your...

The issue is usually caused by insufficient OneDrive space. Please check your OneDrive space and make sure it is sufficient for storing the backup.

The error 'Backup the file ends with an error Failed to add zip files. status string' is usually caused by insufficient disk space. Please check the disk space. Generally, the free disk space should be at least twice the size of the backup. Also, in shared hosting,...

This error can occur during a restoration or migration process. When the error occurs, our plugin can not unzip your backup. Because the backup is either incomplete or corrupted. This may happened during the process of downloading/transferring the backup file. If the...

This error means uploading the backup to pCloud timed out, which is usually caused by a network connection failure between your web hosting server and the cloud storage provider’s server. The failure can be on either end, for example, an outage of the cloud storage...

This error is usually caused by redirect plugins, e.g., Really Simple SSL plugin, on your website which has prevented the redirection to the site. You can try to temporarily deactivate the redirect plugin, then try it again. Normally the redirect plugin should have...

The full error message is like: “Oops, The restoration seems to have encountered a problem:( Please adjust the advanced settings before restoring and retry. Read more… Error Info:An exception has occurred. class: PDOException;msg: SQLSTATE[42000]: Syntax error or...

Here are two main causes of a slow backup process: 1. The disk I/O of the web hosting is slow. We have noticed that the disk IO of many web hosting is only 1MB/s,  then theoretically backing up a 100MB website would require at least 300s. You can check the disk I/O of...

During the backup process, our plugin will compress your website data into zip files to save storage space. So it is normal that your website is, for example, 5 GB(the calculation result on WPvivid backup page) while the backup will be only 1GB. You can verify a...

It can be because on your target site, there were both index.html and index.php after the restoration. By default, WordPress always reads the index.php, and a default WordPress install does not have the index.html file. The problem is that the target website reads...

First make sure to add https(to be the same as your live site) to the subdomain e.g., dev.yourdomain.com when creating the subdomain or the staging site. If the problem still persists, please contact us.

The error is related to SSL certification. Please make sure you have correctly configured SSL certifications for the source and target sites. Here is a thread for how to fix the issue:...

Please temporarily deactivate your firewall plugin, then authenticate your cloud storage again.

It is because the white label name included special characters. The white label name can contain numbers, lowercase/uppercase letters, underscores and spaces only. Please rename white label name without any special characters.

The error is caused by insufficient server disk space. To fix it, check and make sure that the available disk space of the web hosting account is at least twice the size of the website.

1. Please manually upload an image to Media library of your site. Then try to backup again. 2. If the problem occurred after a site migration, the issue might be due to the Media path is set incorrectly and still refers to the old website. So, you need to update the...

Generally, the problem occurs while WP Cron might not be working properly. Please install WP Crontrol plugin to check your WP Cron system and make sure that it works correctly. Additionally, you can use phpMyAdmin to access your database > wp_options >...

This error occurs because there is WPvivid pro activation information in the database of the backup, indicating that you had once activated WPvivid pro on the site where the backup was made, but there is no WPvivid pro plugin folder in the backup, also there is no...

This error occurs because the PHP curl extension is required. So, please install the curl extension first then try it again.

This error is due to maintenance downtime or capacity problems with your web hosting server. Therefore, we recommend that you check whether the server resources of the site are sufficient, such as disk space and memory.

It can be because you are using a custom port for the FTP server, in that case, make sure the custom FTP port is allowed by the hosting provider.

Here are few possible causes and solutions to the problem: 1. The site is hosted on WordPress.com WordPress.com is different from WordPress.org self-hosted sites configuration, for example, the files and folders structure. And our plugin is developed based on the...

That is because by default, our plugin splits a backup to multiple parts(200MB for each) to increase backup success rate, especially for websites with shared web hosting. However, you do have the option to finally get a single backup file by changing the following...

The 403 error always means the access to the requested resource is forbidden, our guess is that there can be a firewall(security) on your target site that is blocking the transfer. In that case, the Manual transfer option is recommended.

It is usually because you have enabled WPvivid white label option on the source site,which has changed the wpvivid slug in the backup file name, causing the backup was not identified by the plugin. The current solution is to enable the white label(using the same brand...

It is because you are still using a pretty old version of WPvivid Pro, which is probably causing the problem. So, it is recommended that you delete it and install the latest version of the Pro plugin(you can always download the latest version of the pro version from...

The JSON error is usually a parsing error caused by unparseable content in the json result returned by the server after sending an ajax request, it is actually an error with the website itself rather than the plugin. When the error occurs, you can use the browser’s...

This error is usually caused by security settings on the site, or the sever side, which are blocking the file uploading. To solve the issue, please check and change the relevant security settings on the site or the server to allow the uploading. Alternatively, you can...

Make sure you have assigned 755 permissions to all your WordPress folders and files. After that, please install and activate the pro version again.