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

Troubleshooting · Troubleshooting

How to Fix Duplicator Installer Errors

Short answer

To fix a Duplicator installer error, first read the exact message, then check that installer.php and its archive came from the same package and sit in the same folder. Next, confirm the destination meets Duplicator's requirements, fix the cause the message points to, and run the installer again. Most errors come from a mismatched pair, a missing PHP extension, wrong permissions, a firewall block, or wrong database details.

Key takeaways

  • Each installer.php works only with the archive from the same Duplicator package, so a mixed pair stops with a mismatch error.
  • Duplicator Lite and Pro need PHP 7.4 or newer, WordPress 6.2 or newer, and a 64-bit operating system and PHP build as of November 2026.
  • Directories should use 755 permissions and files 644, and the installer needs a writable folder to extract the archive.
  • A 403 error often points to a firewall, security plugin, or file permissions, while a 500 error often points to a PHP fatal error.
  • Remove installer.php and the archive from the server after you confirm the restored site works.
  • Ask your host when the error needs a PHP version, extension, or server limit that you cannot change yourself.

What is the Duplicator installer, and what does its error mean?

A Duplicator installer error means installer.php stopped before it could rebuild your site from its archive.

The archive holds your files and a copy of your database, while installer.php is the small PHP script that rebuilds the site from it. Duplicator's archive guide states that the archive is your site data and the installer is the script that restores or migrates it.

The installer does not need WordPress to run. Duplicator states that installer.php works on its own, so it can restore a site onto a blank server.

The exact message matters more than the general label. A mismatch message, a 403 message, a 500 message, and a database message each point to a different cause, so copy the full text before you change anything.

Why does installer.php not open or show a blank page?

A blank installer page usually means PHP stopped before Duplicator could show its first screen.

Start with the server error log, because a blank page hides the real message. WordPress developer docs explain that setting WP_DEBUG_LOG to true writes errors to wp-content/debug.log, which you can read after you load the page again. WordPress debugging docs

Check that installer.php is in the folder you expect and that you opened the right address, such as yourdomain.com/installer.php. A 404 means the file is not at that address, while a 403 or 500 points to permissions or a server fault.

A page that shows only a date and time has a narrower cause. Duplicator support threads link this symptom to Wordfence on the destination or a stale auto_prepend_file line in a parent .htaccess or .user.ini file. WordPress.org support thread

If a security plugin left files behind, remove its loader files from the destination root and parent folders. Check .htaccess and .user.ini for an old path, then load installer.php again.

Why do you see “Archive not found” or a mismatch error?

A mismatch error means the installer and the archive do not belong to the same package.

Duplicator states that each installer only works with the archive it was made for, and it checks the pair before it starts. Duplicator's archive guide also states that a partial download can trigger the same stop, because the archive is not complete.

Fix it with a fresh, matched pair. Download both files again from the same package on the source site, then upload them to the same destination folder without renaming the archive.

Compare file sizes before you run the installer. If the uploaded archive is smaller than the source file, the transfer was cut short, so upload it again, ideally without a proxy or CDN in the path.

Do not pair an installer from one backup with an archive from another. If you lost the installer, use the recovery method in the Duplicator knowledge base for that archive, or use Duplicator Pro Import Backups if WordPress still runs on the destination.

Why does extraction fail or stop partway?

Extraction fails when the server cannot unpack the archive, runs out of time, or runs out of space.

Duplicator needs ZipArchive or shell zip support to create and extract a ZIP archive. Its dependency guide states that the plugin requires the PHP ZipArchive extension or the shell_exec function with zip support, and you can switch to the DupArchive format in Duplicator, Settings, Backups, Archive Engine. Duplicator dependency guide

PHP's own manual describes ZipArchive as the class that reads and writes ZIP archives, so a server without that extension cannot use the ZIP path. PHP ZipArchive manual

SymptomLikely causeFirst fix
“Archive not found”Wrong folder or renamed archivePut the matched pair in one folder, keep the archive name unchanged
Extraction stops partwayTime limit or low memoryUse DupArchive or Shell Zip, then ask the host to raise the time limit
403 on Step 3Firewall, security plugin, or permissionsDisable the security plugin, check permissions, ask the host about firewall rules
500 on Step 3PHP fatal errorRead the server error log, check the PHP version and extensions
Database connection failsWrong host, name, user, or passwordCreate a fresh database and user, then re-enter the details

