Solução de problemas
Corrigir: Fix Empty Server Installer Fails
Causas e correções para « Empty Server Installer Fails » em backups Multisite.
Pro
Correção para Fix Empty Server Installer Fails
When you hit empty server installer fails, 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.
Diagnóstico pelo log para «Empty Server Installer Fails»
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 “empty server installer fails”, 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%.
Correções alinhadas ao Multisite
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/extract. Pick the tool that matches the failure — do not upgrade tiers hoping a cloud auth typo will disappear.
Depois de o arquivo terminar
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.
Retenção, encriptação e higiene de suporte
For fix empty server installer fails, keep enough archive generations to roll back a bad deploy or failed migration. Optional .venc AES-256 encryption on Multisite Migrate archives protects copies at rest when you store offsite on Plus destinations. Document credentials, schedule windows, and who may run Network Admin jobs.
When opening a support ticket, include the last job log lines, hosting class, PHP limits, free disk, and whether a local archive already exists.
Por que importa
Diagnóstico pelos logs
Identifique se a falha é PHP, disco, DB, cloud ou rewrite de URL.
Jobs em chunks como correção padrão
Retomar em vez de reiniciar jobs Multisite enormes do zero.
Verificações após restore
Separar falhas de backup de problemas URL/média/login pós-restore.
Evidência pronta para suporte
Saber quais linhas de log e factos de ambiente capturar para suporte.
Passos
-
1Captar o ponto de falha
Execute este passo no Network Admin ou no subsite e verifique no Staging.
-
2Aplicar a correção certa
Execute este passo no Network Admin ou no subsite e verifique no Staging.
-
3Reexecutar em chunks
Execute este passo no Network Admin ou no subsite e verifique no Staging.
-
4Confirm local archive integrity (localizado)
Execute este passo no Network Admin ou no subsite e verifique no Staging.
-
5Validar o caminho de restore
Execute este passo no Network Admin ou no subsite e verifique no Staging.
Perguntas frequentes
Respostas rápidas sobre este tópico Multisite. Ainda preso? Abra os docs ou fale com o suporte.
Pergunta: Should I raise PHP limits forever?
Resposta Multisite Migrate: Free/Plus/Pro, jobs em chunks, cloud BYO e ensaio de restore em Staging.
Pergunta: Why did the job restart at 0%?
Costuma ser lock perdido, tmp limpo ou novo job ID. Verifique locks e disco antes de reexecutar.
Pergunta: Cloud upload failed but local archive exists?
Corrija auth/quota do destino e reenvie — ou restaure a partir do arquivo local.
Pergunta: Is “empty server installer fails” usually backup or restore?
Resposta Multisite Migrate: Free/Plus/Pro, jobs em chunks, cloud BYO e ensaio de restore em Staging.