Dear,

I assume you are referring to the instances on Spain2 region and I've forwarded your request to Spain support.

Best,
Daniele

The issue has been emailed:

• Time sent: 11/Jul/16 12:54 PM
• To: cokoso@gmail.com
• with subject: *(HELP-6896) [Fiware-lab-help] FIWARE Lab Assistance *
  

Hi,

There doesn't seem to be any problem connecting your host:
$ ssh 130.206.xxx.xxx
The authenticity of host '130.206.xxx.xxx (130.206.xxx.xxx)' can't be established.
ECDSA key fingerprint is d4:9e:60:bb:c0:e6:f2:83:29:ee:26:c6:9b:5b:c8:4c.
Are you sure you want to continue connecting (yes/no)? ^C

Regards,
José Ignacio

Comment by cokoso@gmail.com :

Hi Jose Ignacio,
Thanks for your feedback. however, my connection still failed.
I usually connect in this way :

ssh -i xxxxx.pem root@130.206.119.144

and i am receiving

ssh: connect to host 130.206.119.144 port 22: Connection timed out

Am I losing something?
Regards,Octavio,

Flow Computing Coop. V.
www.flowcomputing.es
info@flowcomputing.es

[image: Logo FLOW] <http://www.flowcomputing.es/>

[image: COOP] <http://www.identity.coop/es>

2016-07-11 12:55 GMT+02:00 Help-Desk <jira-help-desk@fi-ware.org>:

> Hi,
>
> There doesn't seem to be any problem connecting your host:
> $ ssh 130.206.xxx.xxx
> The authenticity of host '130.206.xxx.xxx (130.206.xxx.xxx)' can't be
> established.
> ECDSA key fingerprint is d4:9e:60:bb:c0:e6:f2:83:29:ee:26:c6:9b:5b:c8:4c.
> Are you sure you want to continue connecting (yes/no)? ^C
>
> Regards,
> José Ignacio
>
>
> -------------------------------------------------------------------------------
> José Ignacio Carretero Guarde created HELP-6896:
> ---------------------------------------------------
>
> Summary: [Fiware-lab-help] FIWARE Lab Assistance
> Key: HELP-6896
> URL: https://jira.fiware.org/browse/HELP-6896
> Project: Help-Desk
> Issue Type: extRequest
> Components: FIWARE-LAB-HELP
> Reporter: FW External User
> Assignee: José Ignacio Carretero Guarde
>
>
> Hi,
> My name is Octavio Glorio. I am currently restarting an instance that
> allocate our prototipe "finidt" . Specifically, we are workink in the
> linkage of our prototipe to a data structure allocate in Global Instance of
> Cosmos.
> However, we cannot connect to this instance any more. I had tried
> restarting, but also allocating in a different public IP. Finally, I had
> tried to access (ssh) to a new fresh instance just to check and I had the
> same problem. Could be a problem with my last months inactivity? How
> should we proceed?
> These are the details of my instance:
>
> - *Name: * 4GreenBack2
> - *ID: * c49b4070-928a-4f24-8cc4-aa6bd387bae5
> -
>
> Thanks in advance,
> Octavio.
>
> Flow Computing Coop. V.
> www.flowcomputing.es
> info@flowcomputing.es
>
> [image: Logo FLOW] <http://www.flowcomputing.es/>
>
> [image: COOP] <http://www.identity.coop/es>
>
> Since January 1st, old domains won't be supported and messages sent to any
> domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (
> Fiware-lab-help@lists.fiware.org) instead of the old one.
>

Comment by cokoso@gmail.com :

Hi Jose Ignacio,
Solved. I had connected successfully to our machine during the weekend.
Something change in the proxy of our lab and I did not notice. Sorry for
the misleading and thanks for the support.
Best Regards,
Octavio.

Flow Computing Coop. V.
www.flowcomputing.es
info@flowcomputing.es

[image: Logo FLOW] <http://www.flowcomputing.es/>

[image: COOP] <http://www.identity.coop/es>

2016-07-19 7:46 GMT+02:00 Help-Desk <jira-help-desk@fi-ware.org>:

> I've been testing the connection with your VM from serveral places,
> including GSM connection on my mobile phone and I still can't find any
> problem connecting with port 22 on your VM from nowhere.
>
> Maybe you could send me a "tcptracedump 130.206.119.144 22", but there is
> no way I can reproduce your problem
>
> Regards,
> José Ignacio.
> FW External User
> <https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user>
> created an issue
>
> Help-Desk <https://jira.fiware.org/browse/HELP> / [image: extRequest]
> <https://jira.fiware.org/browse/HELP-6896> HELP-6896
> <https://jira.fiware.org/browse/HELP-6896>
> [Fiware-lab-help] FIWARE Lab Assistance
> <https://jira.fiware.org/browse/HELP-6896>
> Issue Type: [image: extRequest] extRequest
> Assignee: José Ignacio Carretero Guarde
> <https://jira.fiware.org/secure/ViewProfile.jspa?name=jicg>
> Components: FIWARE-LAB-HELP
> Created: 11/Jul/16 12:09 PM
> Priority: [image: Major] Major
> Reporter: FW External User
> <https://jira.fiware.org/secure/ViewProfile.jspa?name=fw.ext.user>
>
> Hi,
> My name is Octavio Glorio. I am currently restarting an instance that
> allocate our prototipe "finidt" . Specifically, we are workink in the
> linkage of our prototipe to a data structure allocate in Global Instance of
> Cosmos.
> However, we cannot connect to this instance any more. I had tried
> restarting, but also allocating in a different public IP. Finally, I had
> tried to access (ssh) to a new fresh instance just to check and I had the
> same problem. Could be a problem with my last months inactivity? How
> should we proceed?
> These are the details of my instance:
>
> - *Name: * 4GreenBack2
> - *ID: * c49b4070-928a-4f24-8cc4-aa6bd387bae5
> -
>
> Thanks in advance,
> Octavio.
>
> Flow Computing Coop. V.
> www.flowcomputing.es
> info@flowcomputing.es
>
> [image: Logo FLOW] <http://www.flowcomputing.es/>
>
> [image: COOP] <http://www.identity.coop/es>
>
> Since January 1st, old domains won't be supported and messages sent to any
> domain different to @lists.fiware.org will be lost.
> Please, send your messages using the new domain (
> Fiware-lab-help@lists.fiware.org) instead of the old one.
>