This will affect Jabber itself and all transport services, and also this website. And it will take place during the next 24 to 48 hours. Please be patient and expect some service outages. We changed the TTL of our DNS zones to 1 minute but nevertheless it could be that your client still looks for the old server. You might need to relogin to the Internet and/or restart your client.
We will be back here when everything is moved. Until then you also can reach us on Twitter, where a link to this post will also be posted.
The Spectrum transport services are down at the moment. It will take one to three days until these services are up again. Mostly because we are about to move all Jabber related services to a new machine. So please stay tuned.
There were some outages in the past weeks.
A big outage was from yesterday to today, almost one day. Coming back just two hours ago. But everything is fine again. We had some server hardware problems which are solved now. No data loss and no need to restore our backups.
The other outages are much harder to detect. There is a annoying bug in Prosody at the moment which causes database connections to fail at some point. Then a restart is needed. We need the information then (because most of the time it only affects users who want to login, not already logged in users) to restart the server. Another bug which is unknown at the moment is that connections to jabber.ccc.de are failing from time to time. A restart solves it – or causes it. You choose… 😉 But these problems are Prosody related (the first for sure, the second maybe) and we work on it.
So we need your help. If you cannot login, tell us. Here or Twitter, does not matter. If you see your buddies from other servers offline at once, tell us. At the moment we just know about this jabber.ccc.de problem which happened two times.
PS: We are not thinking about cancelling our Jabber services here, do not worry! Some people were afraid.
We just upgraded the Jappix web client to 1.1.6 from a older 0.9 version. Have fun! 😉
JWchat is offline, it did not work anymore after we upgraded something on our server a while ago.
We updated our old expired certificates a while ago. And now I just updated the website. You can find the new fingerprints here.
Also we had some problems with certificates, especially on this website. Sometimes the webserver delivered the old and expired certificate. This was because some old tasks of Apache were still in the memory. Problem solved three days ago.
A short time before the old certificates expire we setup some new ones:
hot-chilli.net and im.hot-chilli.net (and also for this website):
Because there are problems/bugs with ejabberd 13.x connecting to our transports we just replaced the certificate for our main virtual host jabber.hot-chilli.net. This host also does service our transports.
Until then we had used a certificate with the common name *.hot-chilli.net, now we have one with jabber.hot-chilli.net and *.jabber.hot-chilli.net common names which does not lead to the problem.
Some days ago we already replaced the *.hot-chilli.net due to the OpenSSL Heartbleed bug.
We upgraded the Jabber server to Prosody 0.9.4 this morning, see the changelog.