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>]
Activity
Hi,
i just restarted the VM and checked again and its closed now...Is there a
time constraint or something like that? I will leave the app deployed and
check again in 10 minutes.
$ nmap 130.206.115.64
Starting Nmap 6.40 ( http://nmap.org ) at 2015-07-13 17:27 EEST
Nmap scan report for 130.206.115.64
Host is up (0.053s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp closed https
On Mon, Jul 13, 2015 at 4:49 PM, Help-Desk <jira-help-desk@fi-ware.org>
–
Groumas Aggelos
Research Assistant
SCAN Lab ~ http://scan.di.uoa.gr/
Berlin node by default allows only connection via SSH port 22. Any other ports needed will be opened upon request.
This is due to the restrict policies of our IT department.
I now requested to configure the following ACL:
IP: 193.175.132.43
Port: 80; tcp; http
Port: 443; tcp; https
Is this correct or other ports needed on the Berlin node?
Ports are opened on the central firewall. No comments from user, therefore ticket will be closed.
Required ports are now open in the central firewall of Berlin node.
Hello Henar,
OK, would appreciate if you could delegate to Berlin support, to see what
is their take on this.
Back to my tests, the VM i used has IP 130.206.115.64, it is in Spain2
region, and it is based on Ubuntu_14.04.1 x64 image.
I have not set the web app to execute during startup (with crontab etc) but
after each restart, i log into the VM and start the app myself. Its a
simple spring boot web app with embedded tomcat that listens on port 80.
If you want i can send you the .pem key to have a look on the inside, as it
is a VM purely to test the ports issue.
BR,
Aggelos
On Mon, Jul 13, 2015 at 2:50 PM, Help-Desk <jira-help-desk@fi-ware.org>
–
Groumas Aggelos
Research Assistant
SCAN Lab ~ http://scan.di.uoa.gr/