Local Community

Adding Site from Cloud Backup & Google Fails - MacOS

I’m using 2 computers: a MacBook pro 16 2019 and iMac 27 2020. Both are running the latest Local 6.3.0+5756. Both are running the latest MacOS Monterey Beta 12.3

I’ve created a cloud backup from the MacBook via Google Drive, which worked fine. I then go to the iMac and create a site from that backup. The site is created without errors, but it cannot be accessed. I get errors such as 502 request error. The “WordPress version” appears as constantly loading.

I’ve tried changing the PHP version, Nginx/Apache, changing Site Domains → Localhost, restarting Local, restarting the computer, tried 3-4 times to create the site from backup, nothing worked.

One of the errors seen:

It seems wp-load.php is missing.

Looking at the folder contents in Local Sites, I think a lot of files are missing: there’s no wp-includes folder and various other files.

I tried copying these missing files and wp-includes manually from the old site (macbook) to the new site. What happens is that I can access the site but I see a WordPress installer that’s asking me to configure WordPress from scratch. If I do, none of my data is there - it’s an empty wp install.

Router log and lightning log:
local-lightning.log (100.1 KB)
error.log (11.2 KB)

Thank you,

Hi @stefsss, thanks for posting! I’m looking into this one on my MacBook Pro, running Monterey 12.2.1.

It looks like that restore stopped midway, or at least missed files. Something that could help me track this down - does this happen consistently? If you create a new site from that same backup again (“MyBackup2”, for example), does wp-load.php or the wp-includes folder come through?

Ideally, I’d like to track down if the files were missed when creating the backup or if they just don’t pull through on creation.

Hi @austinwendt , Thanks for looking into this and for working on Local - awesome product!

I tried running some other tests to help figure out if the files are missing from the backup itself or there’s an issue with site creation.

  1. On the original macbook where the backup was created, I tried using the “Clone site from this backup” option to create a new site from the backup. This worked correctly.
  2. Similarly, on the same macbook I tried clicking on Plus → New Site → Create site from Cloud Backups Addon. This also works - site contents are intact. So I guess the backup itself is fine.

  1. I then switch computers to go on the iMac and do exactly what I did on point (2). This does not work. Wp-load.php and wp-includes/ do not exist in the site.

  2. I made another backup of the same site on the macbook and now there’s an updated backup (v2). On the iMac I tried restoring from this updated backup. Still does not work. Something is different though: now it’s stuck on “Starting up site services…”. No folder for the site has been created in Users/myuser/Local Sites.

  3. I tried logging in and out of the google account on the iMac - same results in tests.


  1. I tried to see if it works when I create a cloud backup on the iMac and and then restore from that backup on the same iMac. Strangely enough…this works. Also works if I restore on the macbook from this backup created on the iMac.
  2. Last test. I go back to the macbook and create another backup, for another site, a very small one with 1 plugin = 50mb total (previous one was larger = 700mb). This time it works to restore it on the iMac.

Not sure what this means - maybe there was indeed an issue with the original backup - or maybe it has to do with its larger size. Is there a way I can delete that backup so I can do it again from scratch? I can’t see it. In Google Drive I can’t find the backup either - is it hidden somehow? I might just have too many folders and files.

1 Like

Bump. It’s June 2022.

Bump. It’s Mid-June 2022

I was checking the forums for a problem I was having with Cloud Backups and it turns out, this is the exact problem I’m having. Almost 7 months later, seems there is still no fix?

Fortunately, the process of manually restoring a cloud backup is well documented and worked flawlessly for me, if somewhat tedious.

Doesn’t mean that this is a bug that should be ignored.