Unknown opened 3 years ago
|
|
Please take a look at the updated documentation: https://docs.tigase.net/tigase-server/master-snapshot/Administration_Guide/html_chunk/ServerCertificates.html#LetsEncryptCertificate and pay special attention to the chain certificates that you include (especially considering Let's Encrypt's X3 and DST Root CA X3 certificates)! |
|
The updated documentation solved my issues. I had tried both chain certificates in the old documentation, but the new ones worked perfectly. Thank you. |
|
Referenced from commit 1 year ago
|
|
Referenced from commit 1 year ago
|
Describe the bug The SSL/TLS certificate that I put inside of
certs/default.pem
fails to be read, resulting in the following error intigase-console.log
:To Reproduce Steps to reproduce the behavior:
Impact Tigase starts, but certificate defaults to the self-signed one, thus leading to SSL certificate invalid errors on encrypted ports.
Expected behavior the SSL/TLS certificate is read by the Tigase XMPP server and then applied to the relevant vhosts
Screenshots N/A
Details (please complete the following information):
8.0.0-b10083/6923973a
OpenJDK 11
Debian 10 aarch64
Additional context The certificates are generated using Certbot