Category Archives: Downtimes

Unexpected downtime Feb. 28th

The host this service is running on hasn’t been reachable since around 4pm today. The hoster has been informed and we hope it will be available again soon. Thanks again for your patience.

Update: The machine is back up. The service wasn’t reachable for around two hours. According to our hoster it was caused by a power outage.

Unexpected downtime Feb. 19th at 3am

Last night we experienced an unexpected crash of Prosody. The service wasn’t available for about two hours from 3am. Unfortunately the Prosody team couldn’t find the cause yet which is why we are going to restart the deamon in debug mode tonight. That will hopefully give us more information in case it happens again. The expected downtime is less than a minute.

Update: The issue has been identified and a fix is being worked on.

Planned downtime on Saturday, August 29 (Server Migration)

On Saturday, August 29 between 11:00 pm and 12:00 midnight (CEST) we will switch from ejabberd to Prosody.
We are also upgrading the host system from Debian Etch to Debian Lenny.

During this window, the domains, and wonÔÇÖt be available.

If you have any questions or encounter problems after the migration process
please join our support channel.

Update: Please login using your username in lowercase. Fixed, thanks Tobias Markmann.


Our hoster just informed us of problems within their network. They are working on it and are expecting it to be working again by the end of the day.

We are deeply sorry for the inconvenience.

Update 1: Thursday, April 16th will be known as the day of bad luck. While the network was working pretty fast again (thanks for that) our HDD died. We are in the process of restoring the data. Please be aware that restarts may occure until restoration is completed.

Update 2: Transports for are up and running again. You may need to re-register your transport account. Your contacts etc. are of course still there.

Notice: You may want to check if you need personal assistance, if no operator is around, just leave a comment.

Update 3: Fixed a bug where under certain circumstances S2S connections couldn’t be established.

Certificate revoked

Yesterday our certificate signed by the XMPP Intermediate Certification Authority was revoked.
Supposingly it was ‘misused’ as a https certificate in order to secure the ejabberd administrationpanel as well as web-access to several MUCs. StartCom told us that wildcard-certificates issued by the XMPP ICA are not ment for (public) https usage.

This information is contrary to what is published in the Certificate Issuance HOWTO, which is based on the StartCom policy in this regard.

For the domain, provide the DNS hostname of the XMPP server. For example, if your organization is called “” but your XMPP server is hosted at “”, type “im” in the first box at the StartCom interface, type “example” in the second box, and select “com” from the dropdown list at the end of the “Domain: xmpp:” line. You can also request a wildcard certificate such as * (type “*” in the first box, type “example” in the second box, and select “com” from the dropdown list). A wildcard domain enables you to use the same certificate for multiple components (e.g., “” as well as “”). You can even use a wildcard certificate for a domain such as “”. NOTE: if your top-level domain is not available in the dropdown list, please send email to <>.

This morning we applied for new certificates and are awaiting approval. We are sorry for the inconvenience and will update you once the certificates have been exchanged.

Update: The certificates have been exchanged successfully. Have a nice stay!