Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,705
  • Joined

  • Last visited

  • Days Won

    659

Everything posted by wolstech

  1. Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. To prevent this from happening in the future please remember to visit http://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.
  2. Cloudflare is supported but needs to be set up manually. We were supposed to get a cpanel extension for it, but Krydos never got around to it since he is busy and a bunch of other things decided to break. Seeng we're doing a bunch if updates to Johnny, maybe now would be a good time to add it. Either way, this post will serve as a good reminder that it still needs to be installed.
  3. You're likely blocked in the firewall. This usually happens when you use FTP too much. An admin needs to unblock you.
  4. It's not down. 1045 is access denied. Log into cpanel, then change your password here: http://johnny.heliohost.org:2082/frontend/x3/passwd/index.html Make sure you have the synchronize MySQL password box checked.
  5. Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. To prevent this from happening in the future please remember to visit http://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.
  6. Krydos is the one who has to make this decision. Sometimes it can be a day or two before gets to it. As long as it isn't [solved], he'll see it eventually.
  7. Verify that your URL does not start with https. Also, try removing the cloudflare and using our server directly.
  8. FileZilla should have an option to limit the number of connections it uses. Try setting that to 3. Try passive mode if not already using it. I've also seen it happen for no good reason. In that case, just ask to be unblocked again. Finally, Wordpress is very easily hacked and abused. Stay away from "free" themes and plugins off of random sites. Try to find these on sites like wordpress' own listings. Dubious themes are notorious for malware, spambots, and backdoors, and plugins can also be malicious. Keep everything up to date at all times.
  9. Nothing was updated in Stevie. This problem does not exist on that server.
  10. Looks like we either need php or MySQL fixed. The error comes from using a MySQL version different from what php's mysqli library is for. Seeing we fixed MySQL recently on Johnny, I bet we updated it and didn't update the php libraries. Escalating.
  11. That's the firewall. Too many connections over FTP is the most common cause. I'll move this to customer service so an admin can unblock you.
  12. Stevie was not down at all today per the monitor: http://heliohost.grd.net.pl/monitor/ If you cannot access anything, you might be blocked in the firewall. Can you log into cPanel?
  13. MySQL 5.5 is available on Johnny and will eventually make its way to Stevie. There are no immediate plans to update php. When we finally do, it will be updated on johnny first. We support all software requiring php 5.3.x. Software requiring php 5.4, 5.5, or 5.6 may or may not work, and officially is not supported here.
  14. We broke a bunch of databases trying to fix the frequent database server crashes. Krydos has to fix this. Escalating.
  15. I see "UNOFFICIAL OTA Server by BioGenX". Please clear your cache.
  16. You were suspended for spam. I'll escalate this.
  17. Your forum account and hosting account are not connected to each other. You can receive hosting email without validation. In fact, we currently don't have email validation for hosting, though we hope to change that in the future to improve communication and reduce the number of spam and phishing accounts we get. Only forum accounts require email validation before you can post. You don't need to validate anything right now since you can already post.
  18. You were suspended for running 4 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.
  19. This support request is being escalated to our root admin.
  20. I'm getting DNS errors for the heliohost.org subdomain, and newforte.cf is still queued. This should have been setup by now (8 days).
  21. It can't be marked solved since it's in the web section. This really should be a customer service topic. I'll move it and mark it solved for you
  22. Install it manually. For details, see http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ (this issue is listed near the bottom of the first post)
  23. Their website does use it in many cases. It's read only so they can't change anything, but their websites at least show up when viewed. If it were missing entirely, they'd be getting an error about the database not existing.
  24. Most of our users register with emails that they don't check or are invalid since we don't verify them (we hope to change this at some point to require email validation). Some use providers that won't receive mail from us. The large majority also never visit these boards, so warnings here are moot. The only solution I can think of is to put a nice big banner at the top of cpanel about it, since they have to login so they aren't suspended due to inactivity. We'd then need to leave that there for several months before we do anything so everyone sees it. Finally, we'd need to fix it and deal with complaints we'd get from those that ignored the warnings. Not really practical.
  25. So back up damaged data, fix the (not broken) software, then restored damaged data? That'll leave us where we are now. The databases themselves, not the software, are the problem. We do not have backups of any form, and there is no way to create one that would be useful. The server is beyond repair unless we want to permanently delete every innodb database on the server. TL;DR: It can't be fixed without losing data, otherwise it'd be fixed already.
×
×
  • Create New...