We upgraded the Jabber server to Prosody 0.12 (from 0.11) yesterday, see the changelog.
Categories
Category: Downtimes
We did some optimizations in the last few days and also deleted some spammers. It looks like we were successful. The server has no more outages. Hope it stays that way. :-)
Categories
Outage due to attack
Today the Jabber/XMPP services were offline for some hours because of an attack on our server. Sorry for the inconvenience.
Wow, the migration of the offline storage from file to database did take very long. I thought one or two hours are enough. No, the scripts ran for 10 hours. Therefore the Jabber/XMPP services were offline for about 10 hours, from ~10:30 pm CEST yesterday to 8:50 am CEST today. We are very sorry about that. Good news: No more big downtimes are planned in the near future.
We need to convert the Prosody offline storage to the new database format. Therefore we need to take the server down. This will happen at between 10 and 11 pm CEST today.
Categories
Prosody 0.10 up and running
Everything is done, the server runs on Prosody 0.10 and is up for over an hour now. Thanks to MattJ for his help solving the small issues when upgrading.
No new features like MAM and WebSocket are activated, yet. This will follow. But I had to disable mod_privacy_lists and mod_blocking and enable mod_blocklist. This means that we drop support for XEP-0016 which only older clients used nowadays as XEP-0191 is the newer standard which we still support with mod_blocklist.
Categories
Planned upgrade to Prosody 0.10
Prosody 0.10 was finally released yesterday. So today at 8:30 pm CEST (~3 hours from now) we plan to upgrade our Prosody server from 0.9 to 0.10. The XMPP/Jabber services will be offline for about 1 to 2 hours. At least this is our plan. ;-) Please stay tuned!
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.