Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

How to Fix Duplicator Installer Errors

Short answer

To fix Duplicator installer errors, first check that installer.php and the archive came from the same package and that both files fully uploaded. Then confirm the destination runs PHP 7.4 or newer and a database version equal to or newer than the source. Finally, open installer-log.txt, find the exact error in the DATABASE RESULTS section, and apply the fix for that error.

Key takeaways

  • Each installer.php works only with the archive from the same Duplicator package.
  • Duplicator needs PHP 7.4 or newer, WordPress 6.2 or newer, and a 64-bit PHP build as of November 2026.
  • Database errors are listed in installer-log.txt under DATABASE RESULTS, marked ERROR.
  • Set max_allowed_packet to 64M when a query is too large for the database server.
  • Delete installer.php and the archive from the server after the restored site passes its checks.

What is the Duplicator installer and what does it do?

The Duplicator installer is a small PHP script that rebuilds your site from a Duplicator archive on a new server.

A Duplicator package has two parts. The archive holds your files and a copy of your database, while installer.php reads that archive and rebuilds the site. Duplicator's archive guide states that each installer only works with the archive it was generated for.

The installer does not need WordPress to run. It can restore a site onto a blank server because it builds the database, writes the config file, and extracts the files itself. That independence is why it is used for moves to a new host and for recovery when the dashboard will not load.

What do you need before you run installer.php?

You need the matching installer and archive, an empty database, and a destination server that meets Duplicator's requirements.

Duplicator's system requirements state that Duplicator Lite and Pro need PHP 7.4 and above, WordPress 6.2 or higher, a 64-bit operating system, and a 64-bit build of PHP as of November 2026. A 32-bit build cannot handle files larger than 2GB, so backups on such servers fail once the archive passes that limit.

The same page lists MySQL 5.6 or newer and MariaDB 10.1 or newer as the minimum database.

MySQL 8.0 or newer and MariaDB 10.6 or newer are recommended. WordPress.org's Requirements page recommends PHP 8.3 or greater and MariaDB 10.11 or newer or MySQL 8.0 or newer as of November 2026, so aim above the Duplicator minimum when you can.

Gather these items before you start:

  • The installer.php file and the archive from the same package, with matching names and sizes
  • An empty database name, database user, and password from your host
  • The destination domain and the folder where the files will live
  • FTP, SFTP, or file manager access to upload both files

Plan for 30 to 60 minutes for a small site, and longer for a large archive. A backup guide helps you keep a separate copy off the server before you start.

Why does the installer say the archive does not match or is not found?

A mismatch error means installer.php and the archive came from different packages, or the archive did not fully download.

Duplicator checks that the two files belong together before it does anything else. If they do not match, or the archive is not fully intact, it stops rather than risking a partial restore. The usual cause is a pairing mix-up, such as an installer from one backup placed next to an archive from another.

Fix it in this order:

  1. Check the file names and sizes against the package on the source site.
  2. Download both files again from the same package.
  3. Upload both files to the same destination folder.
  4. Compare the uploaded archive size with the source size before you run the installer.
  5. Run installer.php again from the destination domain, for example yourdomain.com/installer.php.

Do not rename the archive to force a match. Renaming does not change which package it came from, and the installer still rejects it. If you lost the installer but still have the archive, Duplicator Pro lets you upload the archive on the Import Backups page instead.

How do you fix a 403, 500, or timeout error on step 3?

A 403, 500, or timeout on step 3 usually means the server stopped the installer, not that the archive is broken.

Duplicator's step 3 guide says these errors are not common, but they happen on hosts that are not set up to run the installer for long enough. A timeout means the web server did not allow enough time to extract the archive and install the database.

Work through these fixes in order:

  1. Ask your host to raise the PHP max_execution_time limit.
  2. For a large database, set the Database Dump Engine to Mysqldump instead of PHP Code, if your host supports it.
  3. For a large archive, set the Archive Engine to Shell Zip or DupArchive instead of ZipArchive, if your host supports it.
  4. Temporarily disable security and caching plugins, then run the installer again.
  5. Check the .htaccess file for a rule that blocks installer.php, and ask your host about any ModSecurity rule that fires.

Both engine settings sit under Duplicator Pro, then Settings, then Backup. If Wordfence runs on the destination or on another site in a parent folder, its firewall can block installer.php. Duplicator's guide advises disabling the Wordfence firewall until the site is deployed, then turning it back on.

