Krydos

Your account is showing up as clean now. Thank you for taking care of this.

That username and/or domain is not located on our system. Most likely it was deleted due to inactivity. Feel free to create a new account and restore any backup data you may have, because Heliohost does not keep any backups of your data once your account has been deleted. We apologize for the inconvenience, but we have to automatically delete inactive accounts to make room for users who are still active otherwise our servers would soon be overloaded. To prevent this from happening again in the future don't forget to log into your account at least once every 30 days.

I'm guessing your site was affected by the first reason in my list: Exceeding the process limit. FTP clients with the default settings generally try to get files uploaded and downloaded in the absolute fastest way possible. Those are the settings that we were testing to fix the firewall. The way FTP clients do this is by running as many concurrent FTP threads connected as many concurrent FTP connections as they can. Each FTP connection to the server uses on of your limited number of processes available. The reason we have to limit the number of processes is because if we didn't or if the limit was higher (as it is on Johnny) then one user would either maliciously or unintentionally be able to cause slow performance or downtime for all the other accounts on the server. If your site shows a 500 error, log out of cpanel, close all FTP clients, shut down your email clients, etc. and it should clear up on it's own in a few minutes.

Your account does not appear to be afflicted with brute force protection, but I agree with Shinryuu that you probably did have it at one point and then it cleared on it's own with time. Are you able to log into your account now, or reset the password? Keep in mind that if you are unable to log into your account you shouldn't continue guessing passwords because that just locks you out of your account for longer. If you are still unable to log in, and password resets still aren't working either let us know so we can do a manual password reset for you.

SMTP on Stevie is working fine for me. Have you tried using the SSL settings on port 465 and url stevie.heliohost.org instead of port 25 and mail.yourdomain.com? If it's still not working for you you could provide your username and domain so we can take a look specifically at your account and your settings.

Since we made some progress on your other struts application, and you posted a deploy request for catechesi not webcat I'm going to mark this as solved. Please create a new topic if you do decide to switch back to webcat again.

You could try making a new .war with an absolute reference to the default.css such as infopar.heliohost.org/css/default.css. I'm not sure why it's not finding the .css file.

Ok, GLaDOS was able to help me test this out, and I made some changes to the firewall. It seems to be working better now. Let us know if anyone is still having issues getting disconnected/banned during the middle of an FTP transfer. Are you able to connect again?

Please post the following information: Your cPanel username Your main domain Your queued subdomain The server that you are on

Alright, I've never been able to duplicate this, but a lot of people have reported the same thing happening to them. Since I can never get it to ban any of my test computers I am assuming it has something to do with the network or ISP that people connect with in addition to their FTP client, etc. If anyone is willing to be my guinea pig to test this out please let me know. Basically I would just want you to download or upload a ton of files or whatever it is that causes the bans to happen, and I will watch the log files to see if we can finally get this solved once and for all.

I made some changes to the way the server deploys your old catechesi java application http://infopar.heliohost.org/ which now does more than just show a 404 error. Let me know if you still want to go ahead with the new deployment. I thought it might provide some useful troubleshooting information for you to see this first.

I've been trying different server settings for deploying your catechesi application, and I came up with http://infopar.heliohost.org/ that seems to do more than just a 404 error.

Date CPU MEM ------------------ 2013-05-03 3 1 2013-05-02 1 1 2013-05-01 1 1 2013-04-30 3 2 2013-04-29 5 1 2013-04-28 2 1 2013-04-27 5 1 1=highest cpu/mem, 2=second highest etc. Also this list doesn't take into consideration suspended accounts. Perhaps your account was second highest load, but the highest load account was suspended in which case you should really be a 1 not a 2. I posted this link for another account recently that was using a lot of memory in php scripts. Perhaps you will also find it useful http://v1.srcnix.com/2010/02/10/7-tips-to-prevent-php-running-out-of-memory/

Reading through the logs it looks like Java was enabled on your account on April 9th, and then on April 21st it was removed for abuse. Java can only be enabled on a limited number of accounts at once, and each account that it is enabled on increases the system resources that tomcat uses. Your account was using the same resources as roughly 20 normal accounts, so it was automatically removed. You can request java again http://www.helionet.org/index/forum/74-java-requests/ if you would like, and we can give you another chance.

Since you still seem to be using a lot of memory I thought this link might be useful to you http://v1.srcnix.com/2010/02/10/7-tips-to-prevent-php-running-out-of-memory/

To prove ownership of a Helionet account prior to deletion you must be able to accept and reply to an email sent to the address that you registered the account with. Failure to reply to the deletion verification email means that the account will not be deleted. Once a reply is received the account will be deleted.

Your password has been manually reset, tested, and emailed to your contact email address. Let us know if you're still having trouble accessing your account.

It looks like your changes might have helped, or your coincidentally received a lot less traffic today, but either way your account is now 8th highest load and 2nd highest memory usage over the past 17 hours.

Correct. I have removed the brute force protection from this account. Try logging in once. Let us know if you're still having trouble logging in, and for future reference our system is pretty brutal when it detects someone guessing passwords.

Also make sure your .war is in your home directory such as /home/<username>/MyProject.war

Your request might also benefit from reading the forum rules too. Particularly http://www.helionet.org/index/topic/1544-the-official-etiquette-guide/

Well, if you haven't uploaded any files yet the upload limit is 500 MB. If you've uploaded 25 MB then your upload limit is 475 MB. If you win the website contest http://heliohost.org/home/website-contest that ends tonight then your limit would be 1000 MB.

Log into http://dot.tk/ select custom dns, and set the nameservers to ns1.heliohost.org and ns2.heliohost.org. Once this is done you should be able to park that domain on your account. Let us know if you encounter any other errors adding that domain.

Your account was resuspended for failure to take care of the malware problem during your allotted 24 hour period. The offending files have been deleted, and your account has been manually unsuspended. If you still see the suspended page then you should try clearing your browsers cache. You've been suspended for malware quite a few times. You should probably scan your files before you upload them, or if it's not you that's uploading these files you should probably put some effort into stopping whoever is uploading them. If you need help figuring out how to do any of that just let us know and we can try to help you.

It's interesting that you came here to ask this. Currently your account is the second highest load account on your server, and you are the highest memory usage account. What that means is when one of your users are active on your site your account causes the whole server load to spike up. When the load spikes up mysql, which is very sensitive to high load, slows down considerably. The slower mysql processes your queries the higher chance you have of seeing an error due to maximum connections. The solution to all of this is to make changes to your site to reduce the load it causes. If you use less memory, and less cpu it will reduce the chances of your account being suspended. As a nice side effect you should also see mysql connection limit errors drop too. You're in the unique situation of being able to solve your own problems here. The reason I say it's interesting that you came here to ask this is because the only reliable way we have of letting users know that they are causing problems on the server is to suspend their account. You've essentially saved yourself some potential downtime by coming here to ask this rather than waiting for your account to be suspended.