Jump to content

Krydos

Chief Executive Officer
  • Posts

    24,685
  • Joined

  • Last visited

  • Days Won

    877

Everything posted by Krydos

  1. Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...
  2. Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving... Done. You should now be able to log in and your website should be working again.
  3. Does dreamweaver support SFTP? If so use Host: johnny.heliohost.org Port: 1373 Protocol: SFTP Username: cliffm Password: <same as cpanel> If dreamweaver does not support SFTP Host: johnny.heliohost.org Port: 21 Protocol: FTP Username: cliffm Password: <same as cpanel> We strongly recommend using SFTP if it's available since it actually uses encryption.
  4. No, I meant backups you created and downloaded prior to the crash. We always recommend taking frequent backups.
  5. Yeah, I ran a script to process the logs, bandwidth, and statistics for your account. It fixed the display error.
  6. Do something like this $conn = new mysqli("localhost", "user", "password123", "db"); $sql = "select things from stuff where id = '1'"; $result = $conn->query($sql); $row = $result->fetch_assoc(); $thread = $conn->thread_id; $conn->kill($thread); $conn->close(); Open then execute the query then close it immediately. No other code in between. Obviously don't do things like execute mysql queries inside loops, etc. Just write good code basically.
  7. That sounds like you were using innodb tables. I searched and it looks like prestashop 1.4 and above use innodb by default. What innodb means is that it can't be recovered after a server crashes. Myisam (our default) can be recovered after a crash. That's part of the reason we recommend it to everyone, and that's why if you create a database without specifying you end up with myisam. You'll need to use your next newest backup to restore and you'll lose whatever difference there was between when you took the backup and when the crash occured.
  8. You were blocked for failed imap logins. Be sure the credentials saved in your mail client are correct. Unblocked.
  9. Your php files are permissions 664. They need to be 644. Your directories are permissions 775. They need to be 755. You can change permissions in SFTP or through cpanel file manager. Let us know if you need more help.
  10. No problem. Since you have a nice paid domain .com I would also like to suggest that you consider moving to one of your production servers. Tommy is much faster and has much higher uptime for when you start getting a lot of visitors to your domain. Let us know if you need help moving your account.
  11. It can take up to 12 hours for Johnny domains to start working. In the meantime you will probably see that 404 error or a queued page.
  12. Cool. That's a good plugin to know about. We've had a few other people with this wp-login.php load issue so I'll point them that direction if it works for you.
  13. Krydos

    Delete the other account then. You're only allowed to have one account anyways. http://www.heliohost.org/classic/support/scripts/delete Once you delete the other account you should be able to add the domain to your new account.
  14. I've never tried it, but I assume you could log in via SFTP and rename the wp-login.php file to something hidden like alhwdkwheuidwad.php and then put a new wp-login.php file with contents such as <?php echo "Logins are currently disabled due to abuse."; Then if you need to log in to the admin account just rename the files back, login, do what you need to do, and then disable it again. Also, please check in over the next few days to see how your load is doing. Our suspension system is automated to preserve the functionality of the server, but we can check your load levels to make sure you're not at risk of being suspended again. If one account is causing the other thousands of websites on the same server to run slowly or go offline our automated systems have to correct the problem.
  15. Unsuspended. Please make the changes swiftly before your account starts to cause a lot of load again.
  16. Try deleting or renaming your .htaccess file.
  17. Most of your load is coming from /home/cbrpics/public_html/wp-login.php which probably means you have a lot of bots trying to bruteforce their way into your wordpress account. Would it be feasible to disable logins? Like wolstech said you have basically no bandwidth usage so your site shouldn't be causing this much load unless something is wrong.
  18. On November 22 he created an account called eventor on Johnny. Today he deleted his Johnny account and created a Ricky account. Rather than delete his forum account, I renamed it to match his new hosting username.
  19. You can delete your own hosting account at http://www.heliohost.org/classic/support/scripts/delete Would you like your forum account deleted as well?
  20. Does it look better now?
  21. See https://www.helionet.org/index/topic/30848-account-archived/?p=139049
  22. Yeah, you only have one database and it's 11 MB not 2807 MB. Not sure why it would say that. Is there any effect in cpanel due to this bug or is it just graphical? Can you still upload files and/or update your database?
  23. The error isn't yours. The code that deploys .war files needed to be edited slightly due to the tomcat version upgrade. All that needed to be done is to add a single character. Here you go http://harshacommunications.com/Harsha_Communications/
×
×
  • Create New...