Unable to negotiate with *** port ***: no matching host key type found.

[tarikrital]

I run the following action but give the error below:

• name: rsync deployments
  uses: burnett01/rsync-deployments@6.0.0
  with:
  switches: -avzr --delete
  path: ./dist/ssr/
  remote_path: ${{ vars.HOST_PATH }}
  remote_host: ${{ secrets.SSH_HOST }}
  remote_port: ${{ secrets.SSH_PORT }}
  remote_user: ${{ secrets.SSH_USER }}
  remote_key: ${{ secrets.SSH_KEY }}

Identity added: (stdin) ((stdin))
Unable to negotiate with *** port ***: no matching host key type found. Their offer: ssh-rsa,ssh-dss
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(231) [sender=3.2.7]

FYI I'm able to connect via terminal from my local machine:
The successful cmd is:
ssh user@ip -pXXXXX

[Burnett01]

Hi, @wpplumber

Can you please try a non-released version of this action: release/5.3

uses: burnett01/rsync-deployments@release/5.3

https://github.com/Burnett01/rsync-deployments/tree/release/5.3

Because it could be related to #24.

Please report back if it works with release/5.3 for you :)

Thanks

[cklm]

I need to connect to a rather old server with Ubuntu 14. Using the current version 6.0 results in an error:

Identity added: (stdin) ((stdin))
Warning: Permanently added '***' (ED25519) to the list of known hosts.
Permission denied, please try again.
Permission denied, please try again.
***@***: Permission denied (publickey,password).
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(228) [sender=3.2.3]

server says in /var/log/auth.log

Jan 12 11:57:52 server sshd[12414]: Failed password for <username> from <runner-ip> port 36864 ssh2
Jan 12 11:57:52 server sshd[12414]: Failed password for <username> from <runner-ip> port 36864 ssh2
Jan 12 11:57:52 server sshd[12414]: Connection closed by <runner-ip> [preauth]

which is an interesting error-message, since we are using the key for authorization, not a password. Using release/5.3 works in that case. Thank you!

[Burnett01]

thanks for the feedback @cklm ! I will thus make an official release for 5.3 soon

[Burnett01]

With the latest release 7.0.0 it is now possible to use legacy RSA hostkeys as an official feature of this action.

Feel free to update to the latest release and activate the support:

    - name: rsync deployments
      uses: burnett01/rsync-deployments@7.0.0
      with:
        switches: -avzr --delete
        legacy_allow_rsa_hostkeys: "true"
        path: ......

More about that in the README.md