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.
I’ve re-gen’ed the API credentials and killed anything running on port 80 on my local and still getting the same error. local-lightning.log (103.3 KB)
@Nick-B seems that 443 is only being used by my web browser, nothing else.
It seems to be the error is stemming from this rsync process failing {"thread":"main","class":"WPEPullService","stack":"Error: rsync process existed with code 12\n at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1183)\n at ChildProcess.emit (node:events:527:28)\n at ChildProcess.emit (node:domain:475:12)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)","eventId":"42406d9c3d47429c8244ec0991cf0678","level":"error","message":"rsync process existed with code 12","timestamp":"2023-06-21T19:24:11.221Z"}
I understand it’s not as elegant I just wanted to make sure it worked at least as an alternative option. It also helps us to narrow our troubleshooting focus. Are any of the sites you are working on overly large? Do they have lots of media, big databases, etc?
Okay well if your colleagues are able to pull stuff down normally, then that negates the point of my test. It seems the issue is specific to your machine/connection. I’m assuming you’ve tried all manner of restarts, reboots, and tried resetting your API credentials already. You’re still able to directly import a backup so the site shouldn’t be the problem especially if it’s small and Local is still able to accept and spin it up.
To do a more aggressive reset, you could give the below steps a try:
Export any sites that you have on Local and save them to a folder somewhere on your computer.
When the computer is restarted and turned on, close any applications that automatically run in the background (AntiVirus, Firewall, and other Developer applications included).
I had this same error message (as well as Local couldn’t load the file list! when trying to pull a new site) weirdly only on WP Engine sites. Flywheel sites continued to push and pull fine.
Thanks to this thread I discovered /Library/Logs/local-lightning.log where I saw
{"thread":"main","class":"RsyncService","message":"/Users/jacob/.ssh/config line 2: garbage at end of line; \"#\".\r\n","level":"warn","timestamp":"2023-07-24T21:12:40.766Z"}
{"thread":"main","class":"RsyncService","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","level":"warn","timestamp":"2023-07-24T21:12:40.767Z"}
{"thread":"main","class":"ConnectManifestWpeService","sentryEventId":"6552717388124a9aa27e22a16cd98858","level":"error","message":"Error creating manifest for WPE Service","timestamp":"2023-07-24T21:12:40.769Z"}
{"thread":"main","class":"ConnectManifestWpeService","level":"error","stack":"Error: rsync process existed with code 255\n at ChildProcess.<anonymous> (%%appPath%%/main/rsync/RsyncService.js:1:1548)\n at ChildProcess.emit (node:events:527:28)\n at ChildProcess.emit (node:domain:475:12)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)","message":"rsync process existed with code 255","timestamp":"2023-07-24T21:12:40.769Z"}
Helped me discover a line in my ~/.ssh/config that had both config and a comment:
IdentityFile ~/.ssh/id_rsa # set default so it doesn't just use newest
Turns out some programs (like rsync apparently) really need comments to be strictly on their own line starting with # so I edited my ~/.ssh/config and now Local is pushing and pulling to WP Engine again.
# set default so it doesn't just use newest
IdentityFile ~/.ssh/id_rsa
