WordPress Duplicator - FAQs

Auto Install

1. Go to: WordPress Admin ❯ Plugins ❯ Click "Add New"
2. Search for "Duplicator" ❯ click "Install Now" ❯ click "Activate"

1. Download the plugin from one of the following locations:
• The link in the purchase receipt email you received when you purchased the product
• The Snap Creek dashboard at https://snapcreek.com/dashboard
2. Login to the WordPress Admin ❯ Plugins ❯ Add New ❯ Click "Upload Plugin"
3. Click "Choose File" ❯ select the .zip file you downloaded ❯ click "Install Now" ❯ click "Activate"

Manual Install

1. Download the Pro/Lite plugin zip file to a temporary location on your local computer.
   • For Pro login to your Snap Creek dashboard then click on the "Downloads" tab.
   • For Lite go to the Duplicator Page at wordpress.org and click the blue download button.
2. On your local computer extract the Pro/Lite plugin zip file to a temporary directory (e.g. C:\temp\duplicator\).
3. Open an FTP Client -OR- go to your host's control panel (cPanel) file manager.
4. Create a new directory in your sites WordPress plugins directory via sample examples below.
   Contact your hosting provider or server admin for the exact path if you are unable to locate it.
   • /public_html/my_site/wp-content/plugins/duplicator/
   • /public_html/my_site/wp-content/plugins/duplicator-pro/
5. Copy the extracted contents of the zip file from step 2 to the new plugin directory just created.
   Note: The files duplicator.php and duplicator-pro.php and the other plugin zip content should be at the root of the directories in Step 4.
6. Open your WordPress Admin ❯ Plugins ❯ Activate Duplicator Pro/Lite
   The manual install process should be completed.

Auto Remove

1. Go to Plugins ❯ Duplicator Lite/Pro ❯ click Deactivate
   Note: Be sure the plugin does not have any active schedules or builds running when trying to remove
2. After the plugin is deactivated click Delete

Manual Remove

1. Open a FTP Client - OR - go to to your hosts control panel (cPanel) file manager.
2. Navigate to the sites plugins directory. It might look something like this:
   /public_html/my_site/wp-content/plugins/duplicator/ Duplicator Lite
   /public_html/my_site/wp-content/plugins/duplicator-pro/ Duplicator Pro
3. Select the "duplicator-pro" folder and remove it and all of its contents
   Note: Be sure the plugin does not have any active schedules or builds running when trying to remove

Auto Update

Manual Updates

Overview

• Full WP-CLI Guide
• Installing WP-CLI
• XAMPP WP-CLI Setup

Duplicator Lite

1. Open a command line (Windows/Mac/Linux).
2. Navigate to the root of the WordPress site to install to for example:
   cd /public_html/mywordpresssite/
3. From the command line type:
   wp plugin install duplicator --activate

Duplicator Pro

1. Open a command line (Windows/Mac/Linux).
2. Navigate to the root of the WordPress site to install to for example: cd /public_html/mywordpresssite/
3. From the command line type:
   Single Site wp plugin install http://[URL_YOUR_COMPUTER_CAN_REACH]/duplicator-pro-4-5-0.zip --activate MultiSite wp plugin install http://[URL_YOUR_COMPUTER_CAN_REACH]/duplicator-pro-4-5-0.zip --activate-network

Upgrade Duplicator Lite to Pro

Upgrade Duplicator Pro

1. Change the file upload limit to 5MB or greater, by following these instructions.
2. Restart your web server for the changes to take place
3. To make sure the value has been updated and taken affect follow these steps:
   1. Install the PHP Info plugin and activate.
   2. Go to Settings ❯ PHP Info and then search for "upload_max_filesize"
   3. Check to make sure the value is set to 8M
   4. Alternatively: Contact your host and ask them to: "Change the php.ini setting for upload_max_filesize to 5MB"

1. Download the latest version of the plugin from snapcreek.com/dashboard
2. On Plugins screen ❯ disable and delete the old version of Duplicator Pro
3. On Plugins screen ❯ click 'Add New' and upload the new version of Duplicator Pro & activate

1. Go to Settings ❯ Licensing
2. Add your license key in the box
3. Click the Activate button
4. Go to the Plugins screen and update the plugin

1. Download the latest version of the plugin from snapcreek.com/dashboard
2. On your WordPress admin, go to Duplicator Pro ❯ Settings and make sure the uninstall options "Delete plugin settings" and "Delete entire storage directory" are UNCHECKED
3. Go to your website's plugin list & Disable and then delete the old version of Duplicator Pro
4. On the plugins screen, click Add New and upload the new version of Duplicator Pro and Activate

1. Download the latest version of Duplicator Pro from the Snap Creek Dashboard
2. On your WordPress Admin, go to Duplicator Pro ❯ Settings
3. Ensure "Delete Plugin Settings" and "Delete Entire Storage Directory" are both unchecked
4. Uninstall the old version of Duplicator Pro
5. On the plugins screen, click Add New and upload the new version of Duplicator Pro
6. Activate the new version

1. Download, install and activate the plugin from your purchase email link or from your snapcreek.com dashboard.
2. Goto: Duplicator Pro ❯ Settings ❯ Licensing ❯ Enter your key and click activate.

1. Try to deactivate and reactivate your license a few times, waiting a minute or two between tries.
2. Deactivate & reactivate the plugin from the WordPress admin plugins screen then try the key activation again.

• Contact Host: Contact your host or server admin and ask them to monitor what is happening when you click the license activate button. Specifically, ask if communication is getting blocked between your server and snapcreek.com. If they observe nothing getting blocked on their side then proceed to the step below.
• IP Checks: Gather the following IP addresses by going to WordPress Admin ❯ Duplicator Pro ❯ Tools ❯ General Tab ❯ Server Settings ❯ "Server IP", "Outbound IP", "Client IP". If any are blank then contact your host or system network administrator as its located at the router layer, and we must have all of them in order to properly diagnose the issue from our end. Note: If you on are a localhost server its possible you may see "::1" for "Server IP" and "Client IP". If this is the case for localhost then provide the "Outbound IP".
  
  Once you have all the IPs submit a ticket or reply to an existing ticket with all IP addresses. We will then check to see if they are being blocked on the snapcreek.com end. This is typically very rare although it can happen if your server's IP has been placed on a blacklist of some kind.

1. Login to your dashboard
2. Click View Licenses Link ❯ Manage Sites Link
3. Add/remove URLs that you need to manage licenses on

Renewal Steps

1. Browse to snapcreek.com and purchase the product you are currently using.
2. At Checkout click "Renewing a license key?" and add your license key to get your 40% off discount.
3. Continue with checkout and your license renew date will be updated upon purchase.

1. Log-in to the SnapCreek dashboard snapcreek.com/dashboard
2. Click the "Views Licenses" then click "Extend License"
3. This will take you to your shopping cart with the discount applied.

Renewal Prices

Upgrade Steps

1. Login to your snapcreek.com dashboard
2. Goto: Purchases tab ❯ 'View Licenses' ❯ 'View Upgrades'
3. Choose the upgrade level and checkout.
   Note: When upgrading to a different version the billing will automatically get handled for you.
4. In your WordPress Admin: Go to Duplicator Pro ❯ Settings ❯ Licensing. This will retrieve the license level from our server so you should see information that describes the level which you just upgraded to.

