Krydos

Here are the three abuse reports that we received about your account. The account fpackham has been unsuspended.

The account trinucc has been unsuspended. @admins/moderators, when an account is suspended for sending too many emails it will already be throttled to 1 email per hour anyways. Once the issue is fixed then we can restore the default email sending limit if needed. @trinucc, my guess is that spambots are creating thousands of accounts on your website, and the emails are just a symptom of the bigger issue. It doesn't matter if you disable email sending or get your email throttled, if you don't do something to prevent the bots from creating accounts eventually they will create so many accounts each day that you will get suspended for high load anyways. Do you really need a login system on your website? Can you disable account creation entirely? If you do need to have a login system for users you should at least add a creative captcha type question that will prevent the bots from creating their accounts.

To change the password of phpmyadmin simply visit http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html , make sure the box labeled "Allow MySQL password change" is checked, and change your password. Let us know if you're having any other issues logging into phpmyadmin, or changing your password.

Account's IP changed.

That might be a specific issue with this particular version of cPanel. We are scheduled to update cPanel again on Stevie fairly soon so we'll see if the next upgrade fixes this issue. If you don't mind could you make a new post in the customer service forum about this code editor highlight thing so we can keep track of its progress?

It's actually not a problem anymore. For a while hotmail decided to block all of Heliohost emails and wouldn't even deliver them to people's junk mail boxes. They have since stopped being so rude as to delete our emails without any reason or warning so we re-enabled people being able to create accounts with us using hotmail addresses. I actually can't see any reason why your account wouldn't create successfully. I even checked the other accounts created on or before the date that you posted your issue in case there was some serverwide issue that was causing all accounts to fail to be created, but that isn't the case either. Could you try creating your account again and let us know how it goes this time?

Dedicated IP granted. Here are some instructions I wrote a while back on how to install ssl on your account once you have a dedicated IP. Steps 7-18 are based on getting a free ssl certificate from comodo, but if you're purchasing your certificate from somewhere else it will be similar.

Cool, thanks for noticing this.

As long as you only compile once or twice a day you won't get suspended. If your run three or more cron jobs in a 24 hour period you could be suspended.

Well, it technically doesn't have to be compiled on Heliohost. In order for this to work the system you are compiling the binary on must be exactly or at least reasonably identical to the server you intend to run the binary on. Since it's not working I'm guessing your compiling system is not close enough. Try compiling it on the server as the wiki instructs and let us know if that works any better for you.

This should now be working again. Let us know if you're still getting the data error issue in file manager, or if you're having any other issues with your account.

Does it work now?

Stevie is currently undergoing a software upgrade, and this issue should resolve itself once that upgrade is complete.

These are your options at this point: Purchase a valid vBulletin license at http://www.vbulletin.com/en/purchases/ I can delete the copyright infringement from your account for you. Leave your account suspended forever. Let us know which option your would prefer.

You just need to run that same process on both Stevie and Johnny and it would have worked. When you run it on Johnny it deletes traces of the old account from Johnny and Cody. When you run it on Stevie it deletes traces from Stevie and Cody. So there was traces still left on Stevie. @law942, you should be able to create your account now on Stevie. Let us know if you're having any other issues.

Dedicated IP granted.

I tested your account and you have permission and show tables command works both in phpmyadmin and in a command line connection. I saw two databases. The one had four tables if I recall correctly, and the other had none. In order to test this as the mysql user pete20r2 I had to change your cPanel account password. Let us know if you're having trouble resetting your password and getting logged back into your account. I also tested your databases using the root mysql account and there was no additional tables or data that wasn't available to your pete20r2 mysql account. I'm going to mark this as solved, but if I am misunderstanding the issue or if you have any other issues please let us know and we can work get everything functional for you.

Yeah, the system normally doesn't suspend for malware in somebody's inbox because it's hardly the account owners fault if someone mails them malware or phishing emails. However, since that was a webmail install the scanner didn't ignore it.

Same as last time. Your account has been suspended for high load three times, and each time most of the load was coming from: /home/ufni/tpb/proxy.php

