Proper certificates for secondary domains

To avoid login errors or messages and also to avoid certain problems with server-to-server connections we installed proper certificates for the secondary domains today.

We had to restart the Jabber services several times, sorry. The ejabberd config file isn’t commented very good, also Google didn’t tell us the correct settings in the first place. But everything works fine now.

PS: For old SSL connections to port 5223 there are no dynamic certificates. This just isn’t possible because of how SSL works.

Roi

Recent Posts

XMPP Housekeeping now active for openim Domains!

We just activated XMPP Housekeeping for the openim.de and openim.eu domains. These two domains joined…

3 months ago

openim.de

Yesterday we took over the domain openim.de and the XMPP/Jabber users running on it. The…

2 years ago

Upgrade to Prosody 0.12

We upgraded the Jabber server to Prosody 0.12 (from 0.11) yesterday, see the changelog.

2 years ago

Hot-Chilli Matrix server

If anyone is looking for a Matrix server besides matrix.org or matrix.im, please visit us…

3 years ago

Converse.js finally works here

We did a lot of digging into the issues that the browser windows froze when…

3 years ago

New public domain: hot-chilli.im

We just added another public domain to our XMPP/Jabber server: hot-chilli.im For the future we…

3 years ago