A brief becomes a real page.Fix a stalled backup upload
Check host limits and use the server upload folder when necessary.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- Access to the affected site and AI connection.
- A redacted copy of the exact error.
Let’s do this, step by step.
Step 01
Check the job
Keep the backup/restore tab open and inspect progress, errors, and available disk space.
The uploader sends small pieces and can retry with smaller ones. The whole backup does not need to fit in one upload request.
Step 02
Read the limits panel
Open Safety → Backup & Migrate → Restore. Review Server upload limits and Read the upload guide beside any hosting rejection.
Compare the upload limits with the actual error. Your host can reject a request even when the displayed PHP limits are large enough.
Step 03
Use the hosting controls if needed
Ask the host or use its PHP settings panel to adjust supported limits. Recheck the panel afterward.
Start with the hosting controls. Server types differ, so do not paste configuration directives intended for a different server.
Step 04
Use the file-manager route
Upload the .emcp archive with SFTP or the host file manager into wp-content/emcp-backups/uploads/, then refresh Available to restore.
This avoids browser request-size limits. You still need sufficient disk space and a complete archive; there is no promise of unlimited host storage.
Step 05
Restore and verify
Back up the destination, choose the complete archive, restore, and inspect the resulting site.
Getting the file onto the server is only part of the job. Verify representative pages and admin access after the restore.
You’re done when…
The complete archive is available and the test restore has a verified result.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.