Error when pulling site - Uh-oh we ran into an issue when pulling from WP engine

Support
1

What issue or error are you experiencing?

When I try to pull a site from WPEngine I am getting this error:
Uh-oh we ran into an issue when pulling from WP engine

I also get this error when I choose Select files under What should we include?
Local coudn't load the file list!

After not using Local for about 2 weeks and getting back on it I see these connection errors now
I think these errors showed up after installing the latest version

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Things that I’ve tried to resolve this:

  1. Restarting Local and relogging into my WPEngine account
  2. I made sure MAMP and other ports aren’t running

System Details

  • Local Version:
    Version 9.1.0+6719

  • Operating System (OS) and OS version:
    macOS Monterrey version 12.2.1

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)
local-lightning.log (375.7 KB)

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.

2

Hi @gregslonina

As a workaround, if you download a backup and direct import it into Local does that work?

Is your API access still enabled on the WPE dashboard?

3

Hi @Nick-B

I downloaded a backup and did a direct import into Local and it worked.

Regarding API access I never saw that tab in WPEngine since I started this project.
Here’s a screenshot:

Screen Shot 2024-10-23 at 10.23.26 AM
Screen Shot 2024-10-23 at 10.23.26 AM1496×507 28.8 KB

I am also connecting to WPEngine from Local via my WPEngine account and not API - It shows that I am connected.

4

Hey @gregslonina

I just looked up your account and you only have partial access which is why you’re not seeing the same toggle for API Access. You’ll have to contact the site owner and have them follow the steps here to enable API Access on the account which is currently disabled.

For now as a workaround you can always use the backup import method instead of pulling, and instead of pushing you can use the free WPE Migration plugin.

5

@Nick-B

You’re right.
https://my.wpengine.com/api_access
I just checked and the API isn’t enabled however I created API credentials 35 days ago. Does the API get disabled every 30 days?

6

Hi @gregslonina

I don’t believe there are any automatic shut-offs. There isn’t anything I can find about that in the WPE documentation. It’s possible someone else with access disabled it unintentionally maybe?

7

@Nick-B
I enabled the API and created new credentials and the issue still persists.

Also I’ve been connecting to WPEngine by logging into my WPEngine account.
There was never an option to add the API credentials.

Screen Shot 2024-10-23 at 1.15.58 PM
Screen Shot 2024-10-23 at 1.15.58 PM1427×671 53.3 KB

8

The steps to physically add API credentials were removed several Local versions ago not that all happens automatically.

Now that you have API Access enabled can you try logging out, quitting Local, restarting your machine, and then going back in to do a big refresh?

Is there anything else unique about your connection? VPN, Office network, hotspot, etc?

9

I tried logging out, quitting local, restarting and going back into local.

I’m not using a VPN or office network or hotspot.

I’ve noticed an rsync error:

