Level 75
Have you seen this article.
https://blog.laravel.com/forge-connect-to-your-server-using-ssh-or-sftp
Sep 17, 2019
6
Level 3
SSH key issue
Hello all - just spun up a new AWS instance VIA Forge.
Everything seems to be working fine, apart from being able to SSH in. I've added key to the Forge interface as per instructions, but I get the following:
Admins-iMac:~ admin$ ssh forge@xxxxxxxxxx -v OpenSSH_7.9p1, LibreSSL 2.7.3 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 20: Applying options for * debug1: Connecting to 18.130.145.49 [18.130.145.49] port 22. debug1: Connection established. debug1: identity file /Users/admin/.ssh/id_rsa type 0 debug1: identity file /Users/admin/.ssh/id_rsa-cert type -1 debug1: identity file /Users/admin/.ssh/id_dsa type -1 debug1: identity file /Users/admin/.ssh/id_dsa-cert type -1 debug1: identity file /Users/admin/.ssh/id_ecdsa type -1 debug1: identity file /Users/admin/.ssh/id_ecdsa-cert type -1 debug1: identity file /Users/admin/.ssh/id_ed25519 type -1 debug1: identity file /Users/admin/.ssh/id_ed25519-cert type -1 debug1: identity file /Users/admin/.ssh/id_xmss type -1 debug1: identity file /Users/admin/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.9 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH_7.0,OpenSSH_7.1,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002 debug1: Authenticating to 18.130.145.49:22 as 'forge' 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: chacha20-poly1305@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:g0NjiY9N8X2syR/YkWrPUDpWCUoOeMsd53c1LHHuJTI debug1: Host '18.130.145.49' is known and matches the ECDSA host key. debug1: Found key in /Users/admin/.ssh/known_hosts:1 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: Will attempt key: /Users/admin/.ssh/id_rsa RSA SHA256:2yXMexgc6ttPEPAdgotR+C46tbCwrAB7psM+6jYPCiU debug1: Will attempt key: /Users/admin/.ssh/id_dsa debug1: Will attempt key: /Users/admin/.ssh/id_ecdsa debug1: Will attempt key: /Users/admin/.ssh/id_ed25519 debug1: Will attempt key: /Users/admin/.ssh/id_xmss 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: /Users/admin/.ssh/id_rsa RSA SHA256:2yXMexgc6ttPEPAdgotR+C46tbCwrAB7psM+6jYPCiU debug1: Authentications that can continue: publickey debug1: Trying private key: /Users/admin/.ssh/id_dsa debug1: Trying private key: /Users/admin/.ssh/id_ecdsa debug1: Trying private key: /Users/admin/.ssh/id_ed25519 debug1: Trying private key: /Users/admin/.ssh/id_xmss debug1: No more authentication methods to try. forge@xxxxxxxxx: Permission denied (publickey).
HEEEELLLLPPP PLEASE
Level 3
Yeah bro. Word for word
Level 3
Bump
Level 5
@antlusher From AWS documentation:
Confirm that you are using the private key file that corresponds to the key pair that you selected when you launched the instance.
Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
Select your instance. In the Description tab, verify the value of Key pair name.
If you did not specify a key pair when you launched the instance, you can terminate the instance and launch a new instance, ensuring that you specify a key pair. If this is an instance that you have been using but you no longer have the .pem file for your key pair, you can replace the key pair with a new one. For more information, see Connecting to Your Linux Instance if You Lose Your Private Key.
You may read further here https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesConnectingSSH
1 like
Level 3
Thank you - but the instance is managed by Lara Forge, so the keys are provide via the Forge interface... Just got an email from Forge saying I sould do what I've already done many times over. This is why I dislike using these sort of management consoles etc. Cheers
Level 3
Fixed. Didn't pass a user name when generating the.key. durrrrr me
Please or to participate in this conversation.