welaika / wordmove

Multi-stage command line deploy/mirroring and task runner for Wordpress
https://wptools.it/wordmove
MIT License
1.87k stars 165 forks source link

Solution to rsync error: error in rsync protocol data stream #516

Closed sumitpore closed 5 years ago

sumitpore commented 5 years ago

Hi There,

I was trying to use wordmove but it was throwing the error:

rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(235) [Receiver=3.1.2]

I have figured out the solution to the problem. When this problem occurs, we have to disable SSH host key checking for that particular remote server. Procedure to disable it can be found here.

WARNING: There are security implications in disabling SSH Host key. You can read about it here.

sumitpore commented 5 years ago

I am not suggesting this to be included in wordmove. This should be done by individuals on their machine.

citypilgrim commented 4 years ago

Hi, I am having the same problem. Could I ask what machine were you using? I am running rsync on windows, it works when i run it from git bash terminal, but fails when I use the windows command prompt

alessandro-fazzi commented 4 years ago

Thanks for sharing.

I'd add that if you connect manually through SSH and you one-time accept the remote server host key as "recognized" replying "yes" to the prompt, then you should be able to avoid that particular problem.

@bboytian probably your known_hosts is not shared between the two environments. Unfortunately I don't know how it works on Windows, but trying at first a direct SSH connection maybe could help.

cmbuckley commented 3 years ago

I also experienced this error when the destination host was a Synology NAS and the rsync service was not enabled.

prasanta13 commented 3 years ago

I had faced a similar error.

Permission denied, please try again.
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(235) [sender=3.1.3]

I solved it via, go to NAS control panel (synology) set rsync active (inactive by default)

and it was solved.