Using Let's Encrypt with Jitsi app results in non-functional jitsi proxy config. It looks like the config file for lets encrypt doesn't generate properly. The file, /etc/apache2/sites-enabled/univention-letsencrypt.conf, simply leaves out the proxy config for jitsi in the virtual host generated for jitsi. i.e. I get a virtual host section with the jitsi.domain.com server name, but it's missing the proxy config for jitsi. ProxyPass / http://localhost:8888/ retry=0 ProxyPassReverse / http://localhost:8888/ Adding that proxy config into the file makes jitsi work properly, but I'm not sure why it's left out in the first place or where the fault lies.
Apps that use the vhost feature from bug 45115 are probably incompatible with the current way the letsencrypt app handles the apache2 config. In the apache2 config univention-letsencrypt.conf should be a line IncludeOptional /etc/apache2/ucs-sites.conf.d/*.conf So it may be enough to link the jitsi apache2 config to that directory ln -s /var/lib/univention-appcenter/apps/jitsi/config/vhost.conf /etc/apache2/ucs-sites.conf.d/
In my above comment I got the appid wrong, below is the command with the fixed path. ln -s /var/lib/univention-appcenter/apps/jitsimeet/config/vhost.conf /etc/apache2/ucs-sites.conf.d/
I added a note to the workaround described in this bug to the README of the Jitsi Meet app. As soon as this issue is fixed and released, the Jitsi Meet README file needs to updated, as well.
For me that workaround kills the display of the UCS-Portal.. If I access my server normally, I now just see jitsi. And https://www.*********.de/univention/portal/ Doesnt load properly... Using latest ucs version Do you have the same problem or have any ideas how to solve it?
Tried this workaround after the latest upgrade to Jitsi Meet suggested it, and it broke access to nextcloud. I reverted the fix and restarted apache and nextcloud is working again. I haven't had time to troubleshoot it yet as we use nextcloud for calendars I needed to get it back running quickly.
I ended up putting the contents of /var/lib/univention-appcenter/apps/jitsimeet/config/vhost.conf into the jitsi vhost section of /etc/apache2/sites-enabled/univention-letsencrypt.conf That seems to be working fine at the moment after some basic testing. Not sure if there is a better way to manage these configs for apps in the future. Maybe some sort of default include line that pulls in any needed config into the /etc/apache2/sites-enabled/univention-letsencrypt.conf file at the appropriate applications section. Hopefully someone smarter and more well versed in apache configs can figure out a good process for this so it can be handled easily by the app maintainers and not require any intervention on the part of the admin of a particular UCS install.