Andrzej Wójcik (Tigase) opened 1 year ago
-
This issue was partially fixed by commit c532f16f
In this commit checking of a response from REST API was fixed to not report false positives making failed updates being reported as successful.
Additionally, cron job was allowed to work even if some certificates are missing (ie. not generated yet), while other certificates could be regenerated and required refresh in Tigase XMPP Server.
Moreover, due to bug in CertManager it is now required to not set preferred chain as it may return LE chaing with cross-signed certificates that are not supported by Tigase XMPP Server. This bug was introduced by recent changes done by LE on 8th of February, see https://community.letsencrypt.org/t/cert-manager-le-giving-unwanted-dst-x3-chain-after-feb-8/213476/6 for more details.
-
Previous Value Current Value Open
In Progress
-
Previous Value Current Value In Progress
In QA
-
Wojciech Kapcia (Tigase) moved 10 months ago
Previous Value Current Value Attic/helm-charts
tigase/helm-charts
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
none
|
| Target Release |
1.1
|
| Sprints |
n/a
|
| Customer |
n/a
|
LetsEncrypt certificates are accepted by Tigase XMPP Server and cron jobs are running without any errors, however, certificates within Tigase XMPP Server storage are not being updated.