Wouterr

Got it working by installing the NerdPack (on Community applications). from which i installed PIP with PIP you can then install docker-compose. Then just follow the quick start on https://github.com/jitsi/docker-jitsi-meet and play arround with the .env configuration file. Make sure to set the secrets and passwords to something or the application might not start. Also, Some important settings to change: CONFIG=/mnt/user/appdata/jitsi-meet-cfg DOCKER_HOST_ADDRESS=<your unraid server IP> If you can forward port 80 and 443 to that docker, great, set ENABLE_LETSENCRYPT and you're done. as i have already set-up a nginx reverse proxy in a letsencrypt docker (as set-up to @SpaceInvaderOne totorial) so i could not use the build in functionality. Quik soluition is to join your letsencrypt docker to the jitsi.meet docker network. this can be done trough the terminal with the command docker network connect docker-jitsi-meet_meet.jitsi letsencrypt Where letsencrypt is my letsencrypt docker acting as reverse proxy and docker-jitsi-meet_meet.jitsi is the docker network name as created during docker-compose. Using folowing jitsi.subdomain.conf in the appdata\letsencrypt\nginx\proxy-confs where server_name meet.* point to the subdomain i have configured to serve the jitsi webinterface # https://community.jitsi.org/t/issues-with-using-nginx-on-separate-server/15783/8 server { listen 80; listen 443 ssl; server_name meet.*; location / { ssi on; proxy_pass http://meet.jitsi; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Host $http_host; } # BOSH location /http-bind { proxy_pass http://xmpp.meet.jitsi:5280/http-bind; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Host $http_host; } # xmpp websockets location /xmpp-websocket { proxy_pass http://xmpp.meet.jitsi:5280/xmpp-websocket; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; tcp_nodelay on; } }