Here is your account's load for the last week as a rank amongst other accounts on your server. For instance, 4 means there were 3 accounts that caused more load than you, and 1 means that you caused the most amount of load. Larger numbers are better, and mean less chance of you getting suspended. date cpu 2014-04-30 4 2014-04-29 12 2014-04-28 1 194% more load than #2 2014-04-27 1 130% more load than #2 2014-04-26 10 2014-04-25 72 2014-04-24 22

/home1/rax/skmaildb/alex4093_skxawng.lu_mail.skxawng.lu/INBOX/93638e5f492ba7f7fbfc05cd2005b7cf.eml

It's really not that big of a deal for an admin to reset the brute force protection on your account. If it happens again just post here on the forums and the first admin that sees it can get you back to being able to log it. The reason we try to help users figure out what the reason for the brute force is because it's a better, more long term solution to fix the underlying problem than it is to just fix the symptoms over and over. We have literally thousands of user accounts hosted on our servers, and while this brute force protection issue does come up frequently it's highly unlikely there is anything wrong with the servers because if there was we would see hundreds if not thousands of people like you not being able to log in. There is something on your end causing this, and we'll do everything we can to help you figure it out so it doesn't continue happening, or if you can't figure it out we'll just reset it for you each time you need to log in. Let us know how we can help.

Here is a log of the SFTP login attempts that got your blocked for brute force attempt: Apr 25 03:00:30 stevie sshd[7724]: Accepted keyboard-interactive/pam for pew from 217.157.206.10 port 1376 ssh2 Apr 25 03:01:03 stevie sshd[9016]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:01:03 stevie sshd[9015]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:01:13 stevie sshd[10129]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:01:13 stevie sshd[10126]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:01:23 stevie sshd[10531]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:01:23 stevie sshd[10530]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:01:41 stevie sshd[10911]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:02:34 stevie sshd[12700]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:02:38 stevie sshd[13128]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:02:51 stevie sshd[13684]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:07 stevie sshd[14176]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:07 stevie sshd[14177]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:25 stevie sshd[15119]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:25 stevie sshd[15117]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:35 stevie sshd[15417]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:35 stevie sshd[15418]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:45 stevie sshd[15769]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:45 stevie sshd[15780]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:56 stevie sshd[16164]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:03:56 stevie sshd[16165]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:06 stevie sshd[18492]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:07 stevie sshd[18495]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:18 stevie sshd[18941]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:18 stevie sshd[18940]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:28 stevie sshd[19332]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:28 stevie sshd[19333]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:37 stevie sshd[19632]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:37 stevie sshd[19630]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:04:47 stevie sshd[19979]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 03:31:10 stevie sshd[18692]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 25 04:04:52 stevie sshd[9552]: Accepted keyboard-interactive/pam for pew from 217.157.206.10 port 4604 ssh2 Apr 26 02:32:42 stevie sshd[6612]: error: PAM: Authentication failure for pew from 217.157.206.10 Apr 26 02:42:32 stevie sshd[11531]: error: PAM: Authentication failure for pew from 217.157.206.10 As you can see they all originate from your IP, and there are successful password authentications as well as failures. Are you sure you don't have an incorrect password saved in your ftp client? Another option is that there is some malware on your computer. Does a virus scan find anything on any of the systems located at that IP?

This account cannot be unsuspended because it was involved in illegal activity. If it wasn't you that was doing this feel free to create a new account, and make sure you secure your account better against hackers this time around. If it was you that was involved in the illegal activity feel free to find another host. Either way this account cannot be unsuspended.

I haven't actually checked whether tpb stands for thepiratebay in this case because it doesn't really matter. Most likely it does, but the pirate bay is just a tool like any other. Just because it has the word 'pirate' in its name doesn't necessarily mean that the only thing it can be used for is piracy. Just because someone owns a gun doesn't automatically make them a murderer. Just because someone owns a lighter doesn't make them an arsonist. Just because someone visits thepiratebay or any other torrent site doesn't automatically mean they are violating copyright law. If copyright infringement is occurring then that is illegal, and it is against our ToS. That said, proxies do cause ridiculous amounts of load, and they are probably the number one reason why accounts get suspended for high load. The sensitivity for high load suspensions is higher on Stevie (to keep his uptime nice and high), but if you insist on running a proxy you might have better luck moving your account to Johnny where you're less likely to get suspended.