Archive for the ‘ IRC ’ Category

Services Update!

Pretty much about time I did an update to the services, which I did. We’re now running the latest services released and one of the more important modules was updated as well, so I went ahead with the update. It took a bit longer to do since I had to re-configure the configuration file in case there were any new options.

Anyway, with that out of the way, the services are running stable, have had no problems at all, and everything is back up and running. The IRC server itself never went down. The only time that will happen is when the IRCd needs an upgrade, which I will post ahead of time before I get that far.

Have fun!

Server Update

This isn’t a big update (unlike the one that will be coming soon), but I took the server down yesterday for about 20 or so minutes to update IRC server itself. Compiling decided to take it’s time, so it took a bit longer than I wanted.

The server has been up for a while now, so no real issues going on or anything like that. The next update I’ll probably be waiting a while for. The next update for the IRCd server itself might not happen for a few months, along with the services themselves. This is to ensure that the features that I find more useful work properly before I put it live. Especially the fantasy commands, since that’s a big one for me.

I’ll provide further details when the two programs are near-release or are released.

SSL Support!

Yes! It’s finally here! After much, much pondering and thought about what’s going on with the SSL support on the server, I finally figured it out. Apparently, it was all an error on my part and I never realized it. How dumb of me… lol……… Mk, ’nuff of that.

I have updated the MOTD to include the SSL ports that are available for use for everyone. Both 6697 and 9999 are available for users to use for SSL connections. I bet it’s about time since I’ve been talking about it quite a bit lately, but hey, it’s finally available! Also, I will think about enabling a module for SSL-only channels (via channel mode +z), but that’s something to ponder over. Quite honestly, I don’t think there’d be much use for it. But if need be, I’ll enable it and see how it goes.

If anyone has questions, please join #help and we’ll see what we can help with. To connect via SSL, you may use /server +6697 to connect.

New Provider

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 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 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.

Server Upgrade

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.

Server Issues

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.