Krydos

The first thing to try on 500 errors is rename or delete your .htaccess file(s) and see if the page starts working. Let us know if your site continues showing 500 errors even after removing .htaccess.

Users can make and download their own mailing lists backups by following these steps: Go to http://stevie.heliohost.org:2082/frontend/x3/backup/fullbackup.html Choose backup destination, whether or not to receive an email, and click "Generate Backup." Wait until the full backup finished. This can take a few minutes. Once the full backup has finished you can download it via FTP or by clicking the link. Extract or navigate through the compressed file on your home computer. You may need to install the proper program to do this depending on your OS. Mailing list information will be located in backup-3.9.2013_10-11-12_amenti.tar.gz/backup-3.9.2013_10-11-12_amenti/mm/amunaptra_alessandromenti.heliohost.org/ Let us know if you're having any trouble making your own mailing list backups.

Alright, your account has been unsuspended. Please test your scripts before executing them on the server, and you're only allowed to have one active account at a time unless you receive permission first.

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

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

Well, since you've already created 2 other accounts when each user is limited to 1 we'll use this same thread to ask you which 1 account you would like to keep?

http://wiki.helionet.org/Moving_your_account

The account mng4 has only run one cron job so far today. He might be talking about psuedo-cron that a lot of CMSes use. The way those work is each time someone visits their page it checks when the last time the psuedo-cron ran, and if it's over a certain length of time (1 hour, or 3 hours, or whatever) it executes a php cron file in addition to showing the page to the viewer. If no one visits the site for 24 hours then the psuedo-cron has no way of running at all in that time. We don't limit this kind of cron at all, but it can still raise your overall load caused. Also, this type of cron has a tendency to cause load spikes because of so many processes running at once. He could also be talking about an external cron, where every 1 hour or 3 hours or whatever it hits a certain page on his site to trigger the cron run. Once again we don't limit the number of these crons that you run, but they can raise your overall load level. Your sustained load and memory usage look fine for today. However, you could still be causing load spikes that wouldn't show up on the sustained report. Since you mention drupal, I've also noticed that drupal has a tendency to get people suspended for high mysql use. You could see about disabling unnecessary high load queries too if you're worried about getting suspended again.

It's the Heliohost users and everyone you tell about the contest that will be judging the sites. Any sites that are not hosted on Heliohost servers will automatically be disqualified so that sort of evens the playing field as far as page load speed. I imagine if your site does a 60 second mysql query to load each page the people judging your site will probably get annoyed and leave or not vote for you so it is in your best interest to optimize the loading speed of your pages. However, we have no control over who votes for what though.

suPHP is already enabled on both servers. The first brute force ban comes at 5 wrong attempts, and if you continue guessing passwords the length of your ban increases. The details of the number of wrong guesses and length of bans after that is intentionally kept from public knowledge because knowing that would make it easier for criminals to design brute force bots that maximize the number of guesses per day.

Your account was locked by brute force protection because the system detected someone trying to log in over and over with the wrong password. This lock has been removed and you should now be able to log into your account. Try ONCE with your old password. If that doesn't work try resetting your password ONCE. If that doesn't work let us know and we can manually reset your password. Also make sure you delete or update any saved passwords in any ftp clients or any other program that you have that might try to login with the wrong information over and over. Yes, all the admins know how to log into WHM, because they are administrators. Users do not have access to WHM. Finally, do not ever give your password to anyone whether through PM or in any other manner. Doing so gravely compromises your account security and you are responsible for anything your account and anyone who has access to your account does. No true member of the Heliohost staff will ever ask you for your password for any reason. If anyone does ask for your password let us know because they are undoubtedly trying to impersonate a staff member in order to steal accounts.

If you're having trouble changing your NS settings you will need to contact your domain registrar customer support for help. We cannot change those settings for you.

When you change your nameservers don't forget to delete your old ones. http://byrondallas.heliohost.org/php/tools/dns_records.php?domain=BHAGAVATHIASSOCIATES.IN&rec=NS

On February 27th your account caused 158% more load than the second highest account. On February 28th your account was suspended about 7 hours into the day. Even though your account was only active for less than a third of the day your account caused 606% more load than the second highest account. I don't remember the exact numbers (and since it was quite a while ago the logs have been cycled), but your cgi script had something like 300 CPU hours when your account was suspended. As a comparison Apache (the process that sends and receives http protocol from the server) has been running for about 418 hours, and has less than 250 CPU hours. So your one script caused more load in a few short hours than the main process on the webserver does in almost three weeks. All told I'd estimate that your account caused at least an hour of downtime for the several thousand other accounts on your server. Usually when we see this kind of abuse it's because some jerk is trying to crash the server on purpose. I'm surprised you're even asking for your account to be unsuspended. Can you explain any of the above? Can we get any assurances that you won't do any of the above again? What on earth were you even doing or trying to do?

Sorry, I'll wait 24 hours before fixing it next time to better live up to everyone's expectations.

It looks like there was some hiccup during suspension/unsuspension that caused your account to end up partially unsuspended and partially still suspended. I manually suspended and unsuspended it again to sync everything up to the same state, and it looks like it's all working again now. When I first visited your domain it just said database error, now there is a joomla install with contents so I'm assuming there was no data lost. Let us know if anything else is acting weird still.

