Jump to content

Krydos

Chief Executive Officer
  • Posts

    24,608
  • Joined

  • Last visited

  • Days Won

    871

Everything posted by Krydos

  1. Please post the following information: Your cPanel username Your main domain The server that you are on
  2. /home1/malayale/wp-conf.php
  3. Your account is showing up as clean now. Thank you for taking care of this.
  4. The account 'nemra1' was created on on Johnny on February 9th at 22:25 PST. If you were trying to move your account to Stevie and based on the dates on this post http://www.helionet.org/index/topic/15136-solved-activ-my-account-pls/ it looks like your deleted your account, and then created your account again on the same server, Johnny. Johnny isn't down 80% of the day; the uptime on Johnny is currently 87.61% which by the process of subtraction means that it's down about 12.39% of the day which is mostly in the middle of the night during daily maintenance. If you would like to move your account to Stevie you won't make any progress by deleting your account and creating it again on Johnny over and over. So I'll make it a little easier for you. Delete your account http://www.heliohost.org/home/support/scripts/delete Create your account http://www.heliohost.org/home/create-stevie-account If step two says the daily signup limit as already been reached use http://krydos.tk/sign-up.php to know when to try again. Finally, everyone, myself included, is having a lot of trouble understanding what you're trying to say and/or ask. If English isn't your first language that's fine, but you might want to try using a translator. If English is your first language and you're typing this way on purpose you might want to review our etiquette guide http://www.helionet.org/index/topic/1544-the-official-etiquette-guide/
  5. It looks like you're running wordpress which is probably the most commonly targeted website software for hackers to try to upload junk to and gain control of. I would recommend upgrading to the latest version, deleting all themes and plugins, and only install themes and plugins that are verified as clean. A lot of free themes for wordpress are actually just backdoors for hackers to upload whatever they want to your website. Fixing the underlying problem will prevent your account from being suspended again for malware in the future.
  6. Your account was suspended for the following reason: Malware. 2 file(s). PHP.C99-9 FOUND That means that there are some malware files found on your account. For your safety and to protect your website from potential further corruption the account has been suspended. To find the infected files we recommend making a backup of your site, download the backup file to your computer, and scan the backup using a reputable virus and malware scanner. If you're having trouble locating the offending files please ask and we can provide more information. If you are you certain that it is a false-positive, we strongly encourage you to file a false positive form here: http://cgi.clamav.net/sendvirus.cgi Your account should be unsuspended now, but keep in mind that this is a temporary unsuspension. You have 24 hours starting at the time of this post to clean your account of any and all malicious files or your account will be resuspended. /home/madler/public_html/wp-includes/js/js/cnn.php /home/madler/public_html/wp-includes/js/js/rconfig.php
  7. Thanks for letting us know. Yeah, it's fine to have one account for each of you; one for you and one for your wife. You'll be safe from multi-account suspensions now.
  8. Ok, the email address on the Igrec account has been changed. Log into it and resend the validation code to get that account validated. Once you have that account functional I will delete the chigle account so you will always have one functional account. (Sorry about the delay, I don't remember to check "Contact Helinet" subforum very often apparently.)
  9. This support request is being escalated to our root admin. Escalating this thread so it doesn't get flagged as inactive. It doesn't seem like it's going to be an easy fix, so I'll have to take a look at it when I have some time. For now you could try running your django application on Stevie instead if you want after moving your account by using this guide http://wiki.helionet.org/Moving_your_account Django on Stevie seems to be working fine, but Johnny not so much.
  10. 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.
  11. 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.
  12. 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.
  13. Your account is showing up as clean now. Thank you for taking care of this.
  14. Your account is showing up as clean now. Thank you for taking care of this.
  15. 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?
  16. http://wiki.helionet.org/Moving_your_account
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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
  23. 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?
  24. Sorry, I'll wait 24 hours before fixing it next time to better live up to everyone's expectations.
  25. 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.
×
×
  • Create New...