Vai al contenuto

Risoluzione problemi

Risolvere: Fix Encrypted Backup Wrong Password

Cause e fix per « Encrypted Backup Wrong Password » nei backup Multisite.

Gratuito

Fix per Fix Encrypted Backup Wrong Password

When you hit encrypted backup wrong password, 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.

Diagnosi dal log per «Encrypted Backup Wrong Password»

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 “encrypted backup wrong password”, 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%.

Fix allineati alla realtà 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.

Dopo che l’archivio è completo

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.

Retention, cifratura e igiene support

For fix encrypted backup wrong password, 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.

Perché conta

Diagnosi dai log

Capite se l’errore è PHP, disco, DB, cloud o rewrite URL.

Jobs in chunks come fix predefinito

Riprendere invece di riavviare da zero job Multisite enormi.

Check lato restore

Separa fallimenti backup da problemi URL/media/login post-restore.

Prove pronte per il support

Sapere quali righe di log e fatti ambiente catturare per il support.

Passi

  1. 1Catturare il punto di errore

    Eseguite questo passo in Network Admin o sul subsite e verificate su Staging.

  2. 2Applicare il fix corretto

    Eseguite questo passo in Network Admin o sul subsite e verificate su Staging.

  3. 3Rieseguire in chunks

    Eseguite questo passo in Network Admin o sul subsite e verificate su Staging.

  4. 4Confirm local archive integrity (localizzato)

    Eseguite questo passo in Network Admin o sul subsite e verificate su Staging.

  5. 5Validare il percorso restore

    Eseguite questo passo in Network Admin o sul subsite e verificate su Staging.

Domande frequenti

Risposte rapide su questo tema Multisite. Ancora bloccato? Apri i docs o contatta il support.

Domanda: Should I raise PHP limits forever?

Risposta Multisite Migrate: Free/Plus/Pro, job in chunks, cloud BYO e drill di restore in Staging.

Domanda: Why did the job restart at 0%?

Di solito lock perso, tmp svuotato o nuovo job ID. Controlla lock e disco prima di rieseguire.

Domanda: Cloud upload failed but local archive exists?

Destinazioni native Plus: Google Drive, Dropbox, S3-compatible e SFTP. Niente OneDrive nativo né vault proprietario.

Domanda: Is “encrypted backup wrong password” usually backup or restore?

Risposta Multisite Migrate: Free/Plus/Pro, job in chunks, cloud BYO e drill di restore in Staging.

Rimborso di 14 giorni su Plus e Pro

Leggi la guida backup →