Dear.

Did you configure the security group properly for your instance ?

Here is few hints: http://www.slideshare.net/flopezaguilar/setting-up-your-virtual-infrastructure-using-fi-lab-cloud-30583860 and https://youtu.be/fAVH3b67hP8

If you still have problem let me know I will forward to the specific region support.

Daniele

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.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Hello

yes we did all as specified and more than once.
Everytime with the same results

Please forward to the region support

Thanks in advance

Stamatis Poulimenos

—
Αυτό το e-mail ελέγχθηκε για ιούς από το πρόγραμμα Avast antivirus.
https://www.avast.com/antivirus

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.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Thanks, I’ve just forwarded it to the region support.

Daniele

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.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Dear user,

thank you for the information. We checked your VM that has uuid_ 'e00c1d84-ba6b-4858-824d-e99ac82959c5 '_ and name:_ 'ISTMOS'_.
It seems that the ip you have attached is not available from outside for the public-ext-net-02.
As we have observed the VM has attached a node-int-net-01 internal IP, that means that can get a public ip form the public-ext-net-01 so as to get access on it.
Consequently, please try the followings so as to fix the issue:
1. Disassociate floating public-ext-net-02 IP from the VM. Go Security --> Floating IPs --> right click on the IP and the click on 'Disassociate Floating IP' choice.
2. Release the floating IP, right click on the IP and then click on 'Release Floating IP'.
3. Allocate a new Floating IP from the public-ext-net-01. Security --> Floating IPs --> Allocate IP to project, select public-ext-net-01 and finally click 'Allocate IP'
4. Associate the new floating ip to 'ISTMOS' VM.
5. Finally try to get access by using the new IP with the corresponding ssh-key, having of course the keypairs for ssh default port 22 associated to your VM.

Please confirm if the above work for your situation, as well as your problem has been solved.
We remain available for any further clarification.

Best Regards,
Dimitria Kelaidonis, on behalf of PiraeusU tech team

After p2p communication with the user, problem has been solved.
Ticket is considered as closed.