I definitely understand that! Have you been able to pull this site in the past? Or other sites from WPE without issue?
Sometimes users are in a hurry to start working on their site so the import workaround is helpful to just get things moving along. It also helps determine if the issue is one with the site since it might still fail on import, or something interrupting the Local Connect flow. The logs are a bit sparse, and 4 GB isn’t necessarily a huge site but it is big enough that maybe some connection interference happened.
The specific error, ERR_CHILD_PROCESS_STDIO_MAXBUFFER has shown up in the past and is usually some type of issue with the database. If you get the same error when trying to do a manual import that could confirm the suspicions. In order to get the site into Local you might have to do a more manual approach.
The steps would look like this:
- Download a backup zip of the site
- Unzip the file in a common location, like the desktop
- Create a new, blank site in Local. Use whatever username/password you like since you’ll overwrite the DB with this site archive’s dump.
- Copy the wp-content folder from the unzipped location to this newly created site’s location
- Copy the correct SQL dump to the site root.
- Within Local, open the site shell
- Import the dump with wp db import
<dumpfile> - If that works, now Search and replace the domains.
wp search-replace ' https://production.com ' 'http:mylocalsite.local'