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.
local-lightning-verbose0.log:{“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”:“2023-10-26T16:08:38.494Z”}
local-lightning-verbose0.log:{“class”:“ConnectManifestWpeService”,“level”:“error”,“message”:“Error creating manifest for WPE Service”,“sentryEventId”:“f8a95c52481e4643b33364bfd984f60b”,“thread”:“main”,“timestamp”:“2023-10-26T16:08:38.496Z”}
local-lightning-verbose0.log:{“class”:“ConnectManifestWpeService”,“level”:“error”,“message”:“rsync process existed with code 255”,“stack”:“Error: rsync process existed with code 255\n at ChildProcess. (%%appPath%%/main/rsync/RsyncService.js:1:1548)\n at ChildProcess.emit (node:events:513:28)\n at ChildProcess.emit (node:domain:489:12)\n at ChildProcess._handle.onexit (node:internal/child_process:291:12)”,“thread”:“main”,“timestamp”:“2023-10-26T16:08:38.497Z”}
Actually, in addition to disconnecting/reconnecting, I mean regenerating those API credentials that you use to connect to WPE as well. Details in the article above^
When the computer is restarted and turned on, close any applications that automatically run in the background (AntiVirus, Firewall, and other Developer applications included).
Check and see if the issue still persists. If so, please provide us with an updated log. Retrieving Local’s Log File
Our Devs narrowed down what they believe to be the root cause here and have released a Beta version of Local to try and see if it resolves the problem. Once we know this fix works we’ll roll out a stable release to follow! Can you give this a try and let us know if it does the trick?
Thank you for confirming @jhenrywaugh! We’ve heard from several other WPE users that this is the case and will likely have a stable release out today with the fix.
I am having a weird issue. I had upgraded to the latest release as of today, 8.1.0, but when I tried to connect to a site to pull, I kept getting an error that it couldn’t get a list of files. I tried to go back to 8.0.2 official release, and it wasn’t working either. I was able to SSH in and I was able to get a list of the sites with the API key I had.
Oddly, I had to revert back to Version 8.0.1+6490 in order to connect and get a list of files.
I tried pulling down the beta as well and it doesn’t work either. When using anything above v8.0.1, it seems to give me the same errors in the logs: {"class":"RsyncService","level":"warn","message":"Cannot access install mysite\r\nConnection to mysite.ssh.wpengine.net closed by remote host.\r\n","thread":"main","timestamp":"2023-11-13T22:45:47.217Z"} {"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":"2023-11-13T22:45:47.218Z"}
I am using an SSH key and a custom config that specifies the specific key for any ssh.wpengine.net host. If I SSH in using the same key and with the same install, I can connect just fine. I know with v8.0.2 there were some changes to ignore local config files for SSH, so not sure if this has anything to do with it.
Hi, I am running version Version 8.0.2+local-beta-6503 but still can’t connect to WPE to pull a site. I am running OSX 14.1.1, here’s my log: local-beta.log (13.0 KB)
If you’re still having problems after that please click the Download Local Logs button from the Support tab in Local. This will generate a zip archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering.
