Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,064
  • Joined

  • Last visited

  • Days Won

    618

Everything posted by wolstech

  1. I believe the description given means it got hacked or was used in an attempt to hack out server. Please create a new account.
  2. The one you and Byron linked is the full TOS, at least as I've known it. The TL;DR version: Nothing illegal, no porn, no spam, one account, service is 'as-is', no liability for any losses (regardless of reason), no guarantee it will work or keep working, we can edit/delete your data or account for any/no reason.
  3. No. When tommy is released, you'll be able to use a newer version on that server.
  4. Just sign up on Stevie. It's the only server available. If you need your domain removed from your Johnny account, post your username and domain here and I'll have an admin remove it for you.
  5. wolstech

    Java/jsf

    Java is currently not supported because both of the servers it is offered on are not available (Johnny crashed, Tommy isn't released yet).
  6. Your account was suspended for running too many cron jobs. To help keep load low, we limit accounts to two (2) cron executions in a 24 hour period. This means that, if you only have a single job, it can run no more frequently than once every 12 hours, with two jobs, they can each only run once a day, and so on. Your account has been unsuspended.
  7. Phpmyadmin can be fixed by changing your cpanel password then logging out and in again. Be sure to select "synchronize MySQL password" when changing it.
  8. I wouldn't worry about it since it doesn't really help security that much. Being a free host, anyone could sign up and just check most of that info in cPanel. Plus, things like PHP expose themselves in the headers too. Pretty much all hacking incidents we see are account compromises that result from insecure user-installed software (usually WordPress) or weak/stolen passwords.
  9. Those no longer work due to the damage from the crash. Escalating so a root admin can delete it for you.
  10. This support request is being escalated to our root admin.
  11. If you created the account through the new system, it should've given you that to start with I think. The method I listed was for existing accounts or ones created through the classic site. Escalating.
  12. We recently offered everybody an increase to 1GB if they verified their email address. You should be able to get this increase yourself by signing into our website here:https://heliohost.org/?_=new After that, select the option to validate your email address. Once you complete the verification, it should automatically give the increase. If it does not, or you don't see the option to verify, let me know and I'll escalate it for you.
  13. twnn.heliohost.org is now working, however the file index.php does not exist. Please clear your cache and verify that index.php is in your public_html folder.
  14. This support request is being escalated to our root admin.
  15. Duas.ga is now configured and is already working for me. Please clear your cache again.
  16. What is the account name and email address in question?
  17. I'm not seeing that domain in our system. You probably parked it too soon and it didn't park successfully. Can you please re-park it (remove first if present) and let me know when you've done so? Once you do that, I'll verify it parked properly, then you just have to wait the 24 hours for it to work.
  18. That's just saying it can't find a custom error page for the forbidden error. It's normal if you don't have one set up. If you'd rather show a pretty forbidden page that matches your site, you can set up some custom error pages in cPanel. You specify them by their error code (e.g. 404, 403, 500, etc.). That can be done here: http://stevie.heliohost.org:2082/frontend/x3/err/index.html
  19. That account is still queued. Accounts take 24-48 hours to start working.
  20. They've probably gone invisible. Can you list the database names so I can have krydos take a look?
  21. I see an internal server error. Please clear your cache. The server error is likely caused by whatever software you have installed.
  22. This should be fixed now. Can you try it again?
  23. You just have to wait until 2am unfortunately. Back when I joined, registrations were on pacific time. I live in eastern time, which meant I got up at 3am to register...most of us who've been around here long enough have done it at one point. You can see the state of sign ups here: http://heliohost.grd.net.pl/monitor/ Note that Stevie is the only server that currently accepts registrations. Tommy is not yet released (he's still in private beta), and Johnny is crashed.
  24. Nodejs is not supported. We only support technologies that host through apache. Nodejs is a standalone own server.
×
×
  • Create New...