nginx broken after fresh installation (existing services present)

Description

Having an existing Ubuntu 18.04 server install with some other services (Nextcloud, Matrix, Hauk) serving and working fine, after installing Jitsi i’m not able to restart nginx anymore and all my other services are unreachable with errors. Even after deleting the files from /etc/nginx/sites-available/ and /etc/nginx/sites-enabled/ nginx won’t restart anymore. So it seems like the installation is completely messing with my existing nginx config.

I found this https://github.com/jitsi/jitsi-meet/issues/5487 issue and it seems related, if not the same. I’m not quite willing to replicate again because that would mean to make my services again unaccessible. What i can retrieve from my previous searches, this error was present nginx[7683]: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)

I tried various installation-tutorials, some suggesting installing openjdk-8-jre-headless for example: https://community.jitsi.org/t/installation-on-ubuntu-18-04-4-not-working/22773/3 The first one was https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md but there was the same problem present. Tried some other tutorials as well.

I tried to just use sudo letsencrypt --nginx as well so it creates a letsencrypt-cert for me without changing anything else, but thats not working as well because of the nginx error.

Current behavior

nginx cannot be restartet, errors, other services unreachable, even after deleting sites-available and sites-enabled

Expected Behavior

working nginx. Just jitsi not working if there is a problem.

Steps to reproduce

Have services present, install Jitsi.

Environment details

Ubuntu Server 18.04 Nextcloud Collabora Matrix - Synapse Hauk

[damencho]

Yes, it is using the primary domain. But in the latest packages turn is not configured when 443 listening site is available to stop breaking people deployments. This will work for people that want to do a manual install and not break rest of the website. Maybe this just needs to be documented.

[sellth]

Actually it’s not that simple. The NGINX module installed by the jitsi-turnserver package listens for ALPN protocols declared by the accessing party, then directs HTTP traffic to port 4444 and all other traffic to port 4445. This means that clients which don’t support ALPN or don’t use it are always directed to port 4445 i. e. the turn server.

I found this a problem with the Nextcloud Desktop client and the SSL Labs ssltest website. I’m not an expert here, but can we not specifically listen for TURN traffic and default all other traffic towards 4444?