Jitsi update breaks NGINX (modules?) configuration, blocks start via occupied port 443

Description

---

Yesterday (2020-03-31) I did a dist-upgrade on my server. After this the local NGINX server no longer starts. I have an existing NGINX configuration, serving a mattermost instance (via dedicated NGINX sites-enabled config), installed jitsi according to quick-install, which worked flawless until the update.

Current behavior

---

NGINX fails to start:

Mar 31 17:31:34 communication nginx[2045]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
Mar 31 17:31:35 communication nginx[2045]: nginx: [emerg] still could not bind()
Mar 31 17:31:35 communication systemd[1]: nginx.service: Control process exited, code=exited status=1
Mar 31 17:31:35 communication systemd[1]: nginx.service: Failed with result 'exit-code'.
Mar 31 17:31:35 communication systemd[1]: Failed to start A high performance web server and a reverse proxy server.
 Subject: Unit nginx.service has failed

Asked the forum Link and a user mentioned that this might be related to the latest release and that the modules configuration is what blocks the start.

As I require the mattermost instance, I modified the port in /etc/nginx/modules-enabled/60-jitsi-meet.conf to listen 4443;

This obviously breaks something in Jitsi, but at least the webserver comes up again.

Expected Behavior

---

Jitsi site configuration can coexist with another site on the same NGINX instance, with different hostnames

Possible Solution

---

Steps to reproduce

---

Environment details

---

apt list --installed
jicofo/stable,now 1.0-539-1 all [installed,automatic]
jitsi-meet/stable,now 1.0.4335-1 all [installed]
jitsi-meet-prosody/stable,now 1.0.3928-1 all [installed,automatic]
jitsi-meet-turnserver/stable,now 1.0.3928-1 all [installed,automatic]
jitsi-meet-web/stable,now 1.0.3928-1 all [installed,automatic]
jitsi-meet-web-config/stable,now 1.0.3928-1 all [installed,automatic]
jitsi-videobridge2/stable,now 2.1-157-g389b69ff-1 all [installed,automatic]
prosody/bionic,bionic,now 0.10.0-1build1 amd64 [installed,automatic]
nginx/bionic-updates,bionic-security,now 1.14.0-0ubuntu1.7 all [installed]
nginx-common/bionic-updates,bionic-security,now 1.14.0-0ubuntu1.7 all [installed,automatic]
nginx-core/bionic-updates,bionic-security,now 1.14.0-0ubuntu1.7 amd64 [installed,automatic]

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.4 LTS
Release:	18.04
Codename:	bionic

[damencho]

You can just delete /etc/nginx/modules-enabled/60-jitsi-meet.conf and move the jitsi-meet virtual host to port 443 and this will solve it for you. We are working on a fix for this situation (that include new stable push).

[damencho]

PR #5545 should fix this, by not configuring turn server if there is already a virtual host listening on port 443.