Back to Community
Home / Community / Plugin → Duplicator

Troubleshooting 'Archive Not Found' and Related Errors in Duplicator

31 threads Sep 10, 2025 Plugin → Duplicator

Content

Stuck on an Archive Error? Here's How to Fix It

One of the most common hurdles users face when migrating a WordPress site with the Duplicator plugin is encountering an error related to the archive file. Messages like 'Archive not found', 'Archive parameter not specified', or 'Archive/Installer mismatch' can bring your migration to a screeching halt. This guide will explain why these errors occur and walk you through the most effective solutions to get your installation back on track.

Why Do These Archive Errors Happen?

Based on community reports and common scenarios, these errors are almost never a flaw in the Duplicator plugin itself. Instead, they are typically caused by one of the following issues:

  • Incomplete File Upload/Download: The archive.zip file may not have been fully transferred to the server or downloaded from the source site.
  • Filename Mismatch: The installer.php file is designed to look for one specific archive filename. If the archive is renamed or if the installer and archive are from different packages, they will not recognize each other.
  • Server Configuration Issues: Certain server settings, like security scanners, mod_security rules, or PHP configuration limits, can interrupt file access or execution.
  • File Permissions: The web server user (e.g., www-data) may not have read permissions for the archive file.
  • Path Aliases or Non-Standard Server Setups: Complex server environments, like Docker containers or custom path configurations, can sometimes confuse the installer when it tries to locate files.

Step-by-Step Troubleshooting Guide

1. Verify File Integrity and Names

This is the first and most crucial step. The installer.php and archive.zip must be a matched pair from the same build process.

  • Check the Filename: The error screen will explicitly tell you the exact filename the installer is looking for (e.g., website_20241027_abcdef_archive.zip). Rename your archive file to match this exactly, including capitalization and underscores.
  • Re-download the Pair: If you suspect a corruption, go back to the original site's Duplicator package screen and download the installer and archive together again. Do not rename them after download.
  • Check File Sizes: Compare the size of the archive file on your server with the original size shown in the Duplicator package list. A significant difference (e.g., Actual Size: 0B) indicates an incomplete upload. Re-upload the file using FTP or your hosting file manager, ensuring the transfer completes fully.

2. Address Server and Hosting Issues

If the files are correct and in place, the issue likely lies with the server environment.

  • File Permissions: Ensure the archive file has read permissions for the web server. Typically, setting file permissions (CHMOD) to 644 is sufficient.
  • PHP ZipArchive Module: The error Class "ZipArchive" not found means the PHP Zip extension is not active on your server. This is a required module. You must contact your hosting provider and ask them to enable the PHP Zip extension for your account.
  • Security Software: As noted in some threads, overly aggressive security software or malware scanners (on your local computer or the server) may quarantine or block the installer.php file, mistakenly identifying it as a threat. You may need to temporarily disable such scanners or whitelist the files during the migration process.
  • Manual Extraction Fallback: In extreme cases where the installer cannot access the archive, you can manually extract the zip file's contents into your website's root directory. Then, create an empty text file and name it exactly what the installer is looking for (e.g., website_20241027_abcdef_archive.zip). Place this empty file in the root folder alongside the installer. This 'tricks' the installer into proceeding, and it will then use the manually extracted files to complete the installation.

3. For Advanced Users and Edge Cases

  • DAF Files: If you are using a .daf archive format, the process is different. The 'Duplicator' team provides a separate command-line extraction tool for these files. You would need to use this tool to extract the archive before running the installer.
  • Character Encoding: For sites with non-Latin characters (e.g., Cyrillic) in file paths, ensure your server is running a modern version of PHP (7.0+) to avoid character encoding issues during extraction.

When All Else Fails

If you have diligently worked through these steps and the problem persists, the issue may be highly specific to your server's configuration. In these rare cases, the collective experience from community forums suggests that the problem may be a complex server-level restriction. As a last resort, testing the migration on a different hosting provider can often confirm if the origin server is the source of the problem.

Remember, successful migration relies on the trio of correct files, correct names, and a compatible server environment. By methodically checking each of these areas, you can resolve most archive-related errors and complete your website migration successfully.

Related Support Threads Support