• Resolved AeroWeb

    (@aeroweb)


    We’ve been using this plugin for years now to make copies of websites so we can work on them locally before making the updates live on the main site. However for the last month or so been running into a lot of problems.

    When attempting to restore a website the process often fails about half way through during the database import with an AJAX 500 error. The database is only 44MB and after several attempts it the db import process sometimes goes further and fails at 80%. Is this a timeout issue?

    We’ve restored websites with much larger databases in the past. Any idea why this is happening?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support devdavidam

    (@devdavidam)

    @aeroweb a 500 level error is related to the server. Have a look at the following FAQ item for more information about this.

    Thread Starter AeroWeb

    (@aeroweb)

    Thanks, I found the issue!

    This is only a problem if you are moving the website to a different domain. (we do this as a staging area when we work on a website) If you are restoring the website to the same hosting account with the same domain and username this is not an issue.

    Bottom line the problem was with WordFence. However just disabling the plugin doesn’t work. If you have the firewall in WordFence “optimized”, it makes changes to your .htaccess, php.ini and/or .user.ini files by adding a path to the configuration files. This path will more than likely not be compatible if you are moving the website to another location.

    The fix for this is to remove the firewall optimization before you disable the plugin in order to get Duplicator to work when migrating a website. We never had to deal with this in the past. We always modified the .htaccess, php.ini and/or .user.ini as needed after Duplicator was done with its restore.

    I suspect either something changed in Duplicator restore process where this causes an error now, or perhaps the restore process finished more quickly before the new extracted php.ini and .user.ini files kicked in and caused an error.

    Would be great if Duplicated updated their restore process to maybe suppress any .htaccess, php.ini or .user.ini files until the end of the restore process. Or possibly edit these file during the restore with the updated path of the new host location.

    Plugin Support devdavidam

    (@devdavidam)

    @aeroweb thanks for the feedback.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Restore fails on database import’ is closed to new replies.