ShadowHime

Yep, that’s right. It’s about time too, since Sh3lls is not pleasing me right now with the high ping and such.

The current server will remain for 1 more month before it will no longer be accessible. However, I will, hopefully, have the domain from shadowhime.net pointed towards the new server in due time. I am using about a 2 week period to test the server first. You may access the new server at irc.shadowrequiem.net for the time being. That domain will also serve as our round robin DNS (more information to come once we link to another server at some point) in case we link to other servers.

The old server, again, will hang around for a bit longer. That is, unless Sh3lls want to be idiots and cancel my account before the renewal. By then, I’d be angry… I will make another follow-up post to let everyone know of any further changes. All nicknames (currently in the NickServ Database, and other *Serv’s) will be preserved, and the same goes for channels, and any requested vHosts and BotServ bots. The “noexpire” option has been enabled on the new server and will last for two months from this exact post. This means that your nickname and channel will not expire so that everyone has a chance to get situated on the new server. Once the two months are up, we will go back to our old ways again.

I thank you for your patience, and apologize for any inconvenience this may cause.

Yeah, somewhat continuing a previous post I made here. The current provider, Sh3lls, is giving me some issues such as high ping and frequent disconnects. Not good, is it? So here’s the thing, depending on what happens (and whether or not I can actually afford something of what I’m planning), we’re probably going to switch to a new provider with a new twist. It’s possible we’ll stick with one server, but if we’re lucky enough, we might be able to get two IRCd’s running to link servers. In other words, one will be the main server “Yukina”, and the other is a backup that has yet to be named. The talk is still going around, and we haven’t made a full decision. One thing is for sure, if things keep up the way they have been, we will be switching soon. I will try and make it as painless as possible for everyone, at least so that we won’t get too many problems during the transition.

‘Till then, be sure to read any comments as that is where I’ll post some updates.

Getting SSL enabled on the server is a pain sometimes, but it’s still not quite available… yet.

I ran into some odd errors while trying to get it enabled and I’m not very happy at the moment. So, I might get the server changed to a new host where I should have less problems getting SSL enabled.

If I do change servers, everything will remain the same, I will transfer all of the current data so none of you will lose your nicknames and such. Same goes for the bot configurations. The domain will remain the same, I just have to ask the provider of the domain to update the A Record to point to it.

I’ll post any other updates as I get them.

Quick Update
Just so anyone knows, please see the comments for this post for further updates. It will explain why the server is currently offline.

For anyone that was trying to connect to the server at around 10:30 PM Central Time (UTC -6), I took down the server to upgrade to the latest stable release. Now that the upgrade is complete, it’s now back up and running stable. Don’t worry, all of the data is fine and there is nothing to worry about.

Soon enough, however, I hope to have SSL enabled on the server. I’ll see about working with the hosting provider about it, but I make no guarantees at the moment, but I do hope to get it working.

I don’t know why, but for some reason the host for the server killed the processes and did something on the server. I’ll be doing on and off reconfiguring, but I’ll try and keep it up as much as I can without having to restart it or anything.

All of your nicknames, if registered, should still work just fine. However, for some reason, the vHosts and BotServ Bots are all reset, and those, there are none anymore. For any user that had a vHost, you will have to request a new one if you wish to have one. If you had a bot for your channel, you will need to request it again as they were all wiped out for some reason. (including one of our private bots)

I apologize for any inconvenience this has caused, but it was beyond my control to do anything much about it. I’ll continue to work until everything is pretty much done and the work-load calms down enough. I’ll be taking breaks often as well for the next few days as I figure out what’s going on.

Just thought I’d let everyone know that I’ve got a port scanner going for the IRC. Basically, what this will do is scan your IP for any sort of proxy being used when you connect. If nothing is found, you will be fine and allowed to connect. Where-as, if you are indeed found with a proxy, you will be KLINED from the server for 5 days, no questions asked.

This is your first and final warning. I will update the Information page with the relevant information, as I do not, and will not, allow proxies to be used to connect to the IRC server.