SSL Lets encrypt install problem

I enabled lets encrypt in config file, after docker-compose up command this errors are appering

prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for focus.meet.jitsi)
prosody_1 | focus.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Previous error (see logs), or other system error. (for focus.meet.jitsi)
prosody_1 | focus.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (system lib)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Previous error (see logs), or other system error. (for focus.meet.jitsi)
prosody_1 | focus.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (system lib)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for internal-muc.meet.jitsi)
prosody_1 | internal-muc.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Previous error (see logs), or other system error. (for internal-muc.meet.jitsi)
prosody_1 | internal-muc.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (system lib)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Previous error (see logs), or other system error. (for internal-muc.meet.jitsi)
prosody_1 | internal-muc.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (system lib)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for muc.meet.jitsi)
prosody_1 | muc.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for muc.meet.jitsi)
prosody_1 | muc.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for muc.meet.jitsi)
prosody_1 | muc.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)
prosody_1 | portmanager info Activated service ‘c2s’ on [::]:5222, []:5222
prosody_1 | portmanager info Activated service ‘legacy_ssl’ on no ports
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for recorder.meet.jitsi)
prosody_1 | recorder.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for recorder.meet.jitsi)
prosody_1 | recorder.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for recorder.meet.jitsi)
prosody_1 | recorder.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for meet.jitsi)
prosody_1 | meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for meet.jitsi)
prosody_1 | meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/meet.jitsi.key’: Check that the path is correct, and the file exists. (for meet.jitsi)
prosody_1 | meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)
prosody_1 | portmanager info Activated service ‘http’ on [::]:5280, [
]:5280
prosody_1 | portmanager info Activated service ‘https’ on no ports
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/auth.meet.jitsi.key’: Check that the path is correct, and the file exists. (for auth.meet.jitsi)
prosody_1 | auth.meet.jitsi:tls error Error creating context for c2s: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/auth.meet.jitsi.key’: Check that the path is correct, and the file exists. (for auth.meet.jitsi)
prosody_1 | auth.meet.jitsi:tls error Error creating contexts for s2sout: error loading private key (No such file or directory)
prosody_1 | certmanager error SSL/TLS: Failed to load ‘/config/certs/auth.meet.jitsi.key’: Check that the path is correct, and the file exists. (for auth.meet.jitsi)
prosody_1 | auth.meet.jitsi:tls error Error creating contexts for s2sin: error loading private key (No such file or directory)

hey there

same problem here using docker-compose.
did you fix this on your site?

same here…

same problem here. Running locally on windows. Built using the makefile and force rebuild flag. Also did docker-compose down -v to remove existing volumes and then docker-compose up --force

if you are able to issue trusted certificates, you can place them in the /config/keys folder and you wouldnt need to use lets encrypt.