Upgrade Prices

Overview

1. Renew while your license is a Freelancer for $106.80 (40% off the $178.00)
2. Upgrade from Freelancer to Business for $120.00 as a second step.

• If you run into technical issues please allow us to adequately try and assist you. If we are unable to resolve the issue, we will promptly provide a refund. Please open a support ticket before requesting a refund for a technical issue.
• Refunds may only be issued within 14 days of the purchase date. After 14 days refunds cannot easily be processed. Please be sure to test and use the plugin upon purchase.

• PayPal: See PayPals step-by-step instructions.
• Stripe/Other: For other payment types submit a ticket and we will cancel it.

1. Use the help ticket system
2. Provide your license key, first and last name of the purchaser of the product
3. Submit your ticket and we will get back with you

1. Click on the Account link in the upper right corner
2. Click on the "Lost Password?" link at the bottom of the login form.
3. Enter the username/email used when purchasing the product and click the button.
   If the username/email is not found then the form will not submit; see "Forgot Username" above.
4. An email will arrive shortly with a link that will let you reset your password.
   Be sure to double check your SPAM folder if you don't receive an email from snapcreek within 5-10 minutes.
5. Click on the link in the email. This will take you to a form where you can reset the password.
6. Enter in any password you like, this includes a previous password you may have used.
7. Now enter in your username/email with the password you just updated into the login form.

• Theme Editor Enable/Disable
• Autosave Interval
• Post Revisions

• SSL Enforce on Admin
• Generate New Unique SALTS and Authentication Keys
• Core Auto-Update Control

• Cache Control
• WP Debug Enable/Disable
• WP Debug Log Enable/Disable
• WP Debug Display Enable/Disable
• Script Debug Enable/Disable
• Save Database Queries Enable/Disable
• Cookie Domain
• Memory Limit
• Max Memory Limit

PHP Support

• Duplicator requires PHP 5.3.8+ or higher. Contact your host to upgrade to a stable secure version of a PHP Release
• To create a zip file the plugin requires ZipArchive extension -OR- shell_exec for PHP with zip support enabled. Contact your host to enable. Alternatively you can also use the DupArchive format found on the Duplicator ❯ Settings ❯ Packages Tab ❯ Archive Engine.

Permissions

• Paths that are listed in this section should have permissions of 755 for directories and 644 for files. On some hosts the permission set requires 777. Setting items to 777 is a security issue and should only be set temporarily. Please avoid any hosting company that requires this kind of setup.
• Also be sure to check the Owner/Group settings and validate they are correct and match other successful directories/files that are accessible. For more details contact your host or visit their help pages for more information on how they implement permissions and group settings.

Server Support

• WEB SERVER: The Duplicator currently works with these web servers: Apache, LiteSpeed, Nginx, Lighttpd, IIS, WebServerX. However the best success we have seen with Apache
• DATABASE SERVER: In order to complete an install the mysqli extension for PHP is required. If you are on a hosted server please contact your host and request that mysqli extension be enabled. For more information visit: http://php.net/manual/en/mysqli.installation.php

Installation Files

• Contact your host and ask them to enable the PHP function in question.
• Some hosts have an interface that will allow you to disable/enable features through a control panel such as this.
• Open your php.ini file and look for disable_functions and remove the function you want enabled.

Hosted Server

Your Computer

PHP 7+ Linux

Additional Resources

Also see: How do I do a 'Manual Extraction' or run installer without Zip enabled?

1. Foreign JavaScript - OR - "Other Plugins/Themes JS"
2. Foreign CSS - OR - "Other Plugins/Themes CSS"

1. Open your browser console, how-to instructions here: https://balsamiq.com/support/faqs/browserconsole/
2. Retry the action that was causing issues.
3. Copy any error messages that show up in the browser console and create a help ticket. An image screen-shot capture is preferred.

• Try User Role Editor Plugin: Install plugin, then enable the 'export' capability on the current role (most commonly Administrator). Note: When editing Administrator you must enable "Show Administrator role at the User Role Editor" in the Settings ❯ User Role Editor menu.
• Edit functions.php Add the following to your functions.php
  $admin_role = get_role( 'administrator' );
$admin_role->add_cap( 'export', true );


Also see:
WordPress Form: Menu Tools - Export Missing
WordPress Codex: Roles and Capabilities

1. No forwarding
2. Forward to subfolder without service separation
3. Forward to subfolder with service separation
4. Forward to IP/Host/URL

Also see:
What can I do for issues with migrating a large site?
What can I try for 502/503/504 Gateway issues during the scan/build?
Recommended hosting providers for Duplicator?

1. Log in to Cloudflare
2. From Overview Page click "Advanced" ❯ Click "Pause"
3. Run installer deployment
4. Turn Cloudflare back on

Also see:
What can I try for 502/503/504 Gateway issues during the install?
Recommended hosting providers for Duplicator?

To resolve this issue please do the following:

1. Go to: WordPress-Admin ❯ Duplicator Pro ❯ Settings ❯ Packages Tab ❯ Advanced Settings
2. Change Thread Lock Type to "SQL"
3. Change JSON to "Custom"
4. Retry building a package

1. Go back to step one "1-Setup" and click the [root path] quick link to add the WordPress root directory as a filter then run the scanner.
2. If this works then continue adding and removing directories until you can locate the problem area. Start with the top-most directories and work your way down if not then see "Test 2" below.

1. Go to Settings ❯ Packages ❯ Advanced Settings
2. Change the AJAX setting to 'https' ❯ save settings ❯ retry build

1. Go to Settings ❯ Packages ❯ Advanced Settings
2. Enable "Client-Side kickoff" ❯ save settings ❯ retry build

1. Go to Settings ❯ Packages ❯ Advanced Settings
2. Set "Basic Auth" to the credentials you normally enter in the popup ❯ Save settings ❯ retry build

1. Disable any security plugins ❯ Run a package build
2. If build works, turn back on plugins and isolate the setting preventing the build

1. Go to Settings ❯ Packages ❯ Basic Settings
2. Change 'Archive Engine' to 'DupArchive'

1. Go to Settings ❯ Packages ❯ Basic Settings
2. Change 'Archive Engine' to 'ZipArchive'

Also see:
What can I do for issues with migrating a large site?
Recommended hosting providers for Duplicator?

1. Determine what plugin is actively writing or removing files on your site.
2. Deactivate that plugin temporarily ❯ Build the package ❯ Reactivate plugin.

If you can't determine which plugin is causing the problem, add the cache directory to the file filter:

1. Click Enable File Filters
2. Click the cache link above the Directory box.

• Lite Only: Go to Settings ❯ Package Tab and turn off "Archive Flush". This setting forces a ZipArchive close response after so many files have been loaded. This process can help with FCGI setups. If your package is not building with this setting it is recommended to turn it off.
• Pro Only: Go to Settings ❯ Packages Tab ❯ Archive Engine ❯ "Shell Exec" if available and then retry the build.

Also see: How do "Shell Zip", "ZipArchive" and "DupArchive" engines differ?

1. Visitor hits your site
2. As part of WordPress page processing, Duplicator Pro determines package needs to build
3. Package starts building

1. Go to Duplicator Pro > Packages > Advanced and see if “Client Side Kickoff” is enabled.
2. If it is enabled, uncheck it.
   • If it is NOT enabled, then skip the rest of these steps and go to option #2 client Side Kickoff is not a problem
