I’ve just installed jitsi-meet on Debian buster. I had already created a LetsEncrypt cert for my subdomain. I selected “I want to install my own certificate” and entered the paths for key and cert. Unfortunately I entered fullchain.pem for both. I should have entered privkey.pem for the key path.
I then set up prosody authorisation according to the secure domain document.
When I go to the URL, I get the Jitsi Meet page with meeting name and Start Meeting button. I don’t get any prompt to join as the user with the right to start a meeting, and if I click on Start Meeting I get the “You have been disconnected” loop. I can post the browser console error log if needed.
I’d like to reconfigure the relevant Jitsi components and re-enter the correct private key path. I tried dpkg-reconfigure jitsi-meet-web-config
but that just lets me accept “I want to install my own certificate” again and tells me to execute /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh.
That script looks like it will create a new LetsEncrypt certificate, and also crontabs a renew job. I already have the certificate and a different cron job that renews all my certs.
I ran apt reinstall jitsi-meet but it didn’t give me a config dialogue.
I ran dpkg-reconfigure jitsi-meet and it returned with no output.
I could extract and run the relevant parts of install-letsencrypt-cert.sh but that might be dangerous. Is there a correct way to reconfigure certificate paths?