For large archives, change the engine before you rebuild the package. Duplicator's Step 3 guide states that large archives should use Shell Zip or DupArchive instead of ZipArchive, and large databases should use Mysqldump instead of PHP Code, when the host supports them. Duplicator Step 3 guide

If extraction still stops, try Manual Extract in the installer Advanced options. This lets you unpack the archive yourself first, then run the installer over the unpacked files.

Why do you see a 403 or 500 error during the install?

A 403 error means the server refused the request, while a 500 error means PHP failed while it ran.

Duplicator's Step 3 guide lists permissions, firewall rules, and the .htaccess file as the first 403 checks. It states that the root WordPress folder should use 755 permissions, and Step 1 Advanced options can set permissions on directories or files. Duplicator Step 3 guide

Security and caching plugins can block the installer. Duplicator advises disabling them during the install, and it notes that Wordfence can block installer.php across folders, so disable its firewall until the site is deployed. Duplicator Step 3 guide

For a 500 error, read the PHP error log first. A WordPress.org support thread on installer.php 500 errors links the fault to a damaged installer file, often from an FTP transfer in ASCII mode instead of binary mode. WordPress.org support thread

Re-upload installer.php in binary mode if the log shows a parse error near the top of the file. File transfer tools usually offer binary mode in their transfer settings, and cPanel File Manager avoids the FTP mode problem.

What server requirements must the destination meet?

The destination must meet Duplicator's PHP, WordPress, database, and 64-bit requirements.

Duplicator Lite and Pro need PHP 7.4 or newer as of November 2026, and Duplicator recommends PHP 8.1 or newer because PHP 7.4 has reached end of life. Duplicator system requirements

Duplicator needs WordPress 6.2 or newer, plus MySQL 5.6 or newer, or MariaDB 10.1 or newer, as a minimum. Duplicator system requirements lists MySQL 8.0 or newer and MariaDB 10.6 or newer as the recommended versions.

Duplicator also needs a 64-bit operating system and a 64-bit build of PHP. Duplicator system requirements states that 32-bit PHP cannot handle files larger than 2 GB, so backups fail to build or extract past that limit.

The installer also needs the mysqli extension for the database step. Duplicator's dependency guide states that completing an installation needs the mysqli extension, and you should ask the host to enable it. Duplicator dependency guide

Check permissions with the same guide. It states that directories should use 755 and files 644, and a failed writable-directory check means Duplicator cannot write to that folder.

Why does the database step fail?

The database step fails when the installer cannot connect, cannot create tables, or meets a version or collation it cannot use.

Create the database before you run the installer. Duplicator states that you usually need an empty database and a database user first, then you enter those details when the installer asks for them. Duplicator's archive guide

Use the exact host, database name, user, and password from your hosting panel. On many hosts the host is localhost, but some hosts use a separate database server name, so copy it from the panel instead of guessing.

If the database server is too old, the installer stops at the version check. Duplicator's dependency guide states that a failed MySQL minimum version check means the database server runs an older MySQL version than Duplicator supports, so ask the host to upgrade it.

Collation errors need a different fix. Duplicator's database compatibility guide states that unknown collation errors can be fixed by editing the extracted database.sql file to replace the collation, then running the installer with Manual Extract checked. Use a copy first, and change only the collation value the error names.

If Mysqldump is not available, switch the dump engine. Duplicator states that you can use the PHP Code option under Duplicator Pro, Settings, Backups, Database Dump Engine, when Mysqldump cannot run on the host.

How do you fix a Duplicator installer error step by step?

Work in order, from the files to the server to the database, and re-run the installer after each fix.

  1. Copy the exact error message and the time it appeared, then check the server error log for the matching line.
  2. Confirm installer.php and the archive came from the same package, sit in the same folder, and match the source file sizes.
  3. Check the destination PHP version, WordPress version, and extensions against the requirements in the section above.
  4. Set folders to 755 and files to 644, and confirm the destination folder is writable.
  5. Disable security and caching plugins, or disable the Wordfence firewall, then try the installer again.
  6. In the installer Advanced options, switch the extraction engine to DupArchive or Shell Zip if ZipArchive fails.
  7. Create a fresh empty database and user, then enter those details in the installer database step.
  8. If the build times out, raise the PHP max_execution_time limit and check Max Build Time under Duplicator Pro, Settings, Backup, Processing, which uses minutes and uses 0 for no limit.

For a full walkthrough of the normal install screens, see the guide on how to migrate WordPress with Duplicator. It covers the same installer steps when nothing is broken.

