http-bind responses with 404 (unknown host)

Hi there.

I installed Jitsi-Meet on a server behind a NAT firewall. The publicIP:443 is translated to an nginx reverse proxy, who directs everything with the public jitsi hostname to the local jitsi nginx. I double checked the http routing. UDP10000 is translated directly to Jitsi.

I can access the URL in the app or in the webinterface and I am prompted for a conference name. If I enter a conference, the message “connection interrupted” appears. The logs show me that there are requests to http-bind: "POST /http-bind?room=conftest HTTP/2.0" 404 393 "-" "okhttp/3.12.1"

If I access the http-bind page, I get the message: `404 Not Found

Whatever you were looking for is not here. It’s behind you.

Unknown host: 192.168.5.70`

This IP is the local IP of the jitsi server. How can I fix it? Whom asks http-bind to get an answer? And what should be the desired output? AFAIK is this a reponse of the prosody service, but cannot find any hints for this issue in its log.

[xentity]

@saghul Damn it… the scales fell from my eyes. Solved it.

Jitsi expects to be called with the public/known host header:

        location / {
                proxy_pass https://192.168.5.70/;
                proxy_set_header X-Forwarded-For \$remote_addr;
                proxy_set_header Host $host;
        }

Now, nginx is copying the ctx.domain.de host header into the request to the upstream/jitsi server. Nice.

[xentity]

Of course:

server {
        listen 443 ssl http2;
        server_name ctx.domain.de;
        server_tokens off;

        proxy_headers_hash_max_size 1024;

        #resolver                  192.168.5.1 valid=300s;
        #resolver_timeout          10s;

        ssl    on;
        ssl_protocols TLSv1.2 TLSv1.3;
        ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
        ssl_prefer_server_ciphers on;
        ssl_session_cache shared:SSL:10m;
        ssl_dhparam /etc/ssl/certs/dhparam.pem;

        ssl_certificate /etc/letsencrypt/live/ctx.domain.de/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/ctx.domain.de/privkey.pem;

        client_max_body_size 100M;

        location /_matrix {
                proxy_pass http://192.168.5.70:8008;
                proxy_set_header X-Forwarded-For \$remote_addr;
        }

        location /riot {
                index index.php index.html;
                root /var/www/riot/;
        }

        location / {
                proxy_pass https://192.168.5.70/;
                proxy_set_header X-Forwarded-For \$remote_addr;
        }
}