Dear,

First of all, in which region are you experiencing this issue ?

Some further checks:

• Did you associate a Floating IP to the instance where the web service runs ?
• Can you reach the instance via ssh ?

Best,
Daniele

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Dear sirs,

the region is Trento.

-Yes, we associate a Floating IP to the instance where the web service runs

-Yes, we reach the istance via ssh.

Furthermore from instance's inside the service is reachable (testing with
"curl" command).

Best regards,

Technical Support
Edisonweb  |  Innovation as a Service  |  [QMS UNI EN ISO 9001:2008]

Via I. Silone, 21  |  IT 95040 Mirabella Imb. [CT]  |  Ph +39 0933 99 11 99 
www.edisonweb.com  |  support@edisonweb.com

----Messaggio originale----
Da: Daniele Santoro daniele.santoro@create-net.org
Inviato: martedì 13 ottobre 2015 13:33
A: Support - Edisonweb <support@edisonweb.com>
Cc: fiware-lab-help@lists.fiware.org
Oggetto: Re: [Fiware-lab-help] about port 3000

Dear,

First of all, in which region are you experiencing this issue ?

Some further checks:

• Did you associate a Floating IP to the instance where the web service runs
  ?
• Can you reach the instance via ssh ?

Best,
Daniele

<support@edisonweb.com> wrote:
associated the instance to a security group where port 3000 is enabled, but
the service was unreachable from the outside.
domain different to @lists.fiware.org will be lost.
(Fiware-lab-help@lists.fiware.org) instead of the old one.

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Dear,

I’ve forwarded your request to the Trento node support. They will give you detailed support on this.

Best,
Daniele

Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-lab-help

Hi all,

By default for the VMs we grant an initial set of ports opened as following:

TCP UDP Protocol
ICMP Ping
22 SSH
53 53 dns
80 HTTP
443 HTTPS
861
1026-1028
4823
8080 HTTP / Openstack API
5000-5005 5000-5005 Keystone - General Purp.
6000-6005 6000-6005 General Purposes
16622 SSH - secondary port

As you can see there are some available segment ports where you can try to activate services.
If you would try to move your services in any of 6000-6005 it could be an option immediately available.
Otherwise if you must use any ports outside these segments let us know in order to modify FW rules.

BR
Genci
Trento Node Team

We forwarded the solution to the user by email.

BR
Genci
Trento Node Team

Hi all,

The user confirmed that they will change the binding to the open port segment (6000 - 6005),
for the service to be reachable from outside.

Best
Genci
Trento Node Team