Troubleshooting site creation from Backuply archive

Attempting to restore a ‘Backuply’ (https://backuply.com) archive to a local site fails. The restore hangs at about 70% and results in a half-functional site.

Restoring the same archive to a new location on my Namecheap.com server works fine. I am currently working with Backuply support to see if they can identify the issue, but I figured I would drop a note here, in case someone else has encountered this issue. (I searched the forum but found no mention of ‘Backuply’ either because nobody here uses it or because ‘Backuply’ is a weird name that the forum search engine can’t deal with.)

If I make progress with the Backuply people, I’ll report it here.


To replicate:

  1. Use Backuply to back up a WP site on some public-facing server
  2. Use Local to create a new WP site locally
  3. Add the Backuply plugin to the local site
  4. Download the backup archive from the public site and import to the local site via the Backuply plugin
  5. Use Backuply to (attempt to) restore the local site using the imported archive.
  6. Note that the restoration hangs around 70% and that although the site is largely restored, it is not complete.

I should also note: I have successfully restored a smaller site I manage without error. The tar.gz file for the unsuccessful site is just under 300MB.


System Details

  • Local Version: Version 10.1.1+6939

  • Operating System (OS) and OS version: macOS Tahoe (26.6.1) on iMac M4


Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)


Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

You mentioned a smaller site worked fine @mstrange. Is the site that’s erroring out quite large?

There are some workflows you can use to get a Local site imported. For example, you could directly import a zip backup file with a WP-Content and SQL within. Or you could do a manual import option as well. Details for both are in our guide here.

If you need a plugin to make a zip export for you, you can use a free one like WP Migrate Lite:

As mentioned above, the tar.gz file for the failing site is just under 300MB. I don’t think it is “quite large” but it’s larger than the other site I maintain.

My main point in posting was to see if anybody else uses that successfully with Local; I guess nobody else here uses Backuply, or those folks are not active contributors.

Yesterday I was notified that the folks at Backuply are working on reproducing the issue; I’ll let you know if they find anything.

Sorry for misreading that @mstrange

I’ve never used Backuply myself, but something we’ve seen confuse imports in the past are things like additional backup files, or databases stored within the site files. Would anything like that be included with your site’s backup content? Another possibility could be WordPress core file modifications as well.

Keep us posted if you hear back from their support with any further details!

I just got this email from the Backuply folks…
We were able to replicate the issue on our end, and have tried a fix, will it be possible for you to try this and attempt to restore, for some reason the issue was happening only on Safari browser, although it is a general fix…

I have confirmed that the fix works for me, and I have asked them if there is anything about it that might be helpful for y’all to know.

Thank you for the update here @mstrange! I’m glad to hear you were at least able to get things working on your end.