Web request redirected to turn server on fresh Debian10 Installation

Description

After an upgrade my installation stopped working with a 502 error. I then did a fresh reinstalled and observed the exact same behaviour. It seems like /etc/nginx/modules-enabled/60-jitsi-meet.conf does exactly the configured behaviour and redirects all traffic per default to the turnserver:

    upstream web {
        server 127.0.0.1:4444;
    }
    upstream turn {
        server 127.0.0.1:4445;
    }
    # since 1.13.10
    map $ssl_preread_alpn_protocols $upstream {
        ~\bh2\b         web;
        ~\bhttp/1\.     web;
        default         turn;
    }

The nginx error log (on the jitsi vm):

2020/04/24 16:08:38 [error] 1066#1066: *75 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.101.111, server: 0.0.0.0:443, upstream: "127.0.0.1:4445", bytes from/to client:0/0, bytes from/to upstream:0/0

Current behavior

nginx redirects main page and room links to turn server

Expected Behavior

I would like to see the welcome page

Possible Solution

Fix the nginx config

Steps to reproduce

Do a fresh install on debian 10.3

Environment details

Debian 10.3 behind a NAT and web proxy.

client <-- [https] --> web proxy <–[https]–> jitsi vm

[ghost]

The default here seems to be wrong, a lot of HTTP clients don’t supply the ALPN extension. This may be a possible fix although I haven’t tested extensively yet (see RFC7743):

    map $ssl_preread_alpn_protocols $upstream {
        ~\bstun\.turn\b  turn;
        default          web;
    }

[dpoon]

What web proxy are you using, and is it capable of doing ALPN?