BugWP logo BugWP
Back to Community
Home / Community / Plugin → All-in-one wp migration and backup

How to Fix All-in-One WP Migration Upload Limits and File Size Errors

23 threads Sep 7, 2025 Plugin → All-in-one wp migration and backup

Content

Many WordPress users rely on the All-in-One WP Migration and Backup plugin for site migrations. A common and frustrating issue occurs when the plugin reports an upload limit error—like 128MB, 512MB, or 1GB—even after you've correctly increased your server's PHP settings. This guide explains why this happens and walks you through the most effective solutions.

Why Am I Getting an Upload Limit Error?

The upload limit displayed by the All-in-One WP Migration plugin is not a limit set by the plugin itself. Instead, it reads the various restrictions configured on your web server. The error appears when your backup file is larger than the most restrictive limit in your server's environment. Common culprits include:

  • PHP Settings: The primary settings are upload_max_filesize, post_max_size, and memory_limit.
  • Web Server Config: Servers like Nginx or Apache may have their own client max body size directives.
  • Hosting Plan Restrictions: Some shared hosting providers enforce hard limits on upload sizes, which cannot be overridden by changing your PHP settings alone.
  • Execution Timeouts: A large file upload may take longer than the max_execution_time allows, causing the process to fail.

Step-by-Step Troubleshooting Guide

1. Verify and Increase PHP Settings

First, ensure your PHP settings are correctly configured to be larger than your backup file. You typically need to adjust these four values in your php.ini file, or via your hosting control panel (e.g., cPanel):

  • upload_max_filesize = 2048M (Set to a value larger than your backup)
  • post_max_size = 2048M (Set to a value larger than your backup)
  • memory_limit = 2048M (Set to a value larger than your backup)
  • max_execution_time = 0 (Set to 0 for unlimited, or a very high number like 600)

Important: After making these changes, you must restart your web server (e.g., Apache) for them to take effect. Simply saving the file is often not enough.

2. Check for Web Server Limits

If your PHP settings are correct but the problem persists, your web server software might be imposing a separate limit.

  • For Nginx: Look for the client_max_body_size directive in your server configuration and ensure it is also larger than your backup file.
  • For Apache: Limits may be set using LimitRequestBody in an .htaccess file or the server config.

3. Consult Your Hosting Provider's Error Logs

This is a critical step. The error message in your WordPress dashboard is often generic. The true cause of the failure is logged in your server's error logs.

Contact your hosting provider's support team and ask for the error logs for your website around the specific time you attempted the upload. The logs will explicitly state which limit was encountered (e.g., a specific Nginx or security module limit), allowing you or your host to fix it precisely.

4. Consider the 1GB Barrier

Several user reports indicate a recurring issue where uploads fail specifically for files larger than 1GB, even with seemingly correct server settings. This often points to a deeper server-level constraint, such as:

  • A hard cap set by the hosting provider on certain plans.
  • Limitations of a 32-bit PHP build.
  • Security software or firewalls (e.g., ModSecurity) blocking very large requests.

Your hosting provider's support is best equipped to investigate and resolve these specific infrastructure-level issues.

5. Alternative Import Methods

If uploading through the plugin's interface continues to fail, you have another option:

  1. Use an FTP client (like FileZilla) or your hosting provider's file manager.
  2. Navigate to the wp-content/ai1wm-backups/ directory on your destination site.
  3. Manually upload your .wpress backup file to this folder.
  4. Return to the All-in-One WP Migration > Import page in your WordPress admin. Your manually uploaded file should now appear in the list of backups available for restoration.

This method bypasses the web server's upload handlers entirely and is a reliable workaround for many users.

Summary: Key Takeaways

  • The upload limit error is server-related, not plugin-related.
  • Always set upload_max_filesize, post_max_size, and memory_limit to values higher than your backup file.
  • Restart your web server after changing PHP settings.
  • Check server error logs for the exact error—this is the fastest way to identify the problem.
  • For files over 1GB, be aware of potential hosting-level barriers.
  • Use FTP to manually place the file in the ai1wm-backups folder as a proven alternative.

For persistent issues, your hosting provider's technical support is your best resource, as they have full access to your server's configuration and error logs.

Related Support Threads Support