【问题标题】:Permission denied (publickey). Bitnami AWS instance权限被拒绝(公钥)。 Bitnami AWS 实例
【发布时间】:2015-04-04 02:37:43
【问题描述】:

我无法通过 SSH 连接到我的 Bitnami AWS 实例。我对一般的开发很陌生,所以我确定我可能错过了文档中的一些内容,但我做了 chmod 600 并且还尝试了 400 到我的 bitnami-hosting.pem 并且我使用了这个命令。我检查了帖子,发现没有解决方案有帮助。有什么想法吗?

ssh -i ~/.ssh/bitnami-hosting.pem bitnami@ec2-52-10-192-39.us-west-2.compute.amazonaws.com

我也尝试使用公共和私有 IP。 这就是回报

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/adam/.ssh/config
debug1: /Users/adam/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to ec2-52-10-192-39.us-west-2.compute.amazonaws.com [52.10.192.39] port 22.
debug1: Connection established.
debug1: identity file /Users/adam/.ssh/bitnami-hosting.pem type -1
debug1: identity file /Users/adam/.ssh/bitnami-hosting.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 44:de:04:21:c6:8c:08:9f:a6:6d:b1:48:a2:cb:ab:2f
debug1: Host 'ec2-52-10-192-39.us-west-2.compute.amazonaws.com' is known and matches the RSA host key.
debug1: Found key in /Users/adam/.ssh/known_hosts:12
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/adam/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/adam/.ssh/bitnami-hosting.pem
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).

【问题讨论】:

    标签: amazon-web-services ssh bitnami


    【解决方案1】:

    您是否 100% 确定您使用的是正确的 ssh 密钥而不是其他密钥?

    【讨论】:

    • 不是 100%。我去了 Bitnami 的网站,找到了服务器部分并创建了一个新密钥,就像文档所说/暗示的那样。然后我下载了它并将它移动到我的 ~/.ssh/ 目录。在我这样做之后,我做了chmod 600 ~/.ssh/bitnami-hosting.pem。这是我调用 bitnami-hosting.pem 的唯一 .pem 文件,ssh 命令没有出现“找不到文件”之类的错误,所以我猜我找对了。
    • 您无法在启动服务器后创建密钥。您需要使用创建原始服务器时选择的相同密钥。
    • 我放弃了它并创建了自己的 AMI,但我敢打赌你是 100% 正确的,这是我的问题,Daniel。感谢您的帮助!
    猜你喜欢
    • 1970-01-01
    • 2017-08-31
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2017-03-24
    • 2016-02-17
    相关资源
    最近更新 更多