[Fiware-lab-help] Not able to connect to VM display through VNC

[kuldeep mishra]

Hi Support team,

I've created an instance though following procedure:

Deploying a dedicated GE instance based on an image
> In order to deploy a dedicated instance of this GEi perform the following
> actions:
>
>    1. Access the FIWARE Cloud Portal (http://cloud.lab.fiware.org)
>
>
>    1. Login with your login/password (if you don't have a login/password,
>    please register on http://account.lab.fiware.org)
>
>
>    1. Click on the "Images" option at the left, then "Launch" selecting
>    the row with the name *cep-r5.4.1-img*, which will launch an image
>    identified as *cep-r5.4.1-img*, when asked for the memory model
>    (flavor) chose at least *m1.medium*. In a matter of minutes a
>    ready-to-use VM instance of this GEi will appear in the "Instances" area
>    (see the FIWARE Cloud Portal guide for additional information on VM
>    management using FIWARE Cloud).
>
> After creating the instance successfully, i'm not able to connect to it,
neither through web console(VM display through VNC) nor through ssh(After
assinging global IP) to it.
When accessing though VNC I'm getting attached screen "VNC display"( with
no login screen).

and when connecting it through ssh using private key: "ssh -i newkey1.pem
130.206.113.104 -l root", I'm getting error: "Permission denied
(publickey)".
ssh debug logs are attached.

Please help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20170523/0e11f21f/attachment-0001.html>
-------------- next part --------------
ssh -i newkey1.pem 130.206.113.104 -l root
debug2: ssh_connect: needpriv 0
debug1: Connecting to 130.206.113.104 [130.206.113.104] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file newkey1.pem type -1
debug1: key_load_public: No such file or directory
debug1: identity file newkey1.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 pat OpenSSH_6.6.1* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 130.206.113.104:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: curve25519-sha256 at libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01 at openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01 at openssh.com,ssh-dss-cert-v01 at openssh.com,ssh-dss,ecdsa-sha2-nistp384-cert-v01 at openssh.com,ecdsa-sha2-nistp521-cert-v01 at openssh.com,ssh-ed25519-cert-v01 at openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes256-gcm at openssh.com,aes128-cbc,3des-cbc,arcfour,aes128-gcm at openssh.com,chacha20-poly1305 at openssh.com,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes256-gcm at openssh.com,aes128-cbc,3des-cbc,arcfour,aes128-gcm at openssh.com,chacha20-poly1305 at openssh.com,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,rijndael-cbc at lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,umac-128 at openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-sha1-96,hmac-md5-96,umac-64-etm at openssh.com,umac-128-etm at openssh.com,hmac-sha2-256-etm at openssh.com,hmac-sha2-512-etm at openssh.com,hmac-md5-etm at openssh.com,hmac-sha1-etm at openssh.com,hmac-ripemd160-etm at openssh.com,hmac-sha1-96-etm at openssh.com,hmac-md5-96-etm at openssh.com,hmac-ripemd160 at openssh.com
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,umac-128 at openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-sha1-96,hmac-md5-96,umac-64-etm at openssh.com,umac-128-etm at openssh.com,hmac-sha2-256-etm at openssh.com,hmac-sha2-512-etm at openssh.com,hmac-md5-etm at openssh.com,hmac-sha1-etm at openssh.com,hmac-ripemd160-etm at openssh.com,hmac-sha1-96-etm at openssh.com,hmac-md5-96-etm at openssh.com,hmac-ripemd160 at openssh.com
debug2: kex_parse_kexinit: zlib at openssh.com,zlib,none
debug2: kex_parse_kexinit: zlib at openssh.com,zlib,none
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256
debug2: kex_parse_kexinit: aes256-ctr,aes192-ctr,aes128-ctr
debug2: kex_parse_kexinit: aes256-ctr,aes192-ctr,aes128-ctr
debug2: kex_parse_kexinit: hmac-sha2-512,hmac-sha2-256,hmac-ripemd160
debug2: kex_parse_kexinit: hmac-sha2-512,hmac-sha2-256,hmac-ripemd160
debug2: kex_parse_kexinit: none,zlib at openssh.com
debug2: kex_parse_kexinit: none,zlib at openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: server->client aes128-ctr hmac-sha2-256 zlib at openssh.com
debug1: kex: client->server aes128-ctr hmac-sha2-256 zlib at openssh.com
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<8192<8192) sent
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug2: bits set: 4104/8192
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:ClowBKiNk1WVGCbwIgtxRRNh+S1HnbEmYCq56/duJgs
debug3: hostkeys_foreach: reading file "/home/mobaxterm/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/mobaxterm/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 1 keys from 130.206.113.104
debug1: Host '130.206.113.104' is known and matches the RSA host key.
debug1: Found key in /home/mobaxterm/.ssh/known_hosts:4
debug2: bits set: 4120/8192
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: newkey1.pem (0x0), explicit
debug3: input_userauth_banner
##################################################################################
NOTE: You have accessed a system owned by FIWARE Lab. You must have authorisation
before using it, and your use will be strictly limited to that indicated in the
authorisation.
Unauthorised access to this system or improper use of the same is prohibited and
is against the FIWARE Terms & Conditions Policy and the legislation in force. The
use of this system may be monitored.
#################################################################################



debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred hostbased,publickey,password,keyboard-interactive
debug3: authmethod_lookup publickey
debug3: remaining preferred: password,keyboard-interactive
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: newkey1.pem
debug3: sign_and_send_pubkey: RSA SHA256:0VqLYMZ7ZCfe5BYDreGbfyBigWY1Uga6wX5zANM2qQg
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VNC display.png
Type: image/png
Size: 101131 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20170523/0e11f21f/attachment-0001.png>