How to Fix the “Timed Out While Contacting Website” Backup Error

Why am I seeing this?

The “Timed Out While Contacting Website” error means the backup process didn’t get a response from your site’s server within the expected window. The cause is almost always something blocking our requests from reaching your site, or insufficient server resources once it arrives. The fix is to work through the request path in order — from the outermost layer (network and firewalls) inward to the application (PHP and MySQL). Most sites resolve this in one or two passes.

Key Takeaways

• A backup request travels through CDN, firewall, security plugin, PHP, and MySQL layers before completing. The timeout can happen at any one of them.
• Troubleshooting follows the same path: confirm ManageWP IPs aren’t blocked first, then check PHP resource limits, then MySQL’s max_allowed_packet.
• The recommended PHP values for reliable backups: memory_limit = 512M, upload_max_filesize = 256M, post_max_size = 256M, max_execution_time = 300, max_input_vars = 3000.

What typically causes this?

The timeout is almost always traceable to one of these patterns:

• A CDN or external firewall (Cloudflare, Sucuri, Imperva, Amazon CloudFront) blocking ManageWP backup IPs
• Server-level firewall rules or host-applied IP filters blocking the same IPs
• A security plugin (Wordfence, Solid Security, All-In-One WP Security) blocking the request before it reaches WordPress
• PHP resource limits set too low for the size of your backup
• A low MySQL max_allowed_packet value breaking the database export mid-stream
• Heavy server load at the moment the backup ran (sometimes temporary)

Each cause sits at a specific layer of the backup request path: the request has to pass through your CDN, your server-level firewall, and your security plugin before it ever reaches WordPress. Once inside, PHP runs the backup and MySQL handles the database export. The troubleshooting steps below follow that same path in order. If the request can’t pass an outer layer, fixes at deeper layers won’t help, which is why IP allowlisting comes before PHP limits, even though PHP limits are statistically the more common cause.

How do I fix this error?

Step 1: Retry the backup

Run the backup again from the ManageWP dashboard before changing anything. Timeouts are sometimes one-off events caused by a temporary load spike, and a clean retry is the fastest possible fix.

If the backup completes on the second attempt, you’re done. If it fails again with the same error, move to Step 2.

Step 2: Allow ManageWP backup IPs

If a CDN, firewall, or security plugin is blocking our backup requests, the request never reaches your site so no PHP or MySQL fix will help, because the backup process never gets the chance to run.

We send backup requests from a specific set of IP addresses. The current list is maintained on the ManageWP IP Allowlist page. You’ll need to allow those IPs in three places:

1. CDN or external firewall — in your Cloudflare, Sucuri, Imperva, or CloudFront configuration, add our IPs to the allowlist.
2. Server-level rules — confirm with your host that no server firewall, fail2ban rule, or hosting-applied IP filter is blocking the same IPs.
3. Security plugin — open your active security plugin (Wordfence, Solid Security, All-In-One WP Security, etc.) and add the IPs to its allowlist.

After the IPs are allowed in all three places, retry the backup. If it completes, you’re done. If it still times out, the request is now reaching your site but something inside WordPress is failing. Continue to Step 3.

Tip: If you know your site doesn’t sit behind a CDN, doesn’t use a security plugin, and your host doesn’t apply external firewall rules, you can skip Step 2 and start with Step 3. PHP limits are the most common cause on plain hosting setups.

Step 3: Raise your PHP resource limits

Once the request reaches WordPress, PHP runs the backup. If the resource limits are set too low for your site’s backup size, PHP runs out of memory or time partway through and the process dies. This results in a timeout.

1. Log in to your hosting control panel.
2. Open File Manager.
3. Navigate to the root directory where your WordPress installation lives.
4. Locate the php.ini or .user.ini file.
5. Compare the values against the recommended values:

memory_limit = 512M

upload_max_filesize = 256M

post_max_size = 256M

max_execution_time = 300

max_input_vars = 3000

6. If any value is lower than recommended, edit the file and save.

The new limits take effect immediately on most hosting environments.

Note: php.ini defines global PHP values for the entire server, while .user.ini allows PHP values to be overridden on a per-directory basis and is typically used when php.ini can’t be modified directly.

Important: On shared hosting, your ability to change these values from the user side is often restricted. If you can’t find the file, can’t edit it, or the values don’t take effect after editing, contact your hosting support team. They can either raise the limits for you or confirm that your plan caps them below what backups need.

After updating the limits, retry the backup. If it completes, PHP limits were the cause. If it still times out, the issue is at the database layer — continue to Step 4.

Step 4: Increase the MySQL max_allowed_packet value

If the request is reaching your site and PHP has enough resources, the next layer to check is MySQL. The max_allowed_packet setting caps the size of a single data packet during the database export. When a single table or row exceeds the limit, the export breaks mid-stream and ManageWP reports a timeout.

1. Ask your hosting support team to check your my.ini or my.cnf file (MySQL’s main configuration file, usually managed by your host) for the current max_allowed_packet value, or check it yourself if you have server-level access.
2. Raise the value. A common starting point is 256M, but the right value depends on your largest table size (your host can advise).

Most shared hosting plans don’t expose this setting to the user, so this step usually requires a quick support request to your host.

After the value is raised, retry the backup.

What to keep in mind for next time?

The “Timed Out While Contacting Website” error always happens somewhere along the request path: CDN → firewall → security plugin → PHP → MySQL. When the error appears, check the layers in that order. Fixes deeper in the stack won’t help if an outer layer is dropping the request.

Sites behind Cloudflare, a security plugin, or any other IP-filtering layer should add ManageWP backup IPs to their allowlists proactively, not only after an error appears. It’s a one-time setup that prevents this entire category of failure.

Still stuck?

If you’ve worked through all the steps and the backup still times out, your site likely has an edge case beyond what the standard fix covers. Contact ManageWP support with:

• The website URL where the error occurred
• The steps you’ve already tried
• Your hosting type (shared, VPS, managed) — this changes which fixes are even available

That information lets the support team skip diagnostics and dig straight into your specific case.

Frequently Asked Questions

Why does the backup time out only sometimes, not every time?

Intermittent timeouts usually point to server load rather than a hard configuration limit. When your server is under heavy load (from traffic spikes, cron jobs, or other backups running) it may not have the resources to complete a backup within the expected window. Raising PHP resource limits gives the backup more headroom and reduces the frequency of these intermittent failures.

Can I fix this on shared hosting if I can’t edit php.ini?

Sometimes, but not always. Many shared hosts allow PHP limit increases through their control panel UI even when direct file editing is restricted. If the UI option doesn’t exist or doesn’t go high enough, your hosting support team can raise the limits server-side, or confirm whether your plan caps them below what’s needed for backups.

What’s the difference between php.ini and .user.ini?

The php.ini file defines global PHP settings for the entire server. The .user.ini file allows PHP settings to be overridden on a per-directory basis, and is typically used when php.ini can’t be modified directly. On most shared hosting, .user.ini is the file you’ll actually be working with.

Do I need to allow ManageWP IPs on a brand-new site?

Not usually. Most fresh WordPress installs don’t have IP-blocking security layers active by default. The IP allowlist step matters when you’ve installed a security plugin, sit behind a CDN like Cloudflare, or your host applies firewall rules at the server level.

Does this error affect my live site or just the backup?

Just the backup. Your live site keeps running normally regardless of whether the backup completes. The error means the backup process can’t finish, but no other ManageWP feature or your WordPress site itself is affected.