I'm trying to get a collection of docker images that I can configure and
run as a set of containers for a quick and simple deployment of Jitsi meet
for people in the future. I am aware of the issues around ports with
running the videobridge in a container but will deal with that later. First
I am just trying to get the signalling working.
I am not so familiar with XMPP so links to reference material explaining
how non-trivial aspects affecting this configuration would be very welcome.
So, imagine that you have a set of independent servers on the same LAN as
in the diagram here:
If each server is running on a separate host, named after the server, then
we could have a set of servers named: nginx, prosody, jicofo and
The documentation continues to discuss a domain and set of subdomains but
it is not clear which components use them and from where they need to be
resolvable. The (sub)domains I see are:
It would seem that the main domain (jitsi.example.com) should resolve to
nginx. focus.jitsi.example.com seems to be something to do with jicofo.
jitsi-videobridge.jitsi.example.com should resolve to videobridge. That
leaves conference and auth which I think seem to be something to do with
prosody, as those subdomains are configured there.
Is it possible to not use subdomains, but instead use a set of LAN
hostnames such as having hosts named nginx, prosody, jicofo and
videobridge? Would that then allow doing a mapping of the domains and
subdomains in the documentation to hostnames as follows:
Or are there requirements in XMPP that some addresses must be on subdomains?
Which domains and subdomains necessarily need to have public DNS records to
be resolvable by clients? Or more precisely, from where do each of the
domains and subdomains need to be resolvable?
Which ports need to be exposed to the world such that jitsi meet clients
can interact with them? It looks like only :443 on the web server and :4443
on the videobridge, plus UDP/TCP ports for media transport for videobridge.