wolstech

Another account in the system that was created about a month ago is responsible for the error. Byron or Krydos need to fix it though. Escalating.

Do you have another account?

You need to tell sourcebans that you have a game server hosted 24.76.231.65 on port 51990. I'm not sure if that's done in the config or through its interface since I don't use it. Wherever you had to enter that 192.168.0.17 and 27015 into sourcebans originally, is where you need to enter the IP and port above.

51990 is open for tcp...I use it for my Minecraft server. Didn't know you needed UDP. Let's see what Krydos says.

What is your account username? Also, if you are on Johnny, you will need to change the database server hostname to 127.0.0.1 since localhost no longer works.

Is there a specific error you're receiving?

As of now, likely several months. It's whenever the new server comes online is when it becomes available. As I said above though, sourcebans does not require it, so there's no reason to wait. Sourcebans' docs say it will run on 5.2 and up (and I've seen others run it on Stevie), so it should be compatible with Stevie's 5.3.8.

You can use either. Self signed one will make your visitors see security warnings though, so you're better off buying it. It's installed in cpanel by copy and pasting the contents of the files if I remember right.

5.6 can run 5.5 software, but you'll be waiting until our new server comes online to get 5.6. And yes, you can go back to Johnny. Same process as before...delete, wait, sign up again, wait again. Your best bet though for performance reasons is to just get an older version of sourcebans if you need to, so you can keep your account on Stevie until the new server becomes available. When that happens, you would move to the new server, then update sourcebans. Also, why do you need 5.4? Sourcebans runs on 5.2 and newer based on the manual, so Stevie is compatible: http://docs.sourcebans.net/guide/2.0/en/installation

We do not support PHP 5.5 at this time. The new server is supposed to have 5.6 whenever it finally comes online, but that may be months. For now, the only versions of PHP you can get here are 5.3.8 on Stevie, or 5.4.41 on Johnny.

Seems to have recovered after ~6 hours of acting up.

Is something wrong with Apache on Johnny? Based on http://heliohost.grd.net.pl/monitor/, something quit around 7AM EDT...load looks good in the mid-1.xx's (numbers from top, cPanel's load meter was blank). cPanel/FTP seem to be working and are actually fast right now though, which is unusual since they normally go down at the same time as, if not before, HTTP does when he bogs down under load.

This support request is being escalated to our root admin.

They likely didn't create any email accounts (most of these spammers use PHP's mail() to send the spam), but to be sure, check in your cPanel mail accounts settings. As for WP, the files are kept in three folders: wp-content, wp-includes, and wp-admin. Remove all 3 folders and their contents to get rid of it. Only other thing to do would be to drop the database. Also, since I missed it earlier: We don't send emails for suspended accounts, only for ones that have gone inactive (and even then, many people have said it these often get sent to spam). Real people who actively use their accounts will see the notice and ask about their suspensions anyway.

Your account has been unsuspended. Please clean up the issue within 24 hours. I'd also recommend you change your cPanel password and the passwords for any other software you have installed on your website.

/usr/bin/php /home/andydunn/public_html/blog/wp-includes/js/gallery63.php It looks like WordPress got hacked. These messages were sent by PHP. Hacked WordPress is probably the #1 cause of a spam suspension here at Heliohost. WP is infamous for it's security issues and the number of "free" themes/extensions that come with backdoors). I would recommend that you delete your entire WordPress site and replace it with another CMS. If you insist on keeping WordPress, avoid themes and extensions from dubious websites (they're "free" because they're supported by the malware/backdoor included them), and keep everything up to date.

Change localhost to 127.0.0.1 For some reason, localhost doesn't point to localhost anymore

I just realized you're on Stevie. The localhost thing is a Johnny problem. You just have an invisible database. Krydos needs to restore it for you. Escalating.

OK...I don't see you listed in the firewall list, but it won't reset in the admin tools either. Escalating.

Stevie is bouncing up and down (probably a DDoS based on the appearance on the monitor). I'll reset your password and email it to you when he comes back online.

It means the cPanel monitor is broken. The database server is working fine. The problem is actually that localhost no longer points to 127.0.0.1 like it should. Change your script's database server to 127.0.0.1 instead of localhost and see if it works. If it does not, check in PHPMyAdmin and verify that the database exists and has content like it should. If it's empty or missing, let me know its name so I can escalate this for you.

You were suspended for inactivity. I've renewed it. Try now. That suspension was probably related to the outage we had and some changes we made during that time, not you. I also was suspended immediately after the outage ended.

Krydos will know for sure whether these are actually issues for us. Let's find out.

We already have an antivirus that is updated and run regularly...people get suspended for shells and similar all the time. As for the kernel issue, I don't recall it ever being updated in the time I've been here. OpenSSL is also old and lacks support for new standards...and everything else on both servers is ancient too. To be honest, I don't think anything we use aside from the AV is current. We don't update because the updates like to break things, especially cPanel. There's also user websites that rely on the older versions of things like PHP. As a result, we use what cP recommends and what is backwards compatible...much of which is not recent.

Mysql is an issue there, but the bottom three are normal. Krydos mentioned elsewhere that the host name for database connections needs to be set to 127.0.0.1 for right now, localhost doesn't work for some reason.