Skip to content

Troubleshooting

What Happens If You Close the Browser Mid-Backup

What usually causes this on WordPress Multisite, what to check first, and how to fix it, including the PHP, server, and plugin settings involved.

Multisite Migrate team3 min readChecked against the plugin docs

Short answer

When you hit browser closed mid backup, start with the Multisite Migrate job log: last completed chunk, PHP/memory messages, HTTP 502/504, disk/inode errors, or cloud auth failures. Multisite archives are larger and table-heavier than single-site jobs, so shared hosts interrupt long PHP requests — Jobs in Chunks exist specifically for that.

Check tmp/disk free space, upload_max_filesize for imports, S3/Drive/Dropbox/SFTP credentials for Plus uploads, and security plugins that block admin-ajax. After restore issues, verify siteurl/home, rewrite rules, domain mapping (sunrise.php), object-cache drop-ins, and CDN caches. Reproduce once on Staging before changing production limits.

Log-first diagnosis for “Browser Closed Mid Backup”

Separate backup failures from post-restore URL/media/login problems. Capture job percent, last log line, HTTP status, hosting class, and whether a local archive already exists. That evidence decides whether you raise PHP limits, free disk, fix cloud auth, or only re-upload.

For “browser closed mid backup”, avoid restarting from scratch if a chunked job can resume. Lost locks, cleared tmp, or a new job ID are common reasons a progress bar jumps back to 0%.

Fixes that match Multisite reality

Raise PHP time/memory enough for safety, but keep chunked jobs — shared hosts can still kill long workers. Free disk and inodes before large network archives. Allow admin-ajax through WAF or security plugins. On Plus, re-test Drive/Dropbox/S3-compatible/SFTP credentials and quotas.

Free handles core backup/restore; Plus covers BYO cloud; Pro covers remote import, empty-server installer, Staging, and split. Pick the tool that matches the failure — do not upgrade tiers hoping a cloud auth typo will disappear.

After the archive completes

If the local archive is good, you can restore even when cloud upload failed. Fix destination auth/quota, then re-upload, or restore from local. On Staging, confirm HTTPS, mapping, media, and logins before production.

If only one subsite looks wrong after restore, check that site’s tables and sites/{id}/ uploads path before re-running the whole network job.

Steps

  1. Capture the failure point
    Record job percent, last log line, HTTP status, and hosting type for “browser closed mid backup” before changing settings.
  2. Apply the matching fix
    Raise safe limits, free disk, fix credentials, or allow AJAX through WAF — based on the log, not guesswork.
  3. Re-run chunked
    Resume the job. Avoid overlapping schedules that collide on locks or wipe tmp mid-run.
  4. Confirm local archive integrity
    If the archive finished, note its size/path. Cloud upload can be retried separately from rebuilding Multisite tables.
  5. Validate restore path
    Test import/restore on Staging. Check URLs, media, logins, and mapping before production changes.

Frequently asked questions

Should I raise PHP limits forever?

Raise them enough for safety, but keep chunked jobs — shared hosts can still kill long workers.

Why did the job restart at 0%?

Often tmp cleanup or a new job ID. Confirm the previous lock is gone before starting again.

Cloud upload failed but local archive exists?

Repair cloud credentials or quota, then retry upload — or restore from the local archive.

Is “browser closed mid backup” usually backup or restore?

Use the job log and symptoms: PHP/disk/cloud failures during the job are backup-side; broken URLs/media/logins after import are restore-side.

Sources

  1. Backup guideMultisite Migrate · checked November 9, 2026
  2. WordPress Multisite / NetworkWordPress Developer Resources · checked November 9, 2026

Make your first restorable network backup for free.

14-day money-back on Plus & Pro · Read the backup guide →