Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Spain
Description
Hello,
I've created an instance running Ubuntu 14.04, with floating IP
130.206.119.164. I was able to connect using a keypair, have set up my
environment there on Friday 22.5.2014 and everything was running smoothly.
Suddenly, today I was not able to connect via ssh, since I get the error
"No route to host". On the other hand, I was able to connect via the VM
display provided on cloud.lab.fiware.org - and found out that port 22 is
opened, and ssh service running. My security rules allow open TCP ports:
22, 25, 80 and 8000-9000.
I am not sure where the problem is now, as I've not changed any
configuration since the last moment it was running properly - Friday. (I
have already tried to reboot the instance)
Thank you,
Juraj Machac
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Juraj Machac <jurajmchc@gmail.com>]
Dear Juraj,
This is a specific question for FIWARE Lab support (http://www.fiware.org/contact-us/). I resend this case to the team in charge, that can be reached via the mailbox fiware-lab-help@lists.fi-ware.org<fiware-lab-help@lists.fi-ware.org
>.
Regards,
Miguel
El 25/05/2015 a las 18:52, Juraj Machac escribió:
Hello,
I've created an instance running Ubuntu 14.04, with floating IP 130.206.119.164. I was able to connect using a keypair, have set up my environment there on Friday 22.5.2014 and everything was running smoothly. Suddenly, today I was not able to connect via ssh, since I get the error "No route to host". On the other hand, I was able to connect via the VM display provided on cloud.lab.fiware.org<http://cloud.lab.fiware.org> - and found out that port 22 is opened, and ssh service running. My security rules allow open TCP ports: 22, 25, 80 and 8000-9000.
I am not sure where the problem is now, as I've not changed any configuration since the last moment it was running properly - Friday. (I have already tried to reboot the instance)
Thank you,
Juraj Machac