Prosody Error

Mar 24 15:13:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for beb-hup-jm01.hup-bau.int)
Mar 24 15:13:03 beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 15:13:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for jitsi-videobridge.beb-hup-jm01.hup-bau.int)
Mar 24 15:13:03 jitsi-videobridge.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (No such file or directory)
Mar 24 15:13:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for jitsi-videobridge.beb-hup-jm01.hup-bau.int)
Mar 24 15:13:03 jitsi-videobridge.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 15:13:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for conference.beb-hup-jm01.hup-bau.int)
Mar 24 15:13:03 conference.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 15:13:03 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for conference.beb-hup-jm01.hup-bau.int)
Mar 24 15:13:03 conference.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (No such file or directory)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for focus.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 focus.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (No such file or directory)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for focus.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 focus.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/auth.BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for auth.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 auth.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/auth.BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for auth.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 auth.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (No such file or directory)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for jitsi-videobridge.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 jitsi-videobridge.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (No such file or directory)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for jitsi-videobridge.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 jitsi-videobridge.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Previous error (see logs), or other system error. (for conference.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 conference.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (system lib)
Mar 24 17:23:11 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for conference.beb-hup-jm01.hup-bau.int)
Mar 24 17:23:11 conference.beb-hup-jm01.hup-bau.int:tls error Unable to initialize TLS: error loading private key (No such file or directory)
Mar 24 17:27:30 certmanager error SSL/TLS: Failed to load ‘/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key’: Check that the path is correct, and the file exists. (for focus.beb-hup-jm01.hup-bau.int)

Prosody gets this error and i cant start a Videomeeting everytime i try comes this the whole time

Double check that the certificates exist at /etc/prosody/certs/

If your hostname is beb-hup-jm01.hup-bau.int then i would have expected the certificates to use non-capital letters as well.

Example: I would have expected that this file:
/etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key
is actually named
/etc/prosody/certs/beb-hup-jm01.hup-bau.int.key

It is possibly a configuration error that you entered the hostname with capital letters during installation of jitsi-meet.

Hi, the Hostname was configured during the jitsi meet install also with capital letters and the certifcate is also named with capital letters
in the etc/prosody/certs are the certificate the key and auth.key and auth.crt files also all with capital letter but the files are marked red and wenn one try to open them it say the tey are not existing…

the red color indicate a broken “symlink”
if you type
ls -la /etc/prosody/certs/BEB-HUP-JM01.hup-bau.int.key

then you can see where the link points.
check that the file exist where the link point

1 Like

ok i will check

behind the links was nothing so i put the certs in the folder now i have this

Have you tried this:

sudo chown prosody:prosody -R /var/lib/prosody/
sudo service prosody restart

If you have regenerated the certificates its likely that they are assigned to the root and not to the prosody user.