Jump to content

wolstech

Chief Risk Officer
  • Posts

    16,491
  • Joined

  • Last visited

  • Days Won

    591

Everything posted by wolstech

  1. 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.
  2. It's worth noting that although it might install, it likely won't work because of the firewall.
  3. Did you set the file's permissions to 755? Python requires that to run here. Perhaps this topic might be helpful: http://www.helionet.org/index/topic/19972-using-python-for-cgi
  4. That account does not exist. It was probably deleted for inactivity.
  5. That page needs to be edited. We have no plans to upgrade currently for compatibility reasons (cpanel is rather picky, we use what comes with it, so whenever it gets updated is when PHP will get updated). If we upgrade anything, Johnny generally will get it before Stevie. EDIT: Page updated. Also, for what it's worth, we have 5.3.8 on Stevie, 5.3.23 on Johnny.
  6. You got it...3 cron jobs. You've been unsuspended.
  7. You need to set your domain's name servers to ns1.heliohost.org and ns2.heliohost.org in your registrars control panel. MX records are not the same thing and do not matter for this.
  8. Just to note: That topic is for stevie, but Johnny's MySQL is also damaged in the same manner, so it applies there as well. With both servers like this, we don't have innodb support anymore.
  9. That's odd. It works from some other hosting company, but two different ISPs and multiple devices of yours don't work at all. Are you using the correct host and credentials? It should be: Host: johnny.heliohost.org / stevie.heliohost.org depending on server (don't use your domain name!) Username: (cP username) Password: (cP Password) A DB user you create in cP should work as well, but your cP username will let you access all DBs in your account. I'd recommend you get it working first with the cP account before using an added user. Are you sure you have the remote mysql enabled correctly? It sounds like it already is, but to verify: The only access host that should be listed should be a single % sign. There should be no quotes, no IPs, nothing else in that row. Also, there should be no other hosts in the list. Other than that, I'm out of ideas. Perhaps somebody else here knows what might be the issue. If you want I can escalate it, but it might take some time for Krydos to look at it since it's not a major/server-wide issue.
  10. Have you tried using a different program (e.g. MySQL workbench) to access them? It's possible that the program you're using is incompatible or poorly coded. I have one that won't access DBs here. Java app in my case though (JDBC driver says it can't find the server...) I'd suggest ISP as well, but you already tried that with the mobile hotspot.
  11. Your password has been reset and a new password was sent to the email address on file for your account.
  12. It sounds like your network or PC is to blame. Do you have a firewall on your PC other than Windows Firewall? If so, turn it off. Check your router as well (if applicable). Are you on an enterprise network? If this is the case, you'll need to talk to your IT department and see if they are blocking it. Many company networks block outbound access to non-web ports to prevent the use of outside services for security reasons. It's not likely to be on our end if you whitelisted % and another web host is able to connect to your databases without issue. If our firewall was blocking you, you wouldn't be able to access your website or cpanel.
  13. See http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ Also, I know that topic is for stevie, but some have reported that the problems are also affecting Johnny. There is no estimate on when it'll be fixed. It broke almost a year ago, so I'd say its safe to assume it won't be fixed in the near future.
  14. You were suspended for running 3 cron jobs. The limit is 2 per day. Your account has been unsuspended.
  15. Looks like someone misused /tmp on Stevie and filled it up again... Getting upload errors and cP shows it as full.
  16. This support request is being escalated to our root admin.
  17. LASHBACK listed us again for some reason...
  18. It's been damaged since February 2014. Its not a user crashing it, and there is no easy fix for it (hence why it remains unfixed). See http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ (I've seen symptoms recently that suggest Johnny might be developing a similar problem)
  19. That domain is working fine. Seeing you can't access it, and FTP and cpanel don't work, you're probably blocked by the firewall. An admin can check and unblock you if needed.
  20. You can delete your account here: http://www.heliohost.org/home/support/scripts/delete
  21. 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.
  22. You were suspended for high server load for the second time. Please note that you only get three strikes for that reason, so please fix the issue causing the load. We might not unsuspend you if it happens again. Your account has been unsuspended.
  23. Pgadmin iii works fine for me. Are you using Stevie.heliohost.org as the host, and your cpanel username and password? There is no other solution at the moment other than possibly adminer (a mostly universal php SQL tool).
  24. PHP runs from the top down. You put the code that displays the contents of the arrays before the code that puts the stuff in them. They're always empty because the code that puts the results in hasn't been run yet. Move the code block that shows the array entries (lines 19 to 40) to line 319 (after the queries and if (!$q#) stuff but before the footer) and it should work.
×
×
  • Create New...