Jistsi-Meet / LetsEncrypt behind an nginx proxy

Hello, while setting up an jitsi-meet enviroment, using the docker-jitsi-meet git, I ran into a difficulty with LetsEncrypt.

On my Server runs Plesk Obsidian, with an nginx reverse proxy.
I wrote 2 small location rules to

  1. redirect all ‘normal’ incoming traffic
  2. redirect incoming traffic on .well-known/
    to the container. (Different ports for http and https ofcourse)

When I’m starting the container with ‘docker-compose up’, I’m getting following error:

The following errors were reported by the server:

Domain: meet.[domain].de
Type:   unauthorized
Detail: Invalid response from
http://meet.<domain>.de/.well-known/acme-challenge/KYmSFS36Y8VfsN523Yaw2o9dnb3X2FWRncvMUF53xyk
[IPv6]: 404

I copied the URL and got a 404 page from jetsi:

404 Not Found
You can create new conversation [here]

But why?

Wasn’t able to fix this with the jitsi docker container.
Now my nginx proxy provides the certificate.

Problem is the nginx configuration not providing listen directives for IPv6. Solution is to add these directives alongside the ones for IPv4:

server {
    listen 80;
    listen [::]:80;
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
}

Relevant pull request: https://github.com/jitsi/jitsi-meet/pull/5216

1 Like

Ah, that explains it! Thank you!

1 Like