# Getting a "Uh Oh We Ran Across an Issue when pulling From WP Engine" error

**URL:** <https://community.localwp.com/t/getting-a-uh-oh-we-ran-across-an-issue-when-pulling-from-wp-engine-error/50246>\
**Category:** Support\
**Created:** [May 22, 2025, 4:14pm UTC](https://community.localwp.com/t/getting-a-uh-oh-we-ran-across-an-issue-when-pulling-from-wp-engine-error/50246 "2025-05-22T16:14:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ehudsonchoicelocal](https://avatars.discourse-cdn.com/v4/letter/e/45deac/32.png) [@ehudsonchoicelocal](https://community.localwp.com/u/ehudsonchoicelocal)\
**Post date:** [May 22, 2025, 4:14pm UTC](https://community.localwp.com/t/getting-a-uh-oh-we-ran-across-an-issue-when-pulling-from-wp-engine-error/50246/1 "2025-05-22T16:14:57Z")

</div>

I’m trying to connect to a website on WPE but getting this error. Can you please help me resolve this? This is the only site I’m having an issue with.

 ![Screenshot 2025-05-22 at 12.10.18 PM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/b/2/b23aa08dd6e4235a93f90cd28fc2ec04f0e71a7f.jpeg)

* * *

 ![Screenshot 2025-05-22 at 11.52.54 AM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/2/5/25fd25799fbf78da489fb215eb3090f1901776d6.png)

* * *

I’m running on a Macbook Air.

- \*\*Local Version:Version 9.2.4+6788

- \*\*Operating System (OS) and OS version: MAC OS Sonoma 14.6.1

* * *

### Local Logs

[local-lightning.log](https://community.localwp.com/uploads/short-url/eVc39JoN2UGBiI7Ae7kA9u3oTHP.log) (658.9 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.

---

<div class="post-metadata">

**Author:** ![nickc](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nickc/32/21209_2.png) [@nickc](https://community.localwp.com/u/nickc)\
**Post date:** [May 23, 2025, 1:15pm UTC](https://community.localwp.com/t/getting-a-uh-oh-we-ran-across-an-issue-when-pulling-from-wp-engine-error/50246/2 "2025-05-23T13:15:19Z")

</div>

Thanks for sharing your log, @ehudsonchoicelocal.

The section below suggests you may have a file on the remote under `/wp-content/temp/elfHp49FI/wp-content/themes/goldfishswim-understrap-child/` that rsync is struggling to download.

If you don’t need these files under the (non-standard) `wp-content/temp/` path on the remote, you could try backing up and removing them, then attempting the pull with Local again.

If that does not work you could try exporting the site with WP Migrate and importing into Local instead of pulling directly.

```auto
[receiver]\nERROR: buffer overflow in recv_file_entry [receiver]\n","thread":"main","timestamp":"2025-05-22T15:45:53.194Z"}
{"class":"RsyncService","level":"warn","message":"rsync error: error allocating core memory buffers (code 22) at util2.c(111) [receiver=3.1.3]\n","thread":"main","timestamp":"2025-05-22T15:45:53.194Z"}
{"class":"WPEPullService","error":{},"level":"error","message":"Error in WP Engine connect","sentryEventId":"440ac8aff98a455f81d4b3c0557c93c5","stack":"Error: rsync process existed with code 22\n at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:60:28)\n at ChildProcess.emit (node:events:518:28)\n at ChildProcess._handle.onexit (node:internal/child_process:293:12)","thread":"main","timestamp":"2025-05-22T15:45:53.205Z"}
/wp-content/temp/elfHp49FI/wp-content/themes/goldfishswim-understrap-child/

```

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [August 21, 2025, 1:15pm UTC](https://community.localwp.com/t/getting-a-uh-oh-we-ran-across-an-issue-when-pulling-from-wp-engine-error/50246/3 "2025-08-21T13:15:59Z")

</div>

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