Jump to content

wolstech

Chief Risk Officer
  • Posts

    19140
  • Joined

  • Last visited

  • Days Won

    758

Everything posted by wolstech

  1. The main domain is working. Please clear your cache. As for the addon domain, please remove cloudflare and change your name servers to ns1.heliohost.org and ns2.heliohost.org. After that, verify the domain appears in the addon domains list in cpanel. If it does not, add it and wait 12 hours. If you receive an error adding the domain, please let us know and we can assist further.
  2. Unblocked. It may take up to 10 minutes to be effective.
  3. I will leave this open for Krydos to see. He's the one who handles advanced requests such as this. Please be advised that Krydos has been busy with non-HelioHost stuff lately, so your request may take several days to be completed. We're all volunteers who don't receive any sort of pay for what we do here, so we all have a life and job to tend to as well
  4. Your account has been unarchived and moved to Tommy. You should now be able to log in.
  5. That account is suspended for Phishing. HelioHost does not tolerate phishing activity of any kind, and for security reasons will not unsuspend, back up, or delete an account that was involved in phishing. You will need to create a new account and restore any backup you may have. Please be aware that you will not be able to reuse any domains on your suspended account, and will need to pick a new username. We apologize for any inconvenience this may have caused.
  6. Unarchive done. Now moving...
  7. Tommy can take up to 24 hours to get Java installed, but usually it happens in less time than that. The wait shouldn't be too long. You'll know it finished because there will be a form for deploying a war in place of the request Java message once it happens, and your domain will show a tomcat 404 error instead of a directory listing.
  8. I've answered in your other topic and unsolved it for you. My response is copied below for reference:
  9. I'll answer here since you posted it. For #1, we don't support HTTPS for Java by default because it uses a lot of resources and means your account would up 2 Java slots instead of one if supported both HTTP and HTTPS. It can be enabled for you, but regular HTTP won't work anymore if you want us to do this. For #2, this is a limitation of how we handle WAR files. It occurs because we deploy into a username prefixed folder. If we didn't, nobody else on the server would be able to have a WAR called "blog". We recommend naming your WAR file with the username_ in front of it (e.g username_blog) so the deployment path and the URL are the same. There is no fix other than to either rename the WAR, or develop your code to make the assumption that the username will appear in front when searching for its files.
  10. It worked correctly this time around. No idea what happened with the last account. Please go ahead and request Java/deploy the WAR again. It should work properly now for you.
  11. An invite has been sent for a new account. Please sign up again using that invite.
  12. That account doesn't have Java enabled on it from the looks of it. Assuming you've requested Java in cPanel, your domain is supposed to show a Tomcat 404 error if it was enabled. Looking at that account, there's something...odd...about it too, in that I can't find it in some of our admin tools despite it existing. From what I can tell, something went wrong when it was created...this will need to be looked at by our primary root admin Krydos, which may be a while since he's been busy with other non-HelioHost stuff (we're all volunteers, so we all have a job and the like to tend to as well). If you prefer, I can just delete the account and send an invite for a new one. Would you prefer to do that instead?
  13. That link has a typo in it, my apologies. It should be https://tommy.heliohost.org:2083/
  14. The username for that account is soeng, not leostar. Also, the domain associated with that account is hongsoengsiv.heliohost.org. Try signing in here using soeng as the username: https://tommy.heliohgost.org:2083/
  15. You're not blocked on our end...
  16. What was the username on the account?
  17. The 68 you're seeing is the total open connections for all accounts on the server. MySQL Connections are limited to 4 concurrent connections per account on Johnny and Ricky. Tommy has a limit of 6.
  18. It's probably a stale DNS cache. If you're on windows, open a command prompt and run: ipconfig /flushdns To clear out the stale Ricky DNS entries
  19. Unblocked. Make sure you're using the right password in your FTP client. It may take up to 10 minutes to go into effect.
  20. If you follow this topic here on the forum, yes you will. Krydos will post in this topic when it has been configured for you
  21. Done. You should now be able to log in and your website should start working within 12 hours.
  22. OK. I'll move this so he sees it. Please note though that there's been a delay in getting escalated requests like these handled lately though. The admin who handles these, Krydos, has been busy with non-HelioHost stuff recently. We're all volunteers and don't get paid for what we do here, so we do have a real life and a job to tend to at times
  23. We should also be able to use the email address of your paypal account if you don't know the transaction ID.
×
×
  • Create New...