Ga naar de inhoud

Probleemoplossing

Oplossen: Fix Encrypted Backup Wrong Password

Oorzaken en fixes voor „Encrypted Backup Wrong Password“ bij Multisite-backups.

Vrij

Fix voor 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.

Log-first diagnose voor „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%.

Fixes die bij Multisite passen

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.

Nadat het archief klaar is

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.

Retentie, encryptie en support-hygiëne

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.

Waarom dit telt

Eerst de logs

Bepaal of de fout PHP, disk, DB, cloud of URL-rewrite is.

Jobs in chunks als standaardfix

Hervatten in plaats van enorme Multisite-jobs vanaf nul te herstarten.

Checks na restore

Scheid backupfouten van URL-/media-/loginproblemen na restore.

Bewijs klaar voor support

Weten welke logregels en omgevingsfeiten je voor support vastlegt.

Stappen

  1. 1Faalpunt vastleggen

    Voer deze stap uit in Network Admin of op de subsite en controleer op Staging.

  2. 2Passende fix toepassen

    Voer deze stap uit in Network Admin of op de subsite en controleer op Staging.

  3. 3Opnieuw in chunks draaien

    Voer deze stap uit in Network Admin of op de subsite en controleer op Staging.

  4. 4Confirm local archive integrity (lokaal)

    Voer deze stap uit in Network Admin of op de subsite en controleer op Staging.

  5. 5Restore-pad valideren

    Voer deze stap uit in Network Admin of op de subsite en controleer op Staging.

Veelgestelde vragen

Korte antwoorden over dit Multisite-onderwerp. Vast? Open de docs of neem contact op.

Vraag: Should I raise PHP limits forever?

Antwoord Multisite Migrate: Free/Plus/Pro, jobs in chunks, BYO-cloud en Staging-restore-drill.

Vraag: Why did the job restart at 0%?

Meestal verloren lock, geleegd tmp of nieuwe job-ID. Check locks en schijf vóór opnieuw draaien.

Vraag: Cloud upload failed but local archive exists?

Native Plus-doelen: Google Drive, Dropbox, S3-compatible en SFTP. Geen native OneDrive, geen propriëtaire vault.

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

Antwoord Multisite Migrate: Free/Plus/Pro, jobs in chunks, BYO-cloud en Staging-restore-drill.

14-dag geld terug op Plus & Pro

Lees de backup-gids →