Go to http://stevie.heliohost.org:2082/frontend/x3/ssl/csrs.html Select your domain from the dropdown box (if you have multiple domains.) Fill out country, state, city, company, company division, email, and passphrase for your business or self, not the server. If some of the fields don't really apply, like company division, just put website or something generic. Click generate and you should get two big boxes with all sorts of random letters and numbers. Copy paste the first box that starts with -----BEGIN CERTIFICATE REQUEST----- Go to whatever website you're purchasing your SSL certificate from. For instance you can do a 90 free SSL certificate from comodo.com as a trial. http://ssl.comodo.com/free-ssl-certificate.php (From here on out I will walk you through setting up a free 90 day certificate from Comodo. Other certificate providers will be similar.) Copy from your cPanel tab the CSR and paste it into the website from --BEGIN CERT to --END CERT. "Select the server software used to generate the CSR" is WHM/cPanel. Fill out the rest of the options, and then click "Next." Now they will want to verify that you own the domain you are trying to set up SSL on. The easiest way is to look at the email addresses they have listed and then verify that they are created with this link http://stevie.heliohost.org:2082/frontend/x3/mail/pops.html If the email address is created and tested select it from the list, and click continue. Now you get to fill out some more information. Some of the fields should be autopopulated from what you typed in earlier. Additional required fields are address, zipcode, etc. If your company has an office use that, otherwise your home address. Fill out all their required information and click next. If there aren't any problems with your data you should no arrive at their terms of use agreement. Click accept (if you accept) and continue to payment information. If you're doing the free trial the total should be $0 otherwise enter payment information to pay for your certificate. Continue to the next steps. Check the email address you selected earlier, and you should receive an email to validate that you own the domain. Type the code into their link. Once you have passed validation they will email you a file called yourdomain.crt to your contact email address that you typed in way up in step 3 (unless you changed it somewhere along the line) not necessarily to the same validation email address that you just used. (From here on the steps should be the same no matter if you're using a free certificate, or which company you purchased from.) Open up http://stevie.heliohost.org:2082/frontend/x3/ssl/crts.html In the email copy from --BEGIN CERT to --END CERT and paste that into the big box labeled "Paste the crt below" then click upload. Now your cPanel has all the required components to setup SSL, but it still hasn't been installed. Go to http://stevie.heliohost.org:2082/frontend/x3/ssl/install.html Once again select your domain from the dropdown box (if you have more than one) and it should auto-populate the three big boxes below with the correct information. I like to manually verify the first few characters of each box to make sure it isn't coming up with weird random data. If everything looks good scroll to the bottom and click "Install certificate." Wait patiently while the SSL is installed. It can take a few minutes. If this is what you already did, or if you follow these steps and the certificate still won't install properly feel free to PM me the .crt, .key, and the .ca text blocks and I can install it for you. If you do decide to send me a PM please make sure you post on this thread letting me know about the PM because otherwise I will never remember to check for new messages. Good luck!

Since you were incapable or refused to reduce the load your site caused on Stevie within the three chances we gave you your account has been moved to Johnny and unsuspended.

Johnny is the experimental server; Stevie is the production server. That's why on the signup page when you created your account it shows the uptimes http://www.heliohost.org/home/signup Stevie is currently at 99.9% uptime, and Johnny is currently at 88.59%. If you would like better uptime just move your account to Stevie using this guide http://wiki.helionet.org/Moving_your_account

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

Dedicated IP granted. Let us know if you have any questions about installing your SSL certificate.

Please post the following information: Your cPanel username Your main domain

Mar 6 13:52:03 johnny crond[30945]: (grb) CMD (cd /home/grb/public_html/test/periodic; php -q cron.php) Mar 6 13:53:03 johnny crond[31793]: (grb) CMD (cd /home/grb/public_html/test/periodic; php -q cron.php) Mar 6 13:54:03 johnny crond[416]: (grb) CMD (cd /home/grb/public_html/test/periodic; php -q cron.php) Mar 6 13:55:04 johnny crond[1250]: (grb) CMD (cd /home/grb/public_html/test/periodic; php -q cron.php) Mar 6 14:01:03 johnny crond[6750]: (grb) CMD (wget -q -O /dev/null http://test.shakeupload.com/ow_cron/run.php) Mar 6 14:02:02 johnny crond[7577]: (grb) CMD (wget -q -O /dev/null http://test.shakeupload.com/ow_cron/run.php) Mar 6 14:03:03 johnny crond[8477]: (grb) CMD (wget -q -O /dev/null http://test.shakeupload.com/ow_cron/run.php) Mar 6 14:04:03 johnny crond[9426]: (grb) CMD (wget -q -O /dev/null http://test.shakeupload.com/ow_cron/run.php) Mar 6 14:05:04 johnny crond[10380]: (grb) CMD (wget -q -O /dev/null http://test.shakeupload.com/ow_cron/run.php) I've used softaculous to install a lot of software, and it's never run a cronjob before.

When an account is queued for deletion it is first suspended. This is normal. If you're super fast, or if deletions are a little slow at the time you can even remove your account from the deletion queue by using the reactivate tool.

The recommended way to make sure your logins are counted and account doesn't get suspended for inactivity is by visiting http://heliohost.org/ typing in your username and password.