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>]
Activity
| Field | Original Value | New Value |
|---|---|---|
| Component/s | FIWARE-LAB-HELP [ 10279 ] |
| Assignee | Henar Muñoz [ henar ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
Thank you for a quick response.
However, I am again unable to connect since yesterday - getting a timeout.
Now I can't even see the instances nor any settings I have on
cloud.lab.fiware.org. Are you still having some networking problems?
Best Regards,
Juraj Machac
Hello,
Now I can see my instance in cloud.lab.fiware.org, but still cannot access
it - getting either a timeout or "No route to host".
It has been 5 days without success now, and I would really like connect to
my instance. The IP is 130.206.119.134
Thank you,
Juraj Machac
---------- Forwarded message ----------
From: Juraj Machac <jurajmchc@gmail.com>
Date: 2015-05-30 8:54 GMT+02:00
Subject: Re: [FI-WARE-JIRA] (HELP-3090) [Fiware-tech-help] Cannot access
instance
To: jira-help-desk@fi-ware.org
Thank you for a quick response.
However, I am again unable to connect since yesterday - getting a timeout.
Now I can't even see the instances nor any settings I have on
cloud.lab.fiware.org. Are you still having some networking problems?
Best Regards,
Juraj Machac
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
| Summary | [Fiware-tech-help] Cannot access instance | FIWARE.Request.Lab.Cannot access instance |
| Sender Email | jurajmchc@gmail.com |
| HD-Node | Spain [ 10846 ] |
| Summary | FIWARE.Request.Lab.Cannot access instance | FIWARE.Request.Lab.Spain.Cannot access instance |
| Fix Version/s | 2021 [ 12600 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1d 13h 31m | 1 | Henar Muñoz | 27/May/15 8:24 AM | |||||
|
1s | 1 | Henar Muñoz | 27/May/15 8:24 AM | |||||
|
9m 33s | 1 | Henar Muñoz | 27/May/15 8:34 AM |
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