For a 403 error, also check folder permissions. Duplicator's dependency guide lists 755 for directories and 644 for files. Do not set folders to 777 as a lasting fix, since that leaves them open to anyone who can reach the server.

How do you fix a database connection error or access denied?

A database connection error means the installer cannot reach the database with the details you entered.

The most common cause is wrong credentials. Duplicator's database error guide lists “Access denied for user” as an incorrect database credentials error, fixed by re-entering the correct details in step 2 of the installer.

Check each item in turn:

  • Database host, which is often localhost but can be a separate host name on some plans
  • Database name, spelled exactly as your host created it
  • Database user, which must be linked to that database with full rights
  • Database password, copied without extra spaces

Use the Test Connection button in the installer before you continue. It shows the MySQL version on both servers, which also helps with the collation errors in the next section. If the test still fails, create a fresh database user in your hosting panel and try those details.

The installer also needs the PHP mysqli extension. Duplicator's dependency guide says this extension is required to complete an install. If your host has it turned off, ask them to enable it.

How do you fix an unknown collation or invalid default value error?

An unknown collation error means the destination database is older than the database that created the backup.

Duplicator's compatibility guide states that an error such as “Unknown collation: utf8mb4_unicode_ci” is triggered because the MySQL version in use does not support that table format. The cleanest fix is to update the destination database to the same version as the source, or a newer one.

The guide gives these version facts:

CollationMySQL version needed
utf8mb4_unicode_ciMySQL 5.5.3 or newer
utf8mb4_unicode_520_ciMySQL 5.6 or newer
utf8mb4 tables in generalMySQL 5.5.3 or newer, released 8 April 2010

Ask your host to move your account to a database server that supports the collation. Most hosts move the account rather than upgrading the server in place.

If the versions are close, such as 5.7 on the source and 5.6 on the destination, the move may still work, but a wide gap is more likely to fail.

If installer-log.txt shows “Invalid default value”, set the MySQL mode to NO_ENGINE_SUBSTITUTION.

Duplicator's database error guide gives these steps: switch to Advanced Mode on step 1 of the installer, open the Database tab, find the Mode field, select Custom, and enter NO_ENGINE_SUBSTITUTION. Then continue the install and check the log again after it finishes.

How do you fix a packet too large or server has gone away error?

A packet too large error means one query is larger than the database server allows.

Duplicator's database error guide maps “MySQL server has gone away” and “packet too large” to a query that exceeds max_allowed_packet. The fix is to raise that limit in the MySQL config file, for example max_allowed_packet=64M in my.cnf or my.ini.

MySQL's packet guide states that the server default for max_allowed_packet is 64MB, the mysql client default is 16MB, and the largest possible packet is 1GB. Both the client and the server have their own limit, so a large query needs the server value raised.

Follow these steps:

  1. Open installer-log.txt and search for DATABASE RESULTS to find the failing query.
  2. Ask your host to set max_allowed_packet=64M in the server config, or higher for a very large site.
  3. Ask the host to restart the database server after the change.
  4. Run the installer again from a clean database.

If you cannot change the server config on shared hosting, ask the host to raise the limit for you or move the site to a plan that allows it. Do not keep retrying the same install without changing the limit, since the same large query will fail again.

How do you read installer-log.txt to find the real error?

Installer-log.txt is the record of what the installer did, and it names the exact error that stopped the install.

Duplicator's database error guide says queries that error during installation are recorded in the installer log. Open installer-log.txt and search for the DATABASE RESULTS section, where errors are marked ERROR. Duplicator Pro links directly to the log from any error notice shown during the install.

Use this table to match the error string to the fix:

Error stringLikely causeFirst fix
Unknown collationDestination database is too oldUpgrade the destination database
MySQL server has gone awayQuery exceeds max_allowed_packetRaise max_allowed_packet to 64M
Data too long for columnCharset mismatch between source and destinationCompare the source charset, usually utf8mb4, with the destination charset
Table already existsTables left from a past install attemptDrop all tables or enable Remove All Tables before you re-run
Duplicate entry for PRIMARY KEYPartial past importDrop all tables and re-run from a clean database
Access denied for userWrong database credentialsRe-enter the correct details in step 2
Invalid default valueMySQL mode rejects the valueSet the mode to NO_ENGINE_SUBSTITUTION

