FW External User added a comment - 17/Jun/15 10:53 AM Good morning Jesus. I can confirm that the IP is working fine with the instance, this morning. Could you please let me know what the issue was and is there a simple workaround (from my side)?  Many thanks,Anuj From: Help-Desk <jira-help-desk@fi-ware.org> To: anujcsood@yahoo.com Sent: Wednesday, 17 June 2015, 9:31 Subject: [FI-WARE-JIRA] ( HELP-3342 ) [Fiware-lab-help] FI-LAB issue (public IP to virtual machine) Good morning Now you have access to ip 130.206.113.77 with MyBudget-V1 associated to it. Please try now Best Regards Jesus Message Title We are facing this issue and need your help. We created an instance on the FI-LAB (MyBudget-V1) using the Ubuntu 14.04 image and and associated the public IP (130.206.113.77). We were successfully able to access the VM via SSH and internet and installed the LAMP stack.  However, later when we tried the IP in combination with the VM (SSH or internet), it is not working.  Separately, the VM is working since we were able to connect via the Connect to your instance console using an additional user that we had created initially (in addition to the root). The public IP was also working as we were able to associate it with a new VM (Test) and able to SSH. However, this floating IP is not working with either the MyBudget-V1 or the Test VM. The Spain2 node is working. Do you know why this is happening and how can we solve the problem (even after disassociating and associating the public IP, we are not able to SSH/internet the MyBudget-V1 VM now)? This has happened before also (at that time I just terminated the instance and started again thinking it was a one-off problem). As separately the floating IP and the VM work (and they work the first time), there seems to be a problem with the association or the security group after sometime. Tenant id is 00000000000000000000000000007919 Many thanks,Anuj Anuj SoodMyBudget, a funded project from FINODEX Accelerator ----- Forwarded Message ----- From: Pasquale Vitale <pvitale@eng.it> To: Anuj Sood <anujcsood@yahoo.com> Sent: Tuesday, 16 June 2015, 7:55 Subject: Re: FI-LAB issue (public IP to virtual machine) Hi Anuj, check if you node is available at this link http://fi-health.lab.fi-ware.eu/ . Then if you have problem in FIWARE Lab, please send a mail to fiware-lab-help@lists.fi-ware.org including your ID. Best regards, Pasquale Il 15/06/2015 21:18, Anuj Sood ha scritto: Hello,  We are facing this issue and need your help. We created an instance on the FI-LAB (MyBudget-V1) using the Ubuntu 14.04 image and and associated the public IP (130.206.113.77). We were successfully able to access the VM via SSH and internet and installed the LAMP stack.  However, today when we tried the IP in combination with the VM (SSH or internet), it is not working.  Separately, the VM is still working since we were able to connect via the FI-LAB Cloud console using an additional user that we had created initially (in addition to the root). The public IP is also working as we were able to associate it with a new VM (Test) today and able to SSH. The Spain2 node is working. Do you know why this is happening and how can we solve the problem (even after disassociating and associating the public IP, we are not able to SSH/internet the MyBudget-V1 VM now)? This has happened before also (at that time I just terminated the instance and started again thinking it was a one-off problem). Many thanks, Anuj Anuj Sood MyBudget, a funded project from FINODEX Accelerator _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help [Created via e-mail received from: Anuj Sood <anujcsood@yahoo.com>] |