Hi,
I am trying to pull one of our sites from WP Engine, however I keep running into the issue where it will pull for 10 minutes, and then I get the error message:
Uh-oh! We ran into an issue when pulling from WP Engine.
1 Like
Just a quick update, but I have upgraded to the latest version (5.2.4) and I am still getting the same issue.
I’ve had a similar (same?) issue with the beta version. The partial error message is “Error: autoload.sql not found for site”.
Log:
local-lightning.log (5.7 KB)
What operating system are you running?
I’m using MacOS Catalina.
It appears that the pull might be timing out, as it only happens with certain installs on WPE.
Hey Everyone –
This is an odd issue that we’re still zeroing in on what’s failing. There could be a few different sources to this bug, so it’s hard to know exactly what’s failing.
The general issue is that for some reason, the database on the remote server isn’t exporting correctly and therefor, Local can’t import the database.
We’re taking a closer look as to why this can happen, but it’s not for every remote site.
As a temporary workaround, you should be able to download a backup from WP Engine and import the zip file into Local by dragging-and-dropping it onto Local.
Let me know if that makes sense, or if you have any other questions!
2 Likes
Had the same issue. I tried it with our site (https://www.enthusiastinc.com), and it got hung up (the site is a couple GBs in size). Then, I tried it with an incredibly small 1 page site (https://www.thebackabbey.com). And got that same message noted above.
We have about 90 site installs on a custom WPE setup, and are adding about 1 every week. Using Local looks like a great solution for our devs here!
1 Like
I’m also on MacOS Catalina. I’ll give the manual download/import a try.
Running OS X Mojave here and two attempts so far with a fresh install of the newest version of Local and both fail for me as well; going to try and download AWS backup from WPEngine and give that a try.
Note: Tried a very small site (~10MB) and a medium sized site (~1GB) just to validate it wasn’t the large site causing issues.
Also running Local with Catlina. I noticed this problem last week, before today’s big announcement, so I’ve had some time to dig into this.
I’ve noticed the following:
-
My database includes two sets of tables. One with the standards “wp_” table prefix and another with the custom table prefix (for security reasons, but also because that’s the way WP Engine creates new WP installs).
-
My wp-config.php file uses the standard “wp_” prefix.
-
My site never quite finishes the pull. It usually gets stuck on the “domain” setup.
-
When I try to access the site, WordPress goes into new install mode and asks me to select a language, then site title, etc.
Eventually, I figured out that I can manually change the table prefix in wp-config, clear my browser cache, restart the machine and get to a working copy of my WP Engine site.
Not very streamlined.
2 Likes
Same here,
Tried the manual method, no warnings other than the copy was successfull, but when I opened the site it was broken, like missing css, and ssl privacy error on google that prevents me from navigate the site.
Then I pulled the site without the DB from WPEngine, same result.
Okay, so interestingly I did a manual import, which left the site with a bunch of errors, so then I did a pull from WPE (which failed), but then did another pull from WPE and that worked. The site appears to be up and running, albeit with a few errors still, but works for the most part.
Just tried it again by deleting the site and running through the same process, same result. Site works, but with some errors.
Wanted to report the same issue here as well. Also using WP-Engine with Local installed on a MacOS Catalina 10.15.3 (latest version).
Very disappointed as WP-Engine announced this as a new solution for creating local WordPress environments that just works.
Hi, similar report here only on macOS Mojave.
When attempting site pull from wpe I had errors after a long time spinning the first two attempts, although the site files did look to have been downloaded.
Closed local, reopened and ran pull without database, which worked, then I pulled again with database and this time I got a reported success, and the site looks good.
Same issue here. Windows 10. Latest updates to Win, WP, etc. When I tried to go to WP-Admin “anyway” this is what shows up:
( ! ) Warning: require_once(C:\Users\Bryce\Local Sites\sigep-at-utks\app\public/wp-includes/load.php): failed to open stream: No such file or directory in C:\Users\Bryce\Local Sites\sigep-at-utks\app\public\wp-load.php on line 49
Call Stack
Time Memory Function Location
1 0.0247 393992 {main}( ) …\index.php : 0
2 0.0261 394760 require_once( ‘C:\Users\Bryce\Local Sites\sigep-at-utks\app\public\wp-admin\admin.php’ ) …\index.php : 10
3 0.0267 395256 require_once( ‘C:\Users\Bryce\Local Sites\sigep-at-utks\app\public\wp-load.php’ ) …\admin.php : 34
( ! ) Fatal error: require_once(): Failed opening required ‘C:\Users\Bryce\Local Sites\sigep-at-utks\app\public/wp-includes/load.php’ (include_path=’.:/usr/share/php:/www/wp-content/pear’) in C:\Users\Bryce\Local Sites\sigep-at-utks\app\public\wp-load.php on line 49
Call Stack
Time Memory Function Location
1 0.0247 393992 {main}( ) …\index.php : 0
2 0.0261 394760 require_once( ‘C:\Users\Bryce\Local Sites\sigep-at-utks\app\public\wp-admin\admin.php’ ) …\index.php : 10
3 0.0267 395256 require_once( ‘C:\Users\Bryce\Local Sites\sigep-at-utks\app\public\wp-load.php’ ) …\admin.php : 34
Get the same issue here, also Windows 10. I noticed that the wp-includes folder seems to be empty so something must be failing during the download.
Error message on frontend if I try to access anyways:
( ! ) Warning: require_once(C:\Users\birgi\Local Sites\modena20live\app\public/wp-includes/load.php): failed to open stream: No such file or directory in C:\Users\birgi\Local Sites\modena20live\app\public\wp-load.php on line 49
Call Stack
Time Memory Function Location
1 0.0237 392960 {main}( ) …\index.php : 0
2 0.0417 393256 require( ‘C:\Users\birgi\Local Sites\modena20live\app\public\wp-blog-header.php’ ) …\index.php : 17
3 0.0672 394104 require_once( ‘C:\Users\birgi\Local Sites\modena20live\app\public\wp-load.php’ ) …\wp-blog-header.php : 13
( ! ) Fatal error: require_once(): Failed opening required ‘C:\Users\birgi\Local Sites\modena20live\app\public/wp-includes/load.php’ (include_path=’.:/usr/share/php:/www/wp-content/pear’) in C:\Users\birgi\Local Sites\modena20live\app\public\wp-load.php on line 49
Call Stack
Time Memory Function Location
1 0.0237 392960 {main}( ) …\index.php : 0
2 0.0417 393256 require( ‘C:\Users\birgi\Local Sites\modena20live\app\public\wp-blog-header.php’ ) …\index.php : 17
3 0.0672 394104 require_once( ‘C:\Users\birgi\Local Sites\modena20live\app\public\wp-load.php’ ) …\wp-blog-header.php : 13
Any word on solving the problem?
Same issue here. We have Local working fine on one machine (Catalina) but having the issues on another machine running High Sierra.
Oddly, when we try the fix by @fitz1889 we can get it working by deleting the WPE MU plugins; however, obviously the next time we pull…we get the MU plugins again.
No way this integration was tested properly. Come on guys…
Hi there! Thanks so much for trying Connect to WP Engine. We fixed a bug that caused databases using a prefix other than “wp_” to fail. Could you try again?
Local 5.2.5 enables database pushing and fixes several other Connect to WP Engine bugs: Local 5.2.5