I did a docker image using a nightly build and I tried it runs fine in
my computer, but when I put it in a external host (in a cloud), I can't see
one from other browser. I have this ports opened: 10000 to 10100/udp, 4443,
5222, 5269, 5280, 5347/tcp
To test, i have Chrome and Chromium, each one with its cam. Works fine in
my machine and others sites like appear.in. Using in this external host, no
Someone have some tips to debug what's happen?
Since now, thanks in advance.
2016-08-02 11:27 GMT-03:00 Claudio Ferreia Filho <firstname.lastname@example.org>:
Thank you, Damian. I will see this docs.
2016-07-27 16:20 GMT-03:00 Damian Minkov <email@example.com>:
You also need to setup the addresses so jvb knows them:
You will also need forward udp ports, and default 4443 for tcp media,
or 443 if you are running with jetty. By default single-port
communicating is enabled (port 10000), but of it fails for some reason
it will fallback to the other port range.
On Wed, Jul 27, 2016 at 2:03 PM, Claudio Ferreia Filho >> <firstname.lastname@example.org> wrote:
> I'm trying to use a jitsi-meet docker image. It ups in a private net
> question if can I expose only the https port to host or I *need* to
> too the UDPs ports.
> This question is the util also if I put my app server in a internal net,
> redirected from a reverse proxy, like Nginx, from a DMZ.
> Some tip or reference to read?
> Sinse now, thanks in advance.
> Claudio Ferreira
> dev mailing list
> Unsubscribe instructions and other list options:
dev mailing list
Unsubscribe instructions and other list options: