Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Fix Version/s: 2021
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
Sender Email:
-
HD-Node:Berlin
Description
Hello,
i am providing support for the FRACTALS accelerator project and i received
an email about open port issues.
In order to reproduce it, i set up a VM and indeed was able to see for
myself that something funny is going on.
The first time i set up the VM, port 80 was open, i was able to test by
deploying a simple web app.
But after a reboot the port closed and remained closed no matter what i did.
Below is the email as it was sent to me:
—
FROM: Tania Peneva TPeneva@centermine.com
Hello!
I have created an instance in fiware cloud. The instance has an internal ip
address 192.168.1.156 and I have assigned it public ip address
193.175.132.43. I have created a security group named "default" and added
rules for ports 22, 80 and 443 to be accessible from anywhere. Port 22 is
working - I have connected via ssh and deployed my servers, which are
listening on 80 and 443. The problem is that I cannot connect on ports 80
and 443:
- on 80 the connection times out
- on 443 the connection is refused
Also I can connect to 80 and 443 using address 193.175.132.43 from another
instance in the same network (I have created another instance which has ip
192.168.1.158).
—
Best Regards,
Aggelos
_______________________________________________
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: Aggelos Groumas <gkraggel@di.uoa.gr>]
Required ports are now open in the central firewall of Berlin node.