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.
Same issue here. I was able to pull down a couple WPE sites, but one of them simply refused both for me and another developer.
Lot of errors that look like this
{“class”:“RsyncService”,“level”:“warn”,“message”:“Connection to somesite.ssh.wpengine.net closed by remote host.\r\nrsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.3]\n”,“thread”:“main”,“timestamp”:“2024-12-05T18:22:20.664Z”}
{“class”:“ConnectManifestWpeService”,“error”:{},“level”:“error”,“message”:“Error creating manifest for WPE”,“sentryEventId”:“xxxd”,“stack”:“Error: rsync process existed with code 12\n at ChildProcess. (%%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-12-05T18:22:20.667Z”}
{“class”:“RsyncService”,“level”:“warn”,“message”:“Failed to create shell\r\n”,“thread”:“main”,“timestamp”:“2024-12-05T18:22:20.990Z”}
{“class”:“RsyncService”,“level”:“warn”,“message”:“rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.3]\n”,“thread”:“main”,“timestamp”:“2024-12-05T18:22:20.991Z”}
{“class”:“ConnectManifestWpeService”,“error”:{},“level”:“error”,“message”:“Error creating manifest for WPE”,“sentryEventId”:“xxx”,“stack”:“Error: rsync process existed with code 12\n at ChildProcess. (%%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-12-05T18:22:20.995Z”}
{“level”:“info”,“message”:“Electron Event activate”,“timestamp”:“2024-12-05T18:23:41.932Z”}
{“class”:“CAPIService”,“level”:“info”,“message”:“Deleting CAPI SSH key”,“thread”:“main”,“timestamp”:“2024-12-05T18:24:00.048Z”}
I believe WPE had some server hiccups at play that could have impacted your installs. One way to test and make sure your server is okay is to see if you can access your sites via SSH. If you’re unable to do so then there may be an outage or some maintenance going on and you can reach out to WPE support directly to get a ticket in and follow up regarding that.
As a workaround if this is happening, you can always download a backup and direct import that into Local instead of pulling.
As a workaround for pushes, the WPE Migration plugin is free and easy to use from Local to their platform:
As far as further troubleshooting, you’ll want to make sure your API Access is enabled in the WPE dashboard first:
If it’s turned on, you can access your sites via SSH and Local is otherwise working normally, then you might try disabling the API, signing out of WPE in Local, doing a full reboot and then enabling API again, signing back in and seeing if functionality returns.