As I announced on XMPP a server switch was happening. I decided to do this because the old i3D server was too costly and for some odd reason it took 5 minutes for the server to come back up after every reboot. All data has been transferred over and we are now running on a LeaseWeb VPS with these specifications:

This should be more than enough as Prosody is very efficient and uses minimal resources. Also instead of the server hosting both the site and Prosody I have used SRV DNS records to allow the site to be hosted somewhere else while forwarding all XMPP queries to prosody.xmpp.is (port 5222 & 5269). This is much better because if the XMPP server goes down, updates can be posted on the site where there is no downtime. For fun here is the SRV records I used:

_xmpp-client._tcp.xmpp.is. 3600 IN SRV 10 5 5222 prosody.xmpp.is.
_xmpp-server._tcp.xmpp.is. 3600 IN SRV 10 5 5269 prosody.xmpp.is.

I also apologize very much for the downtime, I had a bit of trouble setting this up. But now that all is better, get back to chatting! 🙂

So while using CryptoStorm VPN I noticed that I would randomly disconnect anywhere from 5-30 minutes from XMPP servers including but not limited to XMPP.is. I have tested this with several other services and it happens on all of them while using CryptoStorm. In my case this has happened on their German, Iceland and US nodes. I am going to tell CryptoStorm about this, and from what I have noticed it only affects XMPP connections. Strange isn’t it?

So if you’re using CryptoStorm and you disconnect a lot, it is not our fault 🙂

Edit: CryptoStorm is aware of the issue and it has been ongoing.

@cryptoworld_is …to open a forum thread explaining how folks can help pin down exact params where it's observed – so we can fix it. Stat.

— ‍ ‍‍‍ᓭ cryptostorm ᓯ (@cryptostorm_is) July 21, 2015

So if you were connected about 10-12 hours ago there was a problem with the dedicated server and it went down. According to i3D, the server shut itself off because of overheating in the rack. This is the response I received from them just now. Sorry about that, but apparently it shouldn’t be happening again.

An announcement feature has been added to the Prosody config, you might have gotten a message yesterday saying the server will be rebooted (that was it). From now on when I’m going to reboot the server or there is an important announcement to make I will send it through there to notify all online users.

So I have decided to disable logs all together except error logs. I have also wiped the existing logs using the “wipe” command. Logs now direct to /dev/null and no information about users besides hashed passwords and offline messages are stored. You can view the new configuration file fully at xmpp.is/prosody.txt

I hope you are enjoying XMPP.is 😀