Jouk
The server has a signed cert, I got from the university. So not self-signed. The server does not use a proxy, but maybe does internally using docker, but that worked...
I just started Jitsi on the server. https://vleegert.nano.tdelft.nl:8443 Please let me know when you are finished, so that I can shut it down again.
oops should be https://vleegert.nano.tudelft.nl:8443
had to shut down the server. please cotact me off-line or by phone (office hours 31-15-2782272
I upgraded to 7648-4, but th did not help. It is now running again. But be aware that this is my "test" machine. So it is rebooted often and than...
The configuration file for this server is just the example + generated passwords and the following 2 lines added: PUBLIC_URL=https://vleegert.nano.tudelft.nl:8443 DOCKER_HOST_ADDRESS=131.180.116.49
[prosody.log](https://github.com/jitsi/docker-jitsi-meet/files/9452615/prosody.log) Attached the prosody log. I added the ENABLE_XMPP_WEBSOCKET=0 and restarted. Soem difference but I still cannot join a meeting. What do you mean by non-standard port, since I thought...
Strange I run docker-compose always as root for over 2 years now. The /.jitsi-meet-cfg is in the /root folder and owned by root
When running docker-compose as a "normal" user, I only see black screen when accessing the serve. I see that some files in .jitsi-meet-c are created by root. Probably because docker...
I created a fresh jitsi-meet-cfg in my home directy. I saw that i.e. the certs generated by defaultt are owned by root after startup with dovcker-compose (runned as myself) Is...