docker + nginx reverse proxy

[y4my4my4m]

I'd like to use it with nginx reverse proxy instead of haproxy.
Also I don't want to install it on the server but do everything via the docker

server {
    listen 80;
    server_name MYSITE
    return 301 https://$host$request_uri; # Redirect all HTTP requests to HTTPS
}

server {
    listen 443 ssl;
    server_name MYSITE

    ssl_certificate /etc/letsencrypt/live/MYSITE/fullchain.pem; # Path to your Let's Encrypt fullchain.pem
    ssl_certificate_key /etc/letsencrypt/live/MYSITE/privkey.pem; # Path to your Let's Encrypt privkey.pem

    location / {
        proxy_pass http://127.0.0.1:8080; # Pointing to the first plugNmeet-server IP as an example
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

    }

}

However, i get this error:

Error
Error: could not establish signal connection: room connection has timed out (signal)

Am I missing configurations?
I've confirmed that the required ports are opened...

I've also tried changing:
/pkg/controller/auth_token.go

to

livekitHost := strings.Replace(config.AppCnf.LivekitInfo.Host, "host.docker.internal", "MYSITE", 1) // without this you won't be able to connect

to no avail...

Any help?

[jibon57]

The error you mentioned related with livekit. Your browser can't established connection with livekit properly. I ain't sure if nginx support tcp pass-through or not. If not then nginx can't be use in this case.

[y4my4my4m]

@jibon57 can't i direct to IP connect? or does it need SSL ?

[jibon57]

As this isn't an issue, I moved to discussions.
Yes, for production environment SSL is must.