@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ WARNING: UNPROTECTED PRIVATE KEY FILE! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@Permissions 0644 for 'ronald.pem' are too open.It is required that your private key files are NOT accessible by others.This private key will be ignored.Load key "ronald.pem": bad permissionshotaisle@23.183.40.132: Permission denied (publickey).
This issue indicates that the private key file (.pem format) that you have does not have the correct permissions. On unix based systems (Linux or MacOS),
you can run the following line to change the file to the right permissions.you
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!Someone could be eavesdropping on you right now (man-in-the-middle attack)!It is also possible that a host key has just been changed.The fingerprint for the ED25519 key sent by the remote host isxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.Please contact your system administrator.Add correct host key in /Users/xxxxx/.ssh/known_hosts to get rid of this message.Offending ECDSA key in /Users/xxxxx/.ssh/known_hosts:1569Host key for <ip> has changed and you have requested strict checking.Host key verification failed.
This issue appears when the underlying server/host for the IP address has changed since the last time you connected to this IP address.
On Shadeform, a lot of our providers have a pool for their public IP addresses that their machines pull from. Therefore, if you
have previously launched a Shadeform instance and just now relaunched one, it’s very likely that the IP address was reused but the machine
behind the IP is a new one.You can very quickly resolve this problem by running the command below to reset your cache of IPs and hosts.
If you are sure you’re using the correct private key and are still getting permission denied, it’s possible that you have multiple
other keys in your keychain that SSH is automatically trying first. The target server will automatically reject your SSH attempts after a
number of back to back failures. In this case, you will need to specifically target a private key file and only use that one for SSH.you