Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: Sprint 4.1.2
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
HD-Node:Spain
Description
Web Browser: Firefox 33.0
Operating System: OSX version 10.9.5
User id: cloudtestulpgc
Tenant: 00000000000000000000000000006443
Description
In spite of have the correct security groups with the port 22 open and an
associated keypair, it’s not possible to connect to the instance of the
access-control-gei-tha-3.3.3-1 image.
How to replicate: Launch access-control-gei-tha-3.3.3-1 image with a
security group with the port 22 enabled and an associated keypair and try
to connect it via ssh.
Console output
------------------------------
MacBook-de-Jaisiel:testCloud jaisiel$ ssh root@130.206.85.20 -i test.pem -v
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to 130.206.85.20 [130.206.85.20] port 22.
debug1: Connection established.
debug1: identity file test.pem type -1
debug1: identity file test.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_5.9p1
Debian-5ubuntu1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH_5*
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 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 3f:8d:48:da:c1:c3:99:f5:eb:6d:47:17:93:a8:a0:e3
debug1: Host '130.206.85.20' is known and matches the RSA host key.
debug1: Found key in /Users/jaisiel/.ssh/known_hosts:8
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/jaisiel/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: test.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).
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Spain Node Support Team [ spain.node ] |
Component/s | FIWARE-LAB-HELP [ 10279 ] |
Assignee | Spain Node Support Team [ spain.node ] | Guillermo Jiménez Prieto [ guillermo.jimenez ] |
Status | Open [ 1 ] | Answered [ 10104 ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Done [ 10000 ] |
Fix Version/s | Sprint 4.1.2 [ 10738 ] |
Workflow | FW eRequest Workflow [ 18152 ] | FW extRequest Workflow-II [ 40875 ] |
Status | Done [ 10000 ] | Closed [ 6 ] |
Issue Type | eRequest [ 10101 ] | extRequest [ 10104 ] |
FI-WARE Environment | FI-LAB [ 10100 ] |
HD-Node | Spain [ 10846 ] |
Summary | [Fiware-lab-help] [Cloud] [Spain] Cannot connect to access-control-gei-tha-3.3.3-1 instance via ssh with associated keypair | FIWARE.Request.Lab.Spain.Cannot connect to access-control-gei-tha-3.3.3-1 instance via ssh with associated keypair |