For large sites, read the Duplicator large site migration guide before you rebuild the package. It covers the DupArchive format and the size limits that cause timeouts.

How do you know the fix worked?

The fix worked when the installer reaches its final report with no errors and the site loads on the new address.

Open the installer report on Step 3 and read every warning. Duplicator's database compatibility guide states that some messages are only notices, so continue with the install and watch the installer log and the install report on Step 3.

Check the site by hand after the install. Open the home page, 2 or 3 inner pages, and the WordPress admin login, then confirm images load and links point to the new domain.

If links still point to the old domain, see the guide on how to fix broken links after migration. It covers the link checks to run after a move.

Delete the installer files only after these checks pass. Duplicator states that installer files must be removed after the install is complete, and the Snapcreek installer guide lists the same cleanup step. Snapcreek installer guide

When should you contact your host?

Contact your host when the fix needs a server setting you cannot change.

Ask the host to upgrade PHP, enable ZipArchive or mysqli, or move the account to 64-bit PHP. Duplicator states that the host can usually upgrade PHP from the control panel or by ticket, and it recommends asking the host first.

Ask the host for the exact error-log line and the ModSecurity rule ID when a 403 or 500 error has no clear cause. The log line names the file and line that failed, and the rule ID tells the host which rule to remove.

Ask about time and memory limits when extraction times out on a large archive. Only the host can raise max_execution_time or the PHP memory limit on many shared plans, so give them the archive size and the step where it stopped.

If you suspect a memory fault rather than a Duplicator fault, see the guide on how to fix Allowed Memory Size Exhausted. It covers the memory limit checks to run before you ask the host to raise it.

What mistakes should you avoid?

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

  • Do not run the installer in a folder that still holds a live site unless you plan to replace that site.
  • Do not rename the archive, because the installer checks the pair and a renamed file can fail the match.
  • Do not leave installer.php, the archive, or installer logs on the server after the move.
  • Do not set folders to 777 as a lasting fix, because Duplicator warns that 777 is a security issue and should only be used for a short test.
  • Do not ignore warnings in the install report, because a warning about the database or URLs can mean broken links later.

Keep a copy of the archive and installer on your own computer until the new site is checked. How to back up WordPress covers the backup habit that makes a failed migration easy to retry.

Frequently asked questions

Can I reuse installer.php from an older backup with a new archive?

No. Each installer.php is made for one archive, and Duplicator checks the pair before it starts. Pairing files from different packages triggers a mismatch error and stops the install. Download both files again from the same package, keep the archive name unchanged, and upload them to the same folder.

Why does installer.php show a blank page with no error?

A blank page usually means PHP stopped before the installer could show its screen, so the real error is in the server log. Check the PHP error log for the time you loaded the page, and look for a fatal error, a missing extension, or a blocked file. A page with only a date and time often points to Wordfence or a stale auto_prepend_file line.

What should I do if the archive extraction gets stuck at the same point?

Stop and check the installer log, disk space, and the archive size before you run it again. Switch the extraction engine to DupArchive or Shell Zip in the installer Advanced options, or use Manual Extract after unpacking the archive yourself. If the same file always fails, rebuild a smaller package and exclude cache and old backup files first.

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, so remove it as soon as the restored site is checked. Delete installer.php, the archive, and the installer logs and temporary folders from the destination root. Keep a copy of the archive on your own computer instead of on the server.

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

No. The installer does not need WordPress installed, and it builds the site from the archive on a blank server. You do need an empty database and a database user, which you create in your hosting control panel first. Enter those details when the installer asks for them during the database step.

When is a Duplicator installer error a hosting problem?

It is a hosting problem when the fix needs a PHP version, extension, time limit, memory limit, or firewall rule that only the host can change. Give the host the exact error message, the time it appeared, the archive size, and the installer step where it stopped. Ask for the error-log line and any ModSecurity rule ID so the cause is clear.

Sources

  1. System Requirements for Duplicator Duplicator
  2. How to resolve requirements and dependency checks? Duplicator
  3. Resolving 403/500/timeout issues on step 3 Duplicator
  4. Duplicator's Archive vs Installer: Why Every Backup Comes in Two Pieces Duplicator
  5. Debugging in WordPress WordPress Developer Resources
  6. ZipArchive manual PHP
  7. Duplicator Lite and Pro Installer Guide Snapcreek
  8. Handling Database Compatibility Issues Duplicator

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