Quantcast
Channel: Active questions tagged amazon-ec2 - Stack Overflow
Viewing all articles
Browse latest Browse all 29259

Can't ssh to AWS EC2: Identity file not accessible

$
0
0

I'm unable to ssh to my EC2 server and am getting the error:

ssh -i /Users/Skeniver/Keepass/skeniver.pem ubuntu@xx.xxx.xx.xxxIdentity file /Users/Skeniver/Keepass/skeniver.pem not accessible: No such file or directory

The file is definitely in the directory and I've chmod'd the directory to 755 and the file to 600:

drwxr-xr-x  14 Skeniver  staff    476 28 Nov  2012 Keepass-rw-------  1 Skeniver  staff    1696  5 Oct  2012 skeniverkey.pem

I'm pretty sure it's a permissions problem, but can't figure out why...

Here is the output of the ssh command using -v, in case it's of any use:

Warning: Identity file /Users/Skeniver/Keepass/skeniver.pem not accessible: No such file or directory.OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 2011debug1: Reading configuration data /etc/ssh_configdebug1: Connecting to xx.xxx.xx.xxx [xx.xxx.xx.xxx] port 22.debug1: Connection established.debug1: identity file /Users/Skeniver/.ssh/identity type -1debug1: identity file /Users/Skeniver/.ssh/id_rsa type 1debug1: identity file /Users/Skeniver/.ssh/id_dsa type -1debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.1debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.1 pat OpenSSH*debug1: Enabling compatibility mode for protocol 2.0debug1: Local version string SSH-2.0-OpenSSH_5.2debug1: SSH2_MSG_KEXINIT sentdebug1: SSH2_MSG_KEXINIT receiveddebug1: kex: server->client aes128-ctr hmac-md5 nonedebug1: kex: client->server aes128-ctr hmac-md5 nonedebug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sentdebug1: expecting SSH2_MSG_KEX_DH_GEX_GROUPdebug1: SSH2_MSG_KEX_DH_GEX_INIT sentdebug1: expecting SSH2_MSG_KEX_DH_GEX_REPLYdebug1: Host 'xx.xxx.xx.xxx' is known and matches the RSA host key.debug1: Found key in /Users/Skeniver/.ssh/known_hosts:8debug1: ssh_rsa_verify: signature correctdebug1: SSH2_MSG_NEWKEYS sentdebug1: expecting SSH2_MSG_NEWKEYSdebug1: SSH2_MSG_NEWKEYS receiveddebug1: SSH2_MSG_SERVICE_REQUEST sentdebug1: SSH2_MSG_SERVICE_ACCEPT receiveddebug1: Authentications that can continue: publickeydebug1: Next authentication method: publickeydebug1: Offering public key: /Users/Skeniver/.ssh/id_rsadebug1: Authentications that can continue: publickeydebug1: Trying private key: /Users/Skeniver/.ssh/identitydebug1: Trying private key: /Users/Skeniver/.ssh/id_dsadebug1: No more authentication methods to try.Permission denied (publickey).

Viewing all articles
Browse latest Browse all 29259

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>