Back to Community
Home / Community / General

Fixing the WPvivid 'wpvivid_request: error()' Communication Error

52 threads Sep 10, 2025

Content

One of the most common issues users report with the 'Migration, Backup, Staging – WPvivid Backup & Migration' plugin is a communication error that halts backups, restores, and migrations. The error message typically appears as:

wpvivid_request: error(): an error occurred when trying to establish communication with your server. This error may be request not reaching or server not responding. Please try again later.

Variations can include wpvivid_request: timeout(timeout) or wpvivid_request: error(Forbidden). This guide will explain why this happens and walk you through the most effective troubleshooting steps to resolve it.

Why Does This Error Occur?

This error is a generic communication failure. It indicates that a request made by the WPvivid plugin (often an AJAX request to admin-ajax.php) did not complete successfully. The root cause is rarely the plugin itself but is almost always related to the server environment or a conflict on the WordPress site. Based on community reports, the most frequent causes are:

  • Server Security & Caching: Security modules (e.g., ModSecurity), firewalls, or aggressive page caching plugins can block or alter the plugin's requests, returning a 403 Forbidden or timeout error.
  • Resource Limitations: Low PHP memory limits, short maximum execution times, or insufficient disk space can prevent the server from processing the request.
  • Network Configuration: Proxies, custom DNS (like Cloudflare), or local development environments (e.g., Local by Flywheel) can sometimes interfere with internal communication.
  • Plugin or Theme Conflicts: Another plugin or the active theme can cause a fatal error or conflict that breaks the admin-ajax process.

How to Troubleshoot and Fix the Error

Follow these steps in order. After each step, test to see if the issue is resolved before moving to the next.

1. Basic Checks and Retries

First, rule out a temporary glitch. Simply refresh your WordPress dashboard and try the operation again. If it fails again, temporarily disable any caching plugins or server-level cache (e.g., Varnish, Object Caching) and clear all caches. Then, try again.

2. Investigate with Browser Developer Tools

This is a crucial step for diagnosing the specific error. When you click the button that causes the error, open your browser's developer tools:

  1. Press F12 on your keyboard (Chrome, Edge, Firefox).
  2. Click on the Network tab.
  3. With the developer tools open, trigger the error in WPvivid again.
  4. In the Network tab, look for any requests to admin-ajax.php that have a red status code (like 403 or 500). Click on that request.
  5. Check the Response tab for that request. It will often contain a more detailed error message from the server that you can provide to your web host for support.

3. Check for Resource Limits

Backup and migration processes are resource-intensive. Contact your web host or check your hosting control panel to verify your settings meet these minimum recommendations:

  • PHP Memory Limit: At least 256MB, but 512MB is recommended for larger sites.
  • Max Execution Time: 180 seconds or more.
  • Disk Space: Ensure you have free space at least twice the size of your backup file.

4. Conflict Test

A plugin or theme conflict is a common culprit. To test for this:

  1. Deactivate all other plugins except for 'WPvivid Backup & Migration'.
  2. Switch your theme to a default WordPress theme like Twenty Twenty-Four.
  3. Try the WPvivid operation again. If it works, you know a conflict exists. Reactivate your plugins and theme one by one, testing after each, to identify the cause.

5. For Local by Flywheel or Localhost Users

Several threads mentioned this error occurring in Local by Flywheel environments. A suggested fix from the community is to adjust the plugin's settings:

  1. Go to WPvivid Backup > Settings > General Settings.
  2. Uncheck the option for "Optimize for web hosting" or similar.
  3. Save settings and retry.

6. Use the Manual Method

If automated migration continues to fail, the most reliable workaround is to use the manual transfer method. This process is more hands-on but often bypasses the server communication issues:

  1. On your source site, use WPvivid to create a backup and choose to "Exclude the unused files" and "Exclude the unused database tables" to reduce file size.
  2. Download the backup files to your computer.
  3. On your target site, install a fresh copy of WordPress and the WPvivid plugin.
  4. Instead of using the "Migrate" function, go to the Backup & Restore tab.
  5. Upload the backup files you downloaded and restore them individually (database, wp-content, plugins, etc.).

When to Seek Further Help

If you have tried all the steps above and the error persists, the issue is likely a specific server configuration. The detailed error message from your browser's developer console (Step 2) is the key. You will need to share that information with your web hosting provider's support team, as they can investigate server-level security rules, PHP error logs, and other configurations that are outside the scope of the plugin.

By methodically working through these potential causes, you can identify and resolve the communication error preventing WPvivid from working correctly.

Related Support Threads Support