Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,994
  • Joined

  • Last visited

  • Days Won

    676

Everything posted by wolstech

  1. A new password has been created, tested, and emailed to the address on file for your account.
  2. There is preventative maintenance going on on Johnny. There's a news post about it here: http://www.helionet.org/index/topic/22692-johnny-restart/ In addition, certain stuff broke as a result: http://www.helionet.org/index/topic/22702-2015-12-05/ It's being worked on.
  3. The script is broken it appears. I see others here this morning with the same issue. Your account has been unsuspended.
  4. The script is broken it appears. I see 3 others here this morning with the same issue. Your account has been unsuspended.
  5. The renewal script is broken. you should be able to renew a stevie account with Johnny down. I see 3 others here this morning with the same issue. Your account has been unsuspended.
  6. The script is broken it appears. I see 3 others here this morning with the same issue. Your account has been unsuspended.
  7. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.
  8. A new password was created, tested, and has been emailed to the address on file for the account ubuntu.
  9. That account is working fine. You're probably stuck in the firewall. An admin can check and unblock you if needed.
  10. Not sure where the 8MB is from, likely an artificial limit in Moodle. PHP is limited at 20M though per upload_max_filesize, so 100M files are pretty much impossible through PHP. You can always upload manually through FTP if you need to host such a file here, though putting it on Dropbox and linking to it would be better. You only have 500M of space anyway, so allowing 100M uploads makes little sense.
  11. Mod rewrite is enabled and works. I use it. I'm not sure if anyone's gotten the pretty Urls to work or not, I know others have had issues with it though and have asked. A forum search might find something on it (I'd look for you, but can't right now, i'm on my phone).
  12. They are completely automated. What's funny is the human-based resets actually work better here because of how our automated emails are handled by mail providers. A small number of services (GMX.de, Comcast, and a few others) won't accept email from us at all (it's just deleted without being delivered). Many others put our emails in spam. Odds are this is what happened. Use a gmail account for best results with our emails. If you wish, I can manually email a new password to the address on file for your account. Please let me know what your account name is if you wish to do this. Those aren't databases, they're the folders containing the actual WordPress software. Nothing related to WordPress will work with those missing since the software is pretty much entirely gone. The backups are failing because you cannot back up something that doesn't exist. As for why they're missing, Softaculous likely deleted them and failed to install them again during an update. You need to reinstall WordPress to get those folders back. We don't block anything. You can't install it because WordPress itself is missing based on what you described. Also, be aware that WordPress themes and extensions are one of the easiest ways to get suspended because they often lead to hacked accounts. I personally recommend you don't use WordPress at all because of the security issues it poses, but if you do, keep everything updated and only install components from reputable websites (no random "free themes" sites or the like, those themes are often disguised backdoors that promptly get you hacked, which can be followed by a suspension for malware/spam/phishing/other abuse depending on what the hacker does). Does this to me sometimes as well. The forum acts weird because the server is bogged down.
  13. That domain is working fine. Please clear your cache. Do you still need a password reset?
  14. This got missed because it's not actually a suspended account. Sorry about that. Escalating.
  15. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.
  16. There is nothing you'd really notice in the Apache upgrade anyway, so it's not really that important (a lot of the changes seem to be security issues we aren't affected by). We have no time frame for PHP 5.4 on Stevie (though I'd expect it at some point since Johnny has it). Heliohost generally tries to avoid running the latest versions of software for stability and compatibility reasons, especially on Stevie. If MySQL got upgraded again, it'd be on Johnny.
  17. This support request is being escalated to our root admin.
  18. This support request is being escalated to our root admin.
  19. No. Think of cpanel updates as updating the UI...the stuff it controls (except mysql which was updated to fix innodb) is still just as ancient as before.
  20. This support request is being escalated to our root admin.
  21. That domain and account are suspended for pornography. We don't permit the hosting of adult content on our service. In addition, the snapchatleaked domain was also subject to an abuse report from snapchat for a copyright/trademark violation. I'll escalate this for you.
  22. We don't plan to add anything to apache or php right now, but thank you for the suggestion. I will escalate this though, since it may actually be a useful extension.
  23. This support request is being escalated to our root admin.
  24. Did you assign the user to the database in cPanel? Is the database visible (check to see if you can view it in PhpMyAdmin)? Is the database empty? If it's not visible or is empty, Krydos needs to fix it for you. Also, did you make sure the wp-config.php file has the correct password in it? That file will have the username and password WordPress uses for database access. If the don't match, either set the user's password to match what's in the file, or edit the file to match the user's password.
×
×
  • Create New...