Some messages are only notices. Duplicator's compatibility guide says it is best to continue with the install and watch the log and the step 3 install report.

If the site is stable and the Deploy or Update error count is under 10, Duplicator's database error guide says you can typically ignore those minor errors or notices.

How do you check that the install worked and clean up safely?

The install worked when the site loads, the admin login works, and the installer report shows few or no errors.

Check the site in this order:

  1. Open the home page and 2 or 3 inner pages.
  2. Log in to the WordPress admin with the source site credentials.
  3. Open Settings, then General, and confirm both URL fields match the destination domain.
  4. Open Settings, then Permalinks, and click Save Changes to flush the rewrite rules.
  5. Re-save settings for any theme, plugin, or widget that showed an error in the report.
  6. Check the installer report on the final step for errors, warnings, and notices.

If a page shows a 404 after the move, saving permalinks is the first fix to try. A host change guide covers the redirect and DNS checks that follow a move.

Then delete the installer files. Duplicator's archive guide states that leaving installer.php live on a production server is a security risk, and it should be deleted as soon as the restore is confirmed.

Use the one-click cleanup the installer offers, then check that yourdomain.com/installer.php no longer loads. Keep your archive only in protected off-server storage, not in the public web folder.

What mistakes should you avoid?

Avoid the mistakes that turn a small error into a lost site.

  • Do not run the installer over a live site without a separate backup stored off the server.
  • Do not mix an installer from one package with an archive from another package.
  • Do not unzip the archive by hand; let the installer extract it.
  • Do not leave installer.php, the archive, or installer-log.txt on the server after the move.
  • Do not set folders to 777 and leave them that way.
  • Do not edit the database dump to change collations unless you have a copy you can restore.
  • Do not ignore a mismatch error and try a different archive at random.

If the destination runs PHP 7.4, note that PHP's supported versions page lists PHP 8.2 security support until 31 December 2026 and PHP 8.3 security support until 31 December 2027 as of November 2026.

PHP 7.4 has no support left, so plan an upgrade with your host after the move. A hosting choice guide can help if your current host cannot run a supported PHP version.

Frequently asked questions

Can I reuse installer.php from an older Duplicator backup?

No. Each installer.php is generated to match one specific archive from the same package. Pairing it with an archive from a different backup triggers a mismatch error and the installer stops. Download both files again from the same package, upload them to the same folder, and run the installer again.

Why does the installer stop on step 3 with a timeout?

Step 3 extracts the archive and installs the database, which takes time on a large site. If the server limit is too low, PHP stops the process partway through. Ask your host to raise max_execution_time, switch the archive engine to DupArchive or Shell Zip if supported, and try the install again from a clean database.

What should I do if the site works but the installer report shows errors?

First confirm the site loads, the admin login works, and the pages look right. If the Deploy or Update error count is under 10 and the site is stable, Duplicator says those minor errors or notices can typically be ignored. Re-save settings for any affected theme, plugin, or widget, and check installer-log.txt for the exact error before you change anything else.

Do I need to install WordPress before I run installer.php?

No. The installer does not need WordPress installed, active, or working on the destination. It builds the database, writes the config file, and extracts your site from the archive. You do need an empty database and a database user ready, plus the matching installer and archive in the destination folder.

Is it safe to leave installer.php on the server after a migration?

No. A working installer script left on a live server could be found and run again by someone else. Delete installer.php and the archive as soon as the restored site passes its checks, using the one-click cleanup the installer offers. Keep a copy of the archive only in protected storage away from the public web folder.

When should I ask my host for help with a Duplicator installer error?

Ask your host when the fix needs a server change you cannot make, such as raising max_allowed_packet, raising max_execution_time, enabling the mysqli extension, or moving your account to a newer MySQL or MariaDB server. Give them the exact error from installer-log.txt, plus the source and destination PHP and database versions, so they can act without guessing.

Sources

  1. Resolving the installer database errors and warnings on the install report Duplicator
  2. System Requirements for Duplicator Duplicator
  3. Resolving 403/500/timeout issues on step 3 Duplicator
  4. Handling Database Compatibility Issues Duplicator
  5. Duplicator's Archive vs Installer: Why Every Backup Comes in Two Pieces Duplicator
  6. Packet Too Large MySQL
  7. PHP: Supported Versions PHP

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test