{"class":"RsyncService","level":"warn","message":"client_loop: send disconnect: Broken pipe\r\n","thread":"main","timestamp":"2024-10-23T19:26:14.624Z"}
{"class":"RsyncService","level":"warn","message":"client_loop: send disconnect: Broken pipe\r\nrsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.3]\n","thread":"main","timestamp":"2024-10-23T19:26:14.625Z"}
{"class":"RsyncService","level":"warn","message":"rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.3]\n","thread":"main","timestamp":"2024-10-23T19:26:14.625Z"}
{"class":"ConnectManifestWpeService","error":{},"level":"error","message":"Error creating manifest for WPE","sentryEventId":"c24db388ff5f44908a0fe17e3c26f70d","stack":"Error: rsync process existed with code 255\n    at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1682)\n    at ChildProcess.emit (node:events:517:28)\n    at ChildProcess.emit (node:domain:489:12)\n    at ChildProcess._handle.onexit (node:internal/child_process:292:12)","thread":"main","timestamp":"2024-10-23T19:26:14.650Z"}
{"class":"ConnectManifestWpeService","error":{},"level":"error","message":"Error creating manifest for WPE","sentryEventId":"ae71d42fed344fafa39d5741df59668c","stack":"Error: rsync process existed with code 255\n    at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1682)\n    at ChildProcess.emit (node:events:517:28)\n    at ChildProcess.emit (node:domain:489:12)\n    at ChildProcess._handle.onexit (node:internal/child_process:292:12)","thread":"main","timestamp":"2024-10-23T19:26:14.653Z"}
{"class":"RsyncService","level":"warn","message":"client_loop: send disconnect: Broken pipe\r\n","thread":"main","timestamp":"2024-10-23T19:26:47.449Z"}
{"class":"RsyncService","level":"warn","message":"client_loop: send disconnect: Broken pipe\r\n","thread":"main","timestamp":"2024-10-23T19:26:47.453Z"}
{"class":"RsyncService","level":"warn","message":"rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.3]\n","thread":"main","timestamp":"2024-10-23T19:26:47.453Z"}
{"class":"RsyncService","level":"warn","message":"rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.3]\n","thread":"main","timestamp":"2024-10-23T19:26:47.454Z"}
{"class":"ConnectManifestWpeService","error":{},"level":"error","message":"Error creating manifest for WPE","sentryEventId":"3e32eb5adcac401499e0cb2389b24719","stack":"Error: rsync process existed with code 255\n    at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1682)\n    at ChildProcess.emit (node:events:517:28)\n    at ChildProcess.emit (node:domain:489:12)\n    at ChildProcess._handle.onexit (node:internal/child_process:292:12)","thread":"main","timestamp":"2024-10-23T19:26:47.458Z"}
{"class":"ConnectManifestWpeService","error":{},"level":"error","message":"Error creating manifest for WPE","sentryEventId":"2b315e94a52e44e0929421ba0f1a242b","stack":"Error: rsync process existed with code 255\n    at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1682)\n    at ChildProcess.emit (node:events:517:28)\n    at ChildProcess.emit (node:domain:489:12)\n    at ChildProcess._handle.onexit (node:internal/child_process:292:12)","thread":"main","timestamp":"2024-10-23T19:26:47.462Z"}
10

And this error comes up when I try to pull:

{"class":"RsyncService","level":"warn","message":"client_loop: send disconnect: Broken pipe\r\n","thread":"main","timestamp":"2024-10-23T19:32:56.878Z"}
{"class":"RsyncService","level":"warn","message":"rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\n","thread":"main","timestamp":"2024-10-23T19:32:56.883Z"}
{"class":"RsyncService","level":"warn","message":"rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.3]\n","thread":"main","timestamp":"2024-10-23T19:32:56.884Z"}
{"class":"WPEPullService","error":{},"level":"error","message":"Error in WP Engine connect","sentryEventId":"d1c05f41a39b476c8e7d38f147e1fc56","stack":"Error: rsync process existed with code 255\n    at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1682)\n    at ChildProcess.emit (node:events:517:28)\n    at ChildProcess.emit (node:domain:489:12)\n    at ChildProcess._handle.onexit (node:internal/child_process:292:12)","thread":"main","timestamp":"2024-10-23T19:32:56.889Z"}
11

Thank you for testing and following up @gregslonina!

These errors are usually indicative of a couple things. It could be network connectivity issues for one. So as long as your network seems to be strong and stable a way to check if this is a more of a server issue would be to try and SSH into the site. If you’re unable to connect then it might be something that WPE has to raise to their engineers for investigation. I can reach out to them to create a ticket for that unless you want to reach out to WPE support directly.

12

I was able to SSH through the Site Shell so it looks like that is working.

So this worked:
I turned on my VPN and now I’m able to pull without errors.
When I turn off the VPN the error comes back.

Does this mean there’s something wrong with my IP address?

13

Nice! Now we are getting somewhere :slight_smile:

It’s entirely possible that your IP was blocked by WPE’s security which is something we’ve seen before. I can DM you and collect more details and ask their security team to review.

14

Yes, that’d be great if you can reach out to them.
Thank you

15

I’ve sent you a direct message if you can take a look when you have time and respond I’ll connect to them to follow up.

17

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.