Relevant information to this issue:
- (MUST) Qovery
- Programming language and version, databases used: not got that far
- Link to your project on GitHub/Gitlab: not got that far
Describe your issue here
spent the day working on qovery. my use case is deploying a React side project and a Rust side project into EC2 single instance
I have worked through the documentation and 2 clusters trying to get ssh into the cluster
generated ssh key/pub with
ssh-keygen -t rsa -b 2048 -C "qovery"
have also tried with the ‘preferred’
ssh-keygen -t ed25519 -C "email@example.com"
firstname.lastname@example.org: Permission denied (publickey). email@example.com: Permission denied (publickey).
HOW TO REPRODUCE
Do we not need ssh anymore? Have this idea that getting SSH working is essential.
basically the output
kjon-asdf:.ssh user$ ssh -v -i /Users/user/.ssh/id_rsa_covery firstname.lastname@example.org OpenSSH_8.1p1, LibreSSL 2.7.3 debug1: Reading configuration data /Users/user/.ssh/config debug1: /Users/user/.ssh/config line 80: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 47: Applying options for * debug1: Connecting to ec2-54-174-74-166.compute-1.amazonaws.com port 22. debug1: Connection established. debug1: identity file /Users/user/.ssh/id_rsa_covery type 0 debug1: identity file /Users/user/.ssh/id_rsa_covery-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.1 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9p1 Debian-10+deb10u3 debug1: match: OpenSSH_7.9p1 Debian-10+deb10u3 pat OpenSSH* compat 0x04000000 debug1: Authenticating to ec2-54-174-74-166.compute-1.amazonaws.com:22 as 'qovery' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: email@example.com MAC: <implicit> compression: none debug1: kex: client->server cipher: firstname.lastname@example.org MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistpdeletedextracharse51VvU8 debug1: Host 'ec2-54-174-74-166.compute-1.amazonaws.com' is known and matches the ECDSA host key. debug1: Found key in /Users/usdr/.ssh/known_hosts:41 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: email@example.com ED25519 SHA256:UYtIdeletedextracharsi/8A agent debug1: Will attempt key: ED25519 SHA256:dvc3deletedextracharsp6yo agent debug1: Will attempt key: /Users/user/.ssh/id_rsa_covery RSA SHA256:vtkrzdeletedextracharsFA explicit debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: firstname.lastname@example.org ED25519 SHA256:UYtIdeletedextracharsA4i/8A agent debug1: Authentications that can continue: publickey debug1: Offering public key: ED25519 SHA256:dvc3deletedextrachars6yo agent debug1: Authentications that can continue: publickey debug1: Offering public key: /Users/user/.ssh/id_rsa_covery RSA SHA256:vtkrzM0deletedextracharsbFA explicit debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. email@example.com: Permission denied (publickey).