First of all, congrats for the great job: about development, and support !
I have a jitsi-meet server up and running, based the last revision.
It’s NATted (behind the router).
It has been configured (on a clean Ubuntu 18.04) following the “Quick-install” guide … but without adding the Advance Configuration step.
At client side, I use both browser (FF, Crome) and Jitsi-meet app (Android, IOS) …
Port forwarding is only active on “443" (tcp) and on “10000” (udp) ports.
Clients - acting both from internal side (LAN) and external side (WAN) - can connect the server as usual (via “https://mydomain.xx”).
Q1.: May I ask you (positively) … why ?
I’ve been banging my head for weeks, while trying to understand why configuring the server step by step before making any test … it has never been working.
Now, avoiding to implement the Advanced configuration it works “better” than expected.
It means that NGINS is properly acting as proxy ? Involving the right process for “http” and for “https” ?
So it means that now we don’t need anymore to add new lines, like here below, to the file
Or these (not suggested in the advanced config section)
Last though: in the /etc/turnserver.conf file … there is a reference to the <Public.IP.Address> of the server.
My <Public.IP.Address> is dynamic (not fix).
Q2.: Is it possible to have it automatically updated, instead of reporting the IP detected during installation ?