3. Go to Duplicator Pro > Schedules, hover over your schedule and click “Run Now”
4. Observe if the package builds or gets stuck at a certain percentage.
5. If the package builds then you are good and the package should not time out.
6. If the package gets stuck/doesn’t build, re-enable Client Side Kickoff and proceed to the next option below.

1. In Duplicator Pro ❯ Settings ❯ Packages set Server Throttle to Off or Low at the most
2. In Duplicator Pro ❯ Settings ❯ Packages set Max Build Time to at least 270 Minutes
3. Set your schedule build time to a time when you will be getting a decent amount of traffic

• Site-1 [Size 250MB]: Starts @ 1:00am
• Site-2 [Size 500MB]: Starts @ 1:02am (2 minute offset for Site 1)
• Site-3 [Size 1.0GB]: Starts @ 1:06am (4 minute offset for Site 2)
• Site-4 [Size 3.0GB]: Starts @ 1:14am (8 minute offset for Site 3)

• Duplicator Pro: See path: /your_site/wordpress_root/wp-content/backups-dup-pro (or the new storage path you setup) on your web-server.
• Duplicator Lite: The path will be in only one of the following:
  • Content Path: '/public_html/wp-content/backups-dup-lite/'
  • Legacy Path: '/public_html/wp-snapshots/' folder (from your WP root)

• Duplicator Pro: Settings ❯ Storage and check the box "Disable .htaccess File in Storage Directory" & save.
• Duplicator Lite: Settings ❯ General and check the box "Disable .htaccess File in Storage Directory" & save.

AddType application/octet-stream .zip .log .sql .daf

• Goto: WordPress Admin ❯ Settings ❯ WordPress Address (URL) & Site Address (URL)
• Change the values from http to https. If the values are disabled you can update by changing your admin URL to https://mysiste.com/wp-admin/options.php
• Try to download the installer or archive file from the main menu or the package details screen.
• For a full overview on how to change these values back see this article

Import Install

Overwrite Install

Classic Install

Database Only Install

1. Create a file called test.txt on your local computer with the text "Hello World" and save it.
2. FTP the test.txt file to your server and observe the path you place it in.
3. Open a web browser and browse to http://www.yoursite.com/test.txt you will get one of two results:
   • A message that says something like 404 file not found
   • The results of the text file with show "Hello World", meaning you found the correct path.
4. Keep moving the file around in the various directories on your server until you can locate the test.txt file
5. Additional details for control panels that use the cPanel software can be found here.

Dear YOUR_HOST,

I would like to install a WordPress site on my domain "http://YOUR_DOMAIN_NAME_HERE.com", however I'm not 100% sure where this domain name maps to on the servers file structure. Could you please point me to the full path for where this domain name points to on the server?

Thanks

1. Build Process: When an archive.zip/daf is created the .htaccess file is added in a hashed format .htaccess_[secure-hash]
   example: .htaccess_048063d-14160036.
2. Installer Step 1: When archive file is extracted in Step 1 it will extract the file in this .htaccess_[secure-hash] format.
   • This is by design so that the .htaccess file from the old system is not executed by the server with parameters that do not correlate to the new environment.
   • Trying to run the .htaccess file from the original server can and does cause issues on the new server in many cases. So a .htaccess file is only made available till the install is completed in step 4.
   • The .htaccess_[original-hashed] will be temporarily available until step 4 is ran. This allows for the advanced options in step 1 to considered if needed.
3. Installer Step 4: After step 3 is ran either the .htaccess_[original-hashed] will be used if you enabled the option in step 1 or a new basic one will be created.
   1. If the advanced option is chosen then the .htaccess_[original-hashed] file will be renamed to .htaccess at the end of Step 3 and start of Step 4
   2. If no option is chosen then the default mode of creating a new streamlined .htaccess file is performed and the .htaccess_[original-hashed] is removed.
4. Existing .htaccess: If you have a .htaccess file in the directory with the archive.zip/daf file before step 1 is ran then that file will be backed up and look something like: .htaccess-200314160148-5e6cffec5ff52-duplicator.bak

1. Build Process: When an archive.zip/daf is created the wp-config.php file is renamed and placed in a special directory in the archive \dup-installer\original_files_[secure-hash]\source_site_wpconfig example: \dup-installer\original_files_048063d-14160036\source_site_wpconfig.
2. Installer Step 1: When the installer extracts the archive.zip/daf file in Step 1 it will extract this directory with the renamed wp-config.php file.
3. Installer Step 3: In step 3 on the options WP-Config file tab there are optional parameters to add to the wp-config.php file.
4. Installer Step 4: This process will generate the wp-config.php based on the new environment settings and additional settings from step 3

1. Build Process: When an archive.zip/daf is created it will build a complete copy of your database into one single file in a hashed format named dup-database___[original-hashed].sql example: dup-database__4ae9c8c-14214644.sql. The .sql file can be built in two separate SQL modes "Mysqldump" and "PHP Code".
   • Mysqldump: This format uses a program called mysqldump to generate your SQL File.
   • PHP Code: This format uses PHP code to generate SQL statements that contain your entire database.
2. Installer Step 1: When the installer extracts the archive.zip/daf file in Step 1 it will lay-down the SQL file (dup-database___[original-hashed].sql) on disk.
3. Installer Step 2: The process will execute the SQL data file and install an exact copy of how it was built into the specified database choose in the installer (step 1)
4. Installer Step 3: This step is where the database data is updated to support its new environment. The update engine runs through every cell in the database looking for the old URL of the source site (old site) replacing it with the destination site (new site).

1. If your on the same server and setting up the database for Site B you accidentally connected it to Site A database.
2. A WordPress redirect plugin (if you have one installed) may have not properly gotten updated during the install and is pointing to the URL on Site A.
3. A web server configuration file such as a .htaccess or .htconfig setting is causing conflicts on the server. This option is really rare but its always a good idea to double check the files.

1. On your local computer see "LOCALHOST" steps. On a host/remote server see "REMOTE-HOST" steps.
   Note: Local computer setups require software such as XAMPP, MAMP, WAMP, Flywheel or similar applications
   
   LOCALHOST
   • Place installer.php & {archive}.zip files in an empty directory where you want to install your site.
   • Open your computers file browser ❯ navigate to the {archive}.zip ❯ extract zip file.
     Note: Make sure archive contents are not extracted into their own subdirectory
   REMOTE-HOST
   • Open your hosts file browser utility (cpanel) or FTP ❯ to an empty directory where you want your site.
   • Transfer both the installer.php & {archive}.zip files to your desired directory.
   • Extract the zip contents directly into the same directory as the {archive}.zip file
     Note: Make sure archive contents are not extracted into their own subdirectory
2. Open a web browser and browse to the http(s)://your_site_location/installer.php file.
3. Goto Step 1 ❯ Advanced Mode ❯ Options Section ❯ Advanced Tab ❯ Extraction Mode ❯ 'Manual Archive Extraction'
4. Complete the install process. This mode will simply skip the installers extraction process.

1. On your local computer see "LOCALHOST" steps. On a host/remote server see "REMOTE-HOST" steps.
   Note: Local computer setups require software such as XAMPP, MAMP, WAMP, Flywheel or similar applications
   
   LOCAL-HOST
   • On you local computer place the {archive}.daf in an empty directory where you wish to install your site.
   • Extract the daf contents directly into the same directory as the {archive}.daf file
   REMOTE-HOST
   • On you local computer place the {archive}.daf in an empty on your computer.
   • Extract the daf contents of {archive}.daf file
   • FTP the files to your remote server including the installer.php file but not the {archive}.daf file.
2. Open a web browser and browse to the http(s)://yoursite/installer.php file.
3. Goto Step 1 ❯ Advanced Mode ❯ Options Section ❯ Advanced Tab ❯ Extraction Mode ❯ 'Manual Archive Extraction'
4. Complete the install process. This mode will simply skip the installers extraction process.

Also See:
Video: How to extract zip file on cPanel

1. Change your hosts file* to make your domain name point to the new location
2. Browse to the installer.php and install the site
3. Test to ensure everything is working
4. On your domain registrar, switch to your new host's DNS servers
5. After you are confident the DNS changes have propagated remove the entry in your hosts file

1. Open an FTP Client -OR- go to your host's control panel (cPanel) file manager.
2. Copy the archive.zip/daf file to the WordPress root -OR- to \wp-content\backups-dup-pro\imports directory.
   Note: The WordPress root is normally where your wp-config.php is located allow with the wp-admin and wp-content folders.
3. Browse to Duplicator Pro ❯ Import screen and look for the uploaded archive file in the archive list.

1. htaccess File: A block via htaccess file. For example an .htaccess files placed in the wp-content folder that prevented execution might look like this:

   <Files *.php>
   Order Deny,Allow
   Deny from all
   </Files>

   The presence of an .htaccess file in wp-content does not necessarily prevent execution. Solution: Temporarily rename the htaccess file
2. Security Plugin: Some plugins like Wordfence "might" try to block the request. If this is the case try to temporarily disable the plugin to see if it resolves the issue.
3. Host or Software If the hosting has set the block via server setting the only solution is to ask the hosting to deactivate the block or change hosting On other systems software like Secure 360 have the ability to prevent the execution of PHP files via cPanel settings.

1. Clean out Directory: Delete all the exiting files of your WordPress site. If your not sure contact your host.
   Its not required but having your host backup all the current files and database is a good idea.
2. Copy Package: Place the archive.zip/daf file and the installer.php file inside of the directory you just cleaned out.
3. Run Installer: Open a web browser and browse to http://yoursite/installer.php and run through the setup.

• Hire a professional developer to troubleshoot your issue.
• Have your site cleaned by a service like WordFence
• If your in a hurry or not familiar with Duplicator, consider hiring a professional developer.

1. How to Fix the 403 Forbidden Error in WordPress
2. Apache giving 403 forbidden errors - Stack Overflow
3. How to resolve 403 Access Denied message?

1. Web Server: Check to make sure the web server is setup properly. Create a new file named test.php in the same location as the installer.php file. Inside the test.php file place the following code:

   <?php phpinfo(); ?>

   If this works and you see the text "PHP Version" at the top followed by other PHP settings info then continue to the other options below, if not then something is wrong with the web-server setup and you will need to contact your host or server administrator.
2. Server Logs: Examine the server error log as explained here. Also you may access all server error logs by going to cPanel > Statistics > Error Logs or using your host-specific control panel. If you don't have direct access to the server logs ask your host support to look for any errors in the logs for you.
3. Permissions: Check the permissions on installer.php file and its parent directory. On most hosts it should be 755 and files should be 644. Be sure to double check with your hosting provider or server admin as to how they want permissions setup on their servers.
4. Change Browsers: Open another web browser and check for the white screen. If it works in the new browser then it may be a browser cache issue. You can usually fix this by holding down ctrl+F5 or manually deleting your browser cache.
5. Config Files: Backup and remove hidden configuration files such as .htaccess, web.config and .user.ini files (Apache, Microsoft IIS, WordFence). These files under certain circumstances have have configurations that prevent the installer from running. Simply remove them from the same directory that the installer.php file is in and try to again. If the problem persist try and backup and remove the files from your root web directory, in most cases public_html.
6. Installer.php Some hosts and security software will automatically block requests to files named "installer.php". In this case try to rename the file to something else. Using the 'installer.php' file name on a public server is not recommended and users should consider using the hashed installer by going to Duplicator ❯ Settings ❯ Packages Tab ❯ Installer settings ❯ Set to [name]_[hash]_[date]_installer.php
7. Reverse Proxy: When running behind a reverse proxy, the value of the original hostname called is in HTTP_X_FORWARDED_HOST. To get around this setup add the following to the top of the installer.php and dup-installer\main-installer.php as such:

   $_SERVER['HTTP_X_ORIGINAL_HOST'] = $_SERVER['HTTP_X_FORWARDED_HOST'];

Also See:
How to handle "Internal Server 500" messages?

• Close your browser and browse to the installer.php again.
• Clear your browser's cache and cookies restart the browser and try to browse to the installer again.
• Try a different browser
• An attempt was made to access the main-installer.php file directly without using the installer.php file. Be sure to always start the install wizard by first going to the installer.php file in your browser.

• Duplicator Pro ❯ Packages ❯ Expand Package Overview ❯ Click "View Details" button ❯ Expand General Section ❯ Copy Full Name of "Archive" link
• Duplicator Lite ❯ Packages ❯ Package Details Button ❯ Expand General Section ❯ Copy Full Name of "Archive" link

1. Open Safari Browser
2. Go to: Preferences > General > Open Safe files after downloading -- leave this box unchecked.
3. Attempt to download the plugin again - it should come down as a single file.

1. Extract the archive file onto your local computer and navigate to the installer-backup.php file.
2. Select all the files/folders and re-create the archive.zip so that installer-backup.php is at the root of the archive.
3. In some cases you may need to rename the archive created in step 2 to the same one extracted in step 1
4. Place the newly re-organized archive file in the same location as the installer.php file and try again.

Plain Text:

Binary Text:

• Direct FTP Download:
  
  1. When transferring the package files from your FTP client be sure it is in binary mode since ASCII mode can/will corrupt the zip file.
  2. In Duplicator Pro FTP to '/public_html/wp-content/backups-dup-pro'.
     In Duplicator Lite FTP to:
     
     • Legacy Path: '/public_html/wp-snapshots/' folder (from your WP root)
     • Content Path: '/public_html/wp-content/backups-dup-lite/'
  3. Find the installer file name associated with the correct package and download it.
  4. Open in an text editor such as Notepad++. The file at this point should be a normal PHP file.
• Use backup installer: Another option is to open the archive.zip file and find the installer-backup.php file it will be an exact copy of the original installer.php file.
• Contact Host: Let your host know that the download of files needs to be set in binary mode not ASCII.

Download Prompts:

1. Non-Technical Route: If your not technical or just don't have time to mess around with server setups contact your host and tell them your site is not properly processing PHP files. They should be able to get you going quickly.
2. Technical Route: Try to explicitly set PHP5 in your .htaccess file: AddHandler x-httpd-php5 .php or with CGI
   AddHandler x-httpd-php5-cgi .php Consider these handlers for your version of PHP.

Parse Errors:

1. In many cases the transfer of the file from one server to another can cause the installer to get corrupted. To solve this issue see the section above titled "BINARY TEXT". In many cases changing the FTP mode from ASCII to binary can fix this issue.
2. If the first option does not solve the issue then open a program like Notepad++ and play around with the "Encoding" setting found in the top toolbar. Change from ANSI to UTF-8 try to convert from one format to the other and then save the file and then re-upload the installer file to the server to see which version works.

Also see:
Why can't I download files / get a corrupted installer / see a 404.3 message?

• What can I try for 502/503/504 Gateway issues during the build?

• How to Fix 504 Gateway Timeout Error in WordPress

1. Log in to Cloudflare
2. From Overview Page click "Advanced" ❯ Click "Pause"
3. Run installer deployment
4. Turn Cloudflare back on

• FTP Downloads
  If you transferred via FTP make sure that the FTP client is in binary mode when transferring down to your local box and then also when it's transferring back up to your host or destination server. If you downloaded straight from the plugin interface then try the download one more time to make sure that the http transfer is clean.
• Web Server Downloads
  Check Web Server Configuration
  These problems usually indicate the web server it not allowing files to be written to the directory. A common solution is to edit the Apache virtual hosts file and include the "AllowOverride All" instruction.
  Example:
  <VirtualHost *:80>
{various instructions}...
<Directory /var/www/html>
AllowOverride All
</Directory>
</VirtualHost>

  

1. Go to cPanel/Host Panel
2. Click on the Imunify360 app
3. Select Proactive Defense
4. Switch Mode Settings to Disabled or Log Only.

• While you install, temporarily disable WordFence. Additionally you may also need to temporarily comment out the line that begins with 'auto_prepend_file' in .htaccess and .user.ini files in the parent site's directory.
• Alternatively go to your web sites control cPanel ❯ file manage ❯ public_html ❯ show hidden files. Edit the user.ini file and make sure the path shows the correct path, if it shows the path from the original account path. Once that is changed the site should work.

1. Perform a manual extraction. https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-015
2. Once extracted the zip make sure that the htaccess file exists with the following setting ---
# Use PHP7 Single php.ini as default
AddHandler application / x-httpd-php70s .php
---
3. Start the installation program and in step 1 Select ❯ Extraction: Manual Archive Extraction ❯ Config Files: Ignore all In this way, the htaccess should not be touched.
4. At the end of the installation, check the wp-config.php and .htaccess configuration files and manually edit what is needed.

• Be sure the database and database user have been created
• Be sure the password matches the database user being used
• Be sure the database user is assigned to the database with the correct permissions
• Temporarly change the database user password to 'test123' to validate character input
• Contact your hosting provider for the exact required parameters

• The quickest way to validate full level of permissions is to contact your hosting provider.
• This codex covers creating a Database and User.
• For a cPanel demo follow along in this Step-By-Step Video.

1. Build in PHP Mode: To avoid any directives that mysqldump generates you can change the build mode to PHP which uses the minimal amount of mysql/mariadb directives. Simply goto Settings ❯ Packages Tab ❯ SQL Script ❯ "PHP Code". Then rebuild the package and re-install.
2. Modify SQL Script: Advanced In a web browser browse to the installer.php. Then check the file system (via FTP, cPanel, Explorer etc.) a directory named "dup-installer" should be present. Open the database.sql file found inside the dup-installer directory and modify this file so that the directives support the new mysql/mariadb server your on. To do this typically you can remove settings that look like the code block below. Typically its best to only remove the line where you are seeing the errors. ...
/*!40111 SET @[email protected]@SQL_NOTES, SQL_NOTES=0 */;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
So in the event the installer reported an error such as: 'Variable 'character_set_client' can't be set to the value of 'NULL'' - [sql=/*!40101 SET character_set_client = @saved_cs_client */;...] Then you might simply try to remove the last line, save the dup-database_[hash].sql file and run the installer again. If the issue persists check the errors till the version of msyql/marida is satisfied with the directives set. If the database engine versions are too far apart then it would be recommend to work with your host or server admin to bring the version closer together.

1. Rebrowse to the installer Step 1 ❯ Advance
2. Check Options ❯ Database Tab ❯ Processing ❯ "Chunking Mode".
3. Continue with the install.
4. If Option 1 does not work or the SQL chunking option is not available then try option 2.

• Quick Steps
• Advanced Steps

• Try running the installer at different times of the day if your on a host that is currently being heavily utilized.
• Change Build Mode: WordPress Admin ❯ Duplicator ❯ Settings ❯ Packages ❯ SQL Script. Some hosts work better with a PHP built SQL Script and others mysqldump.
• Contact your host to see if you can increase their PHP/Web Server timeout limits
• Consider upgrading to Duplicator Pro and trying the SQL file chunk option

<?php
// Update the 4 parameters to match your server requirements

// Create connection
$conn = new mysqli($servername, $username, $password, $dbname);

// Check connection
if ($conn->connect_error) {
    die("Connection failed: " . $conn->connect_error);
}
echo "Success: A proper connection to MySQL was made! The my_db database is ready to use ." . PHP_EOL;
echo "Host information: " . mysqli_get_host_info($conn) . PHP_EOL;
?>

• OPTION A
• OPTION B
• OPTION C

1. Run a database repair on your current WordPress site.
2. On Installer Step 2 ❯ Tables Tab ❯ Uncheck the Import flag for the table generating the issue
3. Alternatively When creating a package on Step 1 exclude the table in question from being added

• MySQL Create Table
• MariaDB Create Table

Unknown Collation Overview:

**ERROR** database error write 'Unknown collation: 'utf8mb4_unicode_ci'

MYSQL VERSION: This Server: 5.4.22 -- Build Server: 5.7.10

Update Database Software

• utf8mb4_unicode_ci: Mysql server 5.5.3+ is required.
• utf8mb4_unicode_520_ci: Mysql server 5.6+ is required.

Enable Legacy Check

Run Compatibility Mode

Manual Configurations

1. Extract the archive zip file manually
2. Open the database.sql file with notepad and Search & Replace on the collations for example you might :
   • replace: 'utf8mb4' with 'utf8'
   • replace: 'utf8_unicode_520_ci' with 'utf8_general_ci'
   • Always try these options in a sandbox first and never on a production site until your content with the results
3. Then browse to the installer.php file on the server and choose Advanced & check 'Manual Extract'
4. This can also be attempted with other collations i.e. replace 'collation_type_1' with 'collation_type_2'

• phpmyadmin
• SQL statements
• MySQL Workbench

Also see:
Recommended hosting providers for Duplicator?
http://dev.mysql.com/downloads/mysql
https://make.wordpress.org/core/2015/04/02/the-utf8mb4-upgrade

Also See:
WPBegginer: How to Fix the 403 Forbidden Error in WordPress.
How to fix a blank/white installer or 403/404/405/500 issues?

• Mis-configured config file such as: wp-config.php, .htaccess or themes/functions.php
• A redirect plugin that maybe installed. Disabling the plugin at install time see Option 3 below.
• Inside an html file via a meta refresh tag or a JavaScript redirect
• Check your cpanels for redirects or contact your host
• Follow these steps for fixing perma links
• Check the installer-log.txt file for warnings or errors.
• Try to remove your .htaccess file and start with a fresh one

1. Add the following to the httpd.conf
   # The Directory path below should match your server the following is a SAMPLE
<Directory /var/www/html/example.com/public_html>
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>
2. Restart Apache
3. If you're on a budget host with no access to the httpd.conf file you will need to send this FAQ item to your host

Also See:
How can I fix my site when the home page shows but no sub-pages work?
Why are some of my plugins/images/links/styles not updating?
WordPress.org Forums: 404 Errors on all pages but home page?

• Try to login a few times and try having the password emailed to you
• Pay attention to the "User Mode" used on Step 1 ❯ Options ❯ General.
• See Installer (Advanced mode) ❯ Step 3 ❯ Options ❯ disable all plugins in-case you have a plugin conflict
• You may have to reset the password by following these instructions
• If all other options fail you can use the emergency password reset script

• https://yoursiteurl.com/wp-admin
• https://yoursiteurl.com/wp-login.php

1. Switch to "Advanced Mode" in the upper right corner of the installer on step 1
2. Under "Options" ❯ "General" for the option "Users Mode:" select the "Merge" option
3. Choosing this option will result in details listed below for Merge

User Mode Overview:

• A defined constant is initialized with a flow check
• A dynamic variables concatenated to your plan value
• Backslashes or other custom settings

1. Using FTP or your host's File Manager copy wp-content/plugins/duplicator-pro/tools/file-renamer.php to the destination web site's root directory.
2. Browse to the tool (I.e. http://mydomain.com/file-renamer.php)
3. Use tool to rename the files.

1. Duplicator Lite Installer ❯ Step 1 ❯ Options ❯ Advanced Tab ❯ Config Files.
2. Duplicator Pro Installer ❯ Step 1 ❯ Advanced ❯ Options ❯ Advanced Tab ❯ Configuration Files

Also See:
How does Duplicator handle data/file migration?

•   How to do a "Manual Extraction" or run installer without zip enabled?

1. WordPress Error Log: Occasionally there are incompatibilities with the new web server and the site itself (PHP version changes for instance). To track down the problem capture an WordPress error log while you refresh the page causing the error. See this article for how to capture the WordPress error log.
2. cPanel Error Log: If your host is running cPanel, click on the "Errors" icon to review the latest errors experienced on the server.
3. Web Server Logs: These include the PHP error log and your web server error log such as Apache or Nginx. To find these files consult your hosts documentation. To find the latest errors match the correct time stamp in the error log with the time for which you were attempting to use the Duplicator. Sometimes error log messages can be vague and a quick Google search for the actual error message many times will lead to a quick resolution, especially if you include your hosting providers name.

1. During Package Build:
   • Disable Plugins: In some cases certain plugins (especially security and caching) will prevent certain actions from happening. If you have a security or caching plugin installed its recommended to temporarily disable it to make sure its not conflicting with anything.
   • Create Filter: Sometimes creating a root directory filter will allow the package to skip any files or directories that are problematic to how PHP is able to process and read them. This test step can help you isolate which directory (if any) might be triggering a 500 error.
   • open_basedir: The php.ini setting can cause all kinds of issues if not properly configured. See question: What is PHP Open Base Dir or "open_basedir restriction in effect"?
2. During Install:
   
   • Disable Plugins: If the 500 error is present on the installer side then its recommend to create your package with all cache and security plugins disabled and add all cache paths to the directory filters list.
     Note: The directories filter has a quick add link for cached WordPress data.
   • If you receive a 500 error during the installation process see the FAQ item below:
     How to resolve 403/500/timeout issues on step 3?
3. Post-Install:
   
   If you experience a 500 error or blank screen when loading a site after installation, please review one of the logs mentioned in the "ERROR LOGS" section above.

Also See:
How to resolve 403/500/timeout issues on step 3?
How to Fix the 500 Internal Server Error on Your WordPress Website
Recommended hosting providers for Duplicator?

Increase Memory

Package Builds

• Duplicator: Settings ❯ Packages ❯ SQL Script ❯ Mysqldump
• Duplicator Pro:
  • Settings ❯ Packages-Basic ❯ SQL Script ❯ Mysqldump
  • Settings ❯ Packages-Basic ❯ Archive Engine ❯ Enable "DupArchive" or "ShellZip"
    These engine options consume much less memory than ZipArchive
  • Settings ❯ Packages-Basic ❯ Server Throttle ❯
    This prevent resource complaints on budget hosts. The higher the value the slower the backup

Running Installer

1. Have your host or server administrator run the database.sql file for you. In some cases you may be able to use phpmyAdmin if the memory options to run it are different than how your web server is setup.
2. After the database has been installed go to step 1 of the installer and choose 'Manual SQL Execution' from the Action drop-down.
3. Continue to finish out the installer as you normally would.

Also see:
What can I try for timeout issues?
What can I do for issues with migrating a large site?
Recommended hosting providers for Duplicator?

• Remove unused files and folders
• Cleanup older backup files from plugins or system processes
• Cleanup your databases with phpmyadmin
• Cleanup your databases with a plugin

1. Go to: Duplicator Pro ❯ Settings ❯ Packages
2. Check "Client-side Kickoff"
3. Set Server throttling to "low" or "medium"

• Create file filters to keep your overall package size smaller
• For scheduled backups consider only backing up the database daily and the full site on a weekly basis.

Also see:
What can I do for issues with migrating a large site?
Recommended hosting providers for Duplicator?

wpconfig.php:

Installer

1. On step 2 of installer under options
2. Set charset: utf8mb4
3. Set collation: utf8mb4_unicode_ci

General Issues

DATABASE ISSUES

• Check wp-config.php
  Look for the DB_CHARSET and DB_COLLATE constants, these values can affect how WordPress handles your character encoding. If DB_COLLATE and DB_CHARSET do not exist in your wp-config.php file, try adding/editing either definition to your wp-config.php file. Please be sure to read the following article to better understand Converting Database Character Sets.
• Advanced Options
  In step one of the installer under advanced options there are two character values that you can try to enable which are "MySQL Charset" and "MySQL Collation" indirectly these values work with mysqli_set_charset. These values may not work on all systems.
• Database.sql File
  Open the database.sql file in Notepad++ and selected "Encode in UTF-8" from the Encoding menu, without changing the contents at all. In some situations this can be more important than changing the DEFAULT CHARACTERSET, as it determines how the file is read by the operating system.

FILE SYSTEM

• Filter Files
  A common work-a-round at this point is to filter the international files and then manually move them later. The scanner process will help you to spot these files.
• Shell Zip
  In Duplicator Pro there is a new process option called shell_exec which is supported by most hosts. This process can on most systems better handle international characters in file names. Please use this option in Pro if you're running into file/directory names with unicode characters.
• PHP 7+
  PHP 7+ has been improved to better handle unicode issues. If you can migrate or get your host to upgrade to the improved/faster performing version of PHP 7 this can solve the issue for internal characters issues at many levels.

1. For example if you receive a threat from a virus scan be sure to check the virustotal site. Check the total virus scan counts. If the count is say 50 virus scanners on all files and Duplicator passed 49 of them with nothing detected and only 1 or 2 of them showing a "possible" threat, then the chances are very low there is a possible corruption or hack of the plugin on your site. Note: You can update the full plugin zip file or just the file in question to the virus-total portal.
   
   
2. Virus signatures can be tricky and it is not uncommon for certain byte or code patterns to set them off. The virus-total site is also aware of false positives and addresses these types of issues on their website.
   
   
3. If the file does indeed show a threat across more than 2+ zones feel free to contact us with the file in question and we can do a compare against the base to determine if the file(s) have been compromised on your system. Our recommendation in all cases will be to remove the plugin and install a fresh clean copy. If the problem persists then there is a wider hole in your site and you will probably need a security analysis done on your site by a company that deals with these issues, like WordFence and the like.

... My name is Jelmer Verkleij, CTO at Patchman. This issue was brought to our attention about 30 minutes ago and after some quick research we noted that these detections are the result of an error in our definition development process. All detections of the installer/build/assets/inc.libs.js.php file in the duplicator plugin folder seem to be false positives at this point. My sincere apologies for the confusion - this should of course not have happened and naturally we have immediately started looking into how and why this went wrong, and what needs to be done to prevent this from happening again in the future.

In the meantime, we have deployed a definition update to all our Patchman customers that rolls back any automated quarantine actions that took place for these files, and retracts the associated detections. This should automatically restore all websites to their original state without problems.

Once again, I sincerely apologize for this inconvenience, and I would like to reiterate that we are taking this matter very seriously. If you have any further questions or comments you have regarding this incident, please don't hesitate to let me know here or by sending an e-mail to [email protected] I will make sure to address each response as soon as possible.

Best regards,

Jelmer Verkleij
Patchman B.V.

1. Disable High sensitivity scanning and return to recommended settings.
2. If you don't want to disable High sensitivity scans, you can click ignore on the individual results and they won't be bothered by them again (until one of the file hashes changes at least)
3. Under their scanner's Advanced settings, they can exclude any specific filepath or a wildcard path from being scanned (See https://www.wordfence.com/help/scan/options/#exclude-files for some detail).

SETUP OVERVIEW

1. Server Upgrade: Budget host may run into constraints with larger complex sites. Upgrading to a managed VPS/dedicated server can help in most scenarios. These systems allow for better control and come with excellent support from the hosting company.
2. Duplicator Pro: The Pro Version uses a multi-threaded architecture to better handle larger data sets. It also comes with dozens of other great features that help to enhance your full WordPress backup/migration strategies.
3. Adjust Settings: Directly below are several strategy options for your current host and with-in the plugin.

1. Try Again: Try more than once with the 'Try Again' button. The first pass on a build request is very slow as it has to cache the IO scan. The second pass is much faster as on some servers the IO seek is cached.
2. Archive Flush: On some web servers if the server doesn't flush a response after a specific amount of time then the process will be killed even if the timeout was increased. In the Settings menu check the 'Archive Flush' option. This will try and keep your connection open via a flush response.

1. Toggle SQL Mode: Consider trying a different database build process. First try "Mysqldump" then try "PHP Code". See Settings ❯ Packages Tab ❯ SQL Mode.
2. Enable Filters: Many times you can get a package to finish building simply by creating multiple directory filterS on a large data source such as your wp-content/uploads folder which contains larger files such as images/movies/pdf etc. For details see the section below titled "MANUAL TIMEOUTS WORKAROUNDS".
3. Enable DupArchive: A new format known as DupArchive has been Developed by Snap Creek to overcome problems experienced on large sites and restricted host environments. Using DupArchive greatly diminishes the changes you will experience a timeout on package builds. When using DupArchive on Duplicator Lite there is a 500MB limit for the size of you package.
   
   To use new format set: Duplicator Lite > Settings > Packages > Archive Engine = DupArchive Duplicator Pro > Settings > Packages > Basic Settings > Archive Engine = DupArchive

SERVER WORKAROUNDS

# Example .htaccess file Inserted By Customer Control Panel
SetENV PHPRC /home/username/public_html
# BEGIN WordPress
<IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteRule ^$ - [E=noabort:1]
   ...
</IfModule>
# END WordPress

<IfModule mod_fcgid.c>
   AddHandler fcgid-script .fcgi
   FcgidIOTimeout 900
   ProcessLifeTime 7200
   IPCConnectTimeout 180
   IPCCommTimeout 7200
</IfModule>

<IfModule litespeed>
   RewriteRule .* - [E=noabort:1]
</IfModule>

OR

<IfModule Litespeed> RewriteEngine On
   RewriteRule .* - [E=noconntimeout:1]
   SetEnv noabort 1
</IfModule>

• Try to exclude large files such as movies, large images or other backup files (like .zips or .tar files) from the file filters section
• Exclude your wp-content/uploads folder by adding it to the directory filters option. Then after the install is complete at the new location you can manually copy/FTP those files back over.
• Perform a Two-Part Install

• If possible try to rebuild a smaller package by excluding larger files/directories that can be moved over manually see "Package Timeouts" above.
• On Step 1 under options try the "Manual Extraction" step. For a step by step of how to perform a Manual extraction see these steps:
  Also see How to do a 'Manual Extraction' or run installer without Zip enabled?.

• If your database is too large for your servers configuration see the steps/options above for "Database Timeouts".
• Pro Users Only enable Options > Chunking > multi-threaded requests to chunk SQL file.
• Pro Only Users enable Setup > Action > Manual SQL Execution (advanced) option. This requires that you have manually imported the database ahead of time. This can be done by your host or a tool like phpMyAdmin if it supports larger sites.

If your moving from https to http or vice versa and run into issues below is a check-list of possible work-a-rounds:

1. Check Plugins: If you have an SSL plugin installed that controls SSL links on your site, try to deactivate/reactivate or temporarily remove the plugin to see if the issue persists. Plugins can be deactivated on step 3 of the installer under the options section.
2. WP-Config: Check the wp-config.php file for the FORCE_SSL_ADMIN constant and try to toggle it true/false.
3. Codex: Check the codex on Administration Over SSL to see if your site complies with the recommendations.

• In cPanel Check the "All PRIVILEGES" checkbox for the database user that is having access issues. Here are some examples:
  • How to Grant all Privileges to a User in MySQL with cPanel
  • How To Create or Delete a MySQL Database or User
• For various command line options see GRANT General Overview

1. Open the sites wp-config.php file with a text editor.
2. Add the following to the file
   define('FS_METHOD','direct');

Also See:
How can I configure PHP open_basedir?
How can I relax PHP's open_basedir restriction?

• Installer password: The archive is NOT encrypted. When the installer starts, it will prompt for a password to prevent anyone from running the installer.
• Archive encryption:^Pro The archive IS encrypted with a password, and the installer will ask for a password when started. This option is the recommended maximum level of security.

• When creating a package, users have the option to set a password on the installer. This password can be easily recovered by just going to Duplicator ❯ Packages ❯ click the package details button ❯ Installer Section and look for 'Password Protection' label.
• In the event you no longer have the package details and you forgot your password below are the manual steps to override the installer password.
  1. Browse to installer file via a web browser. The password screen will show.
  2. On remote server ❯ Open FTP connection to location of installer file, for localhost open a file browser.
  3. Navigate to the following file: \dup-installer\classes\class.password.php
  4. Edit the function CheckPassword and Replace: return $hash === $stored_hash;
With: return true;
Need a little help? Check out our Partners at Codeable
  5. On the installer password screen enter anything in the password field (e.g. 'test') and click submit.
  6. This should place you at step 1 of the installer ❯ Continue with installation

• How does Duplicator handle Multisite support?
• Duplicator Pro Multisite User Guide

define( 'DOMAIN_CURRENT_SITE', 'www.example.com' );

1. Filter the user table and use_meta when creating the package
2. Export users and usermeta with a specific query
3. Import users and usermeta tables into new database manually
4. Run the installation and select as database action "Connect and Do Nothing (Advanced)".

Settings ❯ Storage ❯ Storage Types ❯ Google Drive and set "Upload Size" to 1000kb.

If you need to authorize multiple programs, machines, or devices, one workaround is to limit the number of clients that you authorize per user account to 15 or 20. If you are a G Suite admin, you can create additional admin users and use them to authorize some of the clients.

Settings ❯ Storage ❯ Storage Types ❯ OneDrive and set "Upload Size" to 1000kb.

Duplicator Pro

GoDaddy may be the most resource-constrained of all the major web hosts. Because of this, if your site is over 150MB you may have to switch from the zip format to the DupArchive format which was developed to work on restricted hosts.

To build a package using DupArchive:

1. Go to Duplicator ❯ Settings ❯ Packages
2. Set Archive Engine to DupArchive.
3. Set the "Max Build Time to 270 if your site is over 1GB.
4. Attempt to build.
5. If still encounter an error set the following values in Settings > Packages and rebuild:
• Server Throttle: Medium
• Client-side Kickoff: Enabled
6. If you still have problems:
• Increase your GoDaddy plan's resource level to level 3. By default, All GoDaddy shared plans start at level 1 or 2, even Ultimate. Resource levels are described on GoDaddy's resource page.

When installing to GoDaddy you may experience a timeout. To avoid a timeout perform a manual extraction install as described in the answer to FAQ question How do I do a Manual Extraction?

Duplicator Lite

1. Creates a temp folder in the root path or location where you want to install for example dup_temp
2. Upload the installer and archive files into the dup_temp folder and browse to the installer http://mydomain/dup_temp/installer.php.
   Note: This starts a classic installation so the pre-set values will not enabled like they are for an import install. By default the installer considers the current folder as root path but this can be changed in the advanced installation
3. On step 1 choose "Advanced Mode" and remove dup_temp path from the 'New Site URL' & 'New Path' inputs
4. Click validate without filling in the other fields< Now the validation fails because you didn't enter the database connection data but the GoDaddy wp-config is detected so you are prompted with the correct db connection data that you need to apply.
5. Next set all the 'Configuration Files' to 'Do nothing'
   Now you can continue with the installation and it should work. We are working to streamline this process.

1. On the Packages screen, click the Create New button
2. Click "Enable File Filters" ❯ Above the Directories box ❯ click the root path quick link.
3. Append '/www' to that path. For instance if the root path is /home/myhome/public_html the path should be /home/myhome/public_html/www
4. Perform the same 'root' quick path procedure shown above but this time append the name of your domain (for instance if your domain is mydomain.com append /mydomain so it would be /home/mydomain

1. Go to Duplicator ❯ Settings ❯ Packages.
2. Set "Archive Engine" to "DupArchive"
3. Go to Duplicator ❯ Settings ❯ Packages ❯ Advanced.
4. Set "Lock Type" to "SQL".
5. Set "Installer Name" to "installer.ph1". The default setting of "Installer.php" doesn't work because WPEngine prevents creation of PHP files.
   When you install, be sure to rename the Installer.ph1 file to Installer.php before browsing to the installer.

Online Article Tutorials

1. How to Clone a WordPress Website by: SASA STOJANO
2. How to Move One Web Host to Another in 2019 (No Downtime!) by: isitwp.com
3. How To Move WordPress Site in 7 easy steps by: WPDean.com
4. How to Move/Backup Your Website with the WordPress Duplicator Plugin by:Rachel Adnyana
5. How to Move a Live WordPress Site to Local Server by: wpbeginner.com
6. 3 Plugins For Easily Migrating A WordPress Site, Tried & Tested by: James Bruce
7. How To Move WordPress From Localhost To Live Host Server by: WPDean.com
8. A series of videos and overviews for how to Duplicate a WordPress Site by: Paal Joachim

Duplicator Walk-through Series

1. How To Use Duplicator WordPress Migration Plugin
   Version 1.2.36 | Time: 29:27 | By: Pixemweb
2. Complete Migration Overview
   Version 1.2.32 | Time: 9:27 | By: Paal Joachim
3. Transfer/Migrate a WordPress Site in 10 minutes
   Version 1.1.20 | Time: 10:00 | By: Jakson
4. How to Backup and Clone a WordPress Website - 2017 (Siteground)
   Version 1.1.32 | Time: 14:00 | Web Monkey
5. Complete End to End Overview
   Version 1.1.8 | Time: 1:01:00 | By: Timothy Meyers

Duplicator Walk-through Series (Non-English)

1. WordPress Website auf einen anderen Server umziehen mit dem Plugin Duplicator
   Version 1.3.40 | Time: 14:51 | By: nexTab.de | Language: German

Package Process

Install Process

1. Extract all files: Extract all files from the package archive. This option is selected by default.
2. Skip extraction of WP core files: Extract all files except WordPress core files. Choose this option to extract only the wp-content folder and other non-core files and directories.
3. Extract only media files and new plugins and themes: Extract all media files, new plugins, and new themes. The installer will not extract plugins and themes that already exist on the destination site.

Prerequisites

• You have two sites i.e. a Development and Staging site
• The sites files are identical except for their physical location.
• The sites databases are the same except for locations which could be the same or different servers.

Work-Flow

1. Create a new package on the Development site and exclude/filter the \wp-content\uploads\ directory.
   This can also be other locations that might have large files.
2. Download the package files locally then transfer them to your Staging site in the WordPress root
3. Browse to the installer.php file on the staging site and exact the archive.
4. Upon completion that Staging site should have all the updates of the Development site minus the filters from step 1.
5. Since the sites were identical initially the \wp-content\uploads\ should still be functional on the Stage site.

1. Install Duplicator Pro on both sites
2. On the main site set the engine to DupArchive (Settings > Packages > Archive Engine = DupArchive)
3. Build a package on your main site
4. Perform an import URL install as described here Import Link tab

1. In a new browser tab, go to phpAdmin or the equivalent on your destination machine.
2. Remove existing database tables from your the destination database.
3. Import your own custom script (this should represent a copy of your site in most cases). This can be done via the phpMyAdmin import procedure.
4. Launch the Duplicator Pro installer.php in a browser tab
5. Switch to Advance Mode ❯ Choose "Manual SQL Execution" from the database option.
   this will prevent the installer from using the .sql within the archive and skip past the data insertion step all-together.
6. Finish the install process

1. Login to your development site and goto Duplicator Pro ❯ Packages screen ❯ "Create New" button
2. Archive ❯ Database Tab ❯ Check "Enable Database Table Filters" ❯ check "wp_posts" table & build package
   Note: This will exclude/ignore the "wp_posts" table from being created in the database.sql script
3. On staging site open the installer.php and location the "Setup" area on Step 1.
4. Choose Action "Overwrite existing tables" ❯ Click the "Validate" button
   Note: This will keep all the existing tables in the database and overwrite those with the same name.
5. Validate the "wp_posts" table is NOT in the removal list
   See: Validate tables Validate ❯ Database ❯ "Tables Flagged for Removal or Backup"
6. Continue with the install process & upon completion the "wp_posts" table should remain unchanged