I just installed the jitsi-meet package(s) on a Ubuntu 18.04 LTS server, following the quick install guide and the secure domain instructions.
So far so good: Conferencing works, authentication works, anonymous guests can join running conferences without authentication, a host needs to authenticate in order to start a new conference.
BUT: When I start a new conference using the anonymousdomain in the browser, I get the pop-up telling me that the host ist not there yet, asking me if I’m the host. So I can authenticate and start the meeting from the anonymousdomain.
That seems inconsitent/odd.
I wonder if that’s just how it is or if I misconfigured something. My expectation would be that I could authenticate only via the main domain (see “domain:” in /etc/jitsi/meet/bla-config.js and “authentication = internal_plain” in /etc/prosody/conf.d/bla.cfg.lua) and not via the anonymousdomain.
It seems that I don’t need to use the main domain in the browser at all: Both, authenticated hosts and guests can use the anonymousdomain.
Am I missing something here?
Thanks for any hint in advance
ii jicofo 1.0-541-1 all JItsi Meet COnference FOcus
ii jitsi-meet-prosody 1.0.3969-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-web-config 1.0.3969-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.1-164-gfdce823f-1 all WebRTC compatible Selective Forwarding Unit (SFU)
ii prosody 0.10.0-1build1 amd64 Lightweight Jabber/XMPP server