Andrzej Wójcik (Tigase) opened 4 years ago
|
|
After further analysis, I've ended up with manual updating of After I've recreated certificates and placed them in the repository, Tigase XMPP Server once again overwritten them and become unusable. I could not connect to the installation with BeagleIM to upload new certificates manually as Tigase XMPP Server complained about "no cipher suites in common". After turning of Tigase, removing self-signed certificates, removing Finally, after uploading the SSL certificate via ad-hoc command Tigase started to be usable once again. I'm not sure what exactly caused this issue, however, SSL certificates which are disappearing and using autogenerating and using self-signed SSL certificates from the database instead of available certificates in the directory is just weird. It would be nice if Tigase XMPP Server would at least mention the issue and allow us to "set" (load from the file) this certificate into the database with some utility (not connecting via XMPP as this may not be available, ie. XMPP client cannot connect or VHost settings do not allow connection with invalid/missing SSL certificate). Either way, that was a very weird behaviour and unexpected one while upgrading fully working and quite up-to-date (updated 3 months ago) installation. @wojtek Please review if this behaviour is correct or "something" happens. It would be nice to have a solution for issues like that. Moreover, how do we now update certificates from Let's Encrypt? Until now I was able to just "merge" SSL certificate files and restart Tigase. What is currently suggested approach now? I'm asking in the context of Kangaroo as it may be using Let's Encrypt certificates quite often... |
|
I've set this issue to priority |
|
After restarting the server I've ended up once again with this error:
|
|
And why it is trying to use self-signed wildcard certificate:
It should use the certificate for |
|
The issue appears after server restart. |
|
It looks like the issue appears (using a wrong SSL certificate, no common ciphers) after server restart and is solved by setting certificate via ad-hoc (ie. with admin web console). |
|
|
|
You are correct that there is something weird going on - I'll investigate. Regarding:
They would be updated either locally from the instance (#issue #817) or externally. In either case, having to "just merge" wouldn't work in how Kangaroo would be deployed and managed (EB could recreate the instance just like that) making filestore simply a no-go hence the whole idea to move certificate store to the database. One question - when you updated the certificate using ad-hoc have you selected "use as default" by any chance? |
|
Yes, I did as I wanted hi-low.eu certificate to be default. |
|
I know, that having SSL certificates on disk is a no-go for Kangaroo but would be useful to have a utility to simply load SSL certificate from file to database (ie. certificate generated by Let’s Encrypt). As utility, I mean a command line tool. |
|
I'm actually quite irritated by current behaviour of Tigase XMPP Server: as it just decided to overwrite my SSL certificate ("valid one") in the database and use a new certificate disconnecting me. It looks like it restarted after a JVM crash:
After automatic restart I've found following lines:
In the database I do have now following entries:
|
|
Apologies for the inconvenience. I've pushed some improvements: made using repository optional (which requires explicit configuration) and made it 'either/or' (enabling repository disables filesystem usage) and added relevant documentation. Please keep in mind that those are nightlies nevertheless and they can contain errors… |
|
Sorry about my latest comment
I had a working and stable server and it stopped working after this upgrade while I considered this version quite stable at this point. The current version still overrides files with a self-signed certificate. I've decided to rollback. |
|
I checked it again and I think I know what happens. I changed one call from |
|
Just checked this new version and now it works without any issues (with the use of files as certificate storage). |
Type |
Bug
|
Priority |
Major
|
Assignee | |
Version |
tigase-server-8.2.0
|
Spent time |
7h 45m
|
After updating my installation
hi-low.eu
with latest build of Tigase XMPP Server (-dist-max
currently latest), I've encountered an issue with SSL certificates.CertificateUtil::getCertificateFingerprint()