Skip to main content

Why your restoration isn’t completing

Why isn’t my restoration working?​

While the restoration process typically runs smoothly, complications can sometimes occur.  This page outlines some common issues and their solutions.

Note: Some of the solutions require you to edit files within your WordPress installation.  If you are uncomfortable using S/FTP or your web hosting File Manager, we recommend using a free plugin such as Advanced File Manager.  Please remember to make a backup of any files that you intend to change.

Corrupted zip files​

Example error log message:

PCLZIP_ERR_BAD_FORMAT (-10)

Solution: The files need to be downloaded again and then uploaded to replace the problematic version.

1. Download your files​

Download the files from your storage provider directly to your computer.

2. Test them​

Unzip the files and test that they are not corrupted.  If this test is unsuccessful you will need to repair them with a suitable zip repair utility.

3. Remove the old files​

Next, delete the backup set that is causing the problem from UpdraftPlus >> Backup / Restore >> Existing backups.  Ensure the ‘also delete from remote storage’ checkbox is unticked.

4. Upload​

Connect to your site via S/FTP and upload the files into the wp-content / updraft folder.

5. Rescan local storage​

Go back to UpdraftPlus >> Backup / Restore >> Existing backups and click rescan local storage for new backup sets.

6. Retry your restoration​

Click the Restore button next to the backup set you have just uploaded and follow the process.

Lack of memory​

Example error log message:

Allowed memory size of 268435456 bytes exhausted

Solution: Increase the amount of memory available to WordPress.

1. Check your server memory limit​

At the top of a backup or restoration log file, note the value next to the memory_limit directive.  This is the maximum amount of memory that is available to your server.

2. Increase your WordPress memory limit​

Your WordPress website has its own memory limit.  This can often be increased.  To do this, open your wp-config.php file and search for WP_MEMORY_LIMIT.

If this definition is already present, you can edit the value to the same as the one for memory limit found in the previous step – if it is not present you can add it above the line that says:

/* That's all, stop editing! Happy blogging. */

Example:

define('WP_MEMORY_LIMIT', '512M');

This sets the WordPress memory limit to 512MB.

Note: If your WordPress memory limit is already the same as your server memory limit, you will need to contact your host for further advice.

3. Retry your restoration​

Click the Restore button next to the backup set you have just uploaded and follow the process.

Not enough storage space​

Example error log message:

Disk quota exceeded

Solution: A lack of storage space is preventing the restoration from completing. To proceed, you’ll need to free up disk space so that UpdraftPlus can create the required files.

File permissions errors​

Example error log message:

Could not move the files into place

Solution: WordPress requires specific file and folder permissions to work correctly.  We recommend contacting your hosting company for assistance if you see this error.

There are no error messages in my log file​

Use WordPress debugging​

If your restoration fails without a clear reason, enabling WordPress debugging can help identify the issue.

Use a plugin​

For a simpler approach, install the Debug Log Manager plugin from the WordPress Plugin Directory. Activate the plugin, retry your restoration, and then review the generated log file for error messages.

Do it manually​

If you prefer to do this manually, follow the WordPress debugging instructions to enable debugging. After enabling debugging, retry the restoration and check the debug log for error details.

Are you using the Litespeed web server?​

If you are using Litespeed, edit your .htaccess file in the root directory and follow these instructions:Find the line that says:

# BEGIN WordPress

and add this code above it:

# BEGIN LiteSpeed noabort
<IfModule rewrite_module>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END liteSpeed noabort

Save your changes and then retry your restoration.

Need More Help?​

If you’re unable to resolve the issue based on the debug error log information, our support team is ready to assist you.