is that when I try to go to my meeting URL i get a CLoudFlare 522 Connection Timeout Error. My problem to date, after going through this setup, and before that the setup for LetsEncrypt - because I didn't have it yet - and connecting to cloudflare, etc. Currently this recording supports only upto 1GB (approximately 100 minutes). Implementing and using this feature will be discussed in this blog article. This allows any user to record the meeting to local storage. I'm worried, because I do not see this record at all in the ENV section. Apart from the jitsi default recording, jitsi has introduced a local recording feature. Is there any easy way to edit the DOCKER_HOST_ADDRESS? I tried to recreate those steps in the video to to edit this file and when i type nano env.example it seems to come up with a blank dock. I just restarted the jitsi containers and now cant access it at all other than internally file in the env section the DOCKER_HOST_ADDRESS is incorrect because of my fat fingers (its not my unraid server ip) env file and add the host container I think I typed it wrong as when I look in portainer under the
JITSI RECORDING HOW TO
In the part of the video where it shows you how to edit the. Ok think i may have found the issue but unsure But if I remember it right, the Letsencrypt container has to be added to the jitsi docker-network each time the Letsencrpyt container restarts, correct? I seem to recall that the docker cointainers are only able to save one network. Thanks for sharing your thoughts, it seems to work so far. Proxy_set_header X-Forwarded-For $remote_addr Where server_name meet.* point to the subdomain i have configured to serve the jitsi webinterface Using folowing in the appdata\letsencrypt\nginx\proxy-confs 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. this can be done trough the terminal with the commandĭocker network connect docker-jitsi-meet_meet.jitsi letsencrypt Quik soluition is to join your letsencrypt docker to the et docker network. as i have already set-up a nginx reverse proxy in a letsencrypt docker (as set-up to so i could not use the build in functionality. If you can forward port 80 and 443 to that docker, great, set ENABLE_LETSENCRYPT and you're done.
Make sure to set the secrets and passwords to something or the application might not start.
Then just follow the quick start on and play arround with the.
JITSI RECORDING INSTALL
With PIP you can then install docker-compose. Got it working by installing the NerdPack (on Community applications).
0 kommentar(er)
