ssh command, when used with the
--rsh) option in
rsync, should not need to mention the remote host by name as this is part of the source specification (in your command).
In your case, it would be enough to use
rsync --progress -avz -e "ssh -i ~/.ssh/keyFile" firstname.lastname@example.org:/path/to/files/ ~/Downloads/
rsync will execute the command given in
-e together with the source path. You can see the exact command being executed if you use yet another
-v. It will most likely look something like
opening connection using: ssh -i "~/.ssh/keyFile" email@example.com -l root 188.8.131.52 rsync --server --sender -vvlogDtpre.iLfxC . /path/to/files/
Here, you can see that
184.108.40.206 would be interpreted as a command to be executed on the remote host as user
root (taking the actual command that ought to be executed as command line arguments).
rsync starts a "sender" on the source side of the file copy, and a "receiver" on the destination side. These two processes are then communicating the actual data and checksums etc. between each other to carry out the file copy. The
ssh command that you see above is the command that
rsync uses to (try to) start the sender on the remote host. The
--server --sender etc. are internal command line flags that
rsync uses for this purpose. The
rsync manual basically says "don't use these options yourself".
In your case, you can see in the error message that the receiver (
rsync running locally) is having problems communicating with the sender on the remote host. This is because the sender wasn't started correctly, and this in turn was due to the erroneous