Jump to content

wolstech

Chief Risk Officer
  • Posts

    19147
  • Joined

  • Last visited

  • Days Won

    759

Everything posted by wolstech

  1. We'll wait and see what Krydos says, but this is not a normal request. The DNS updates do take a while because of propagation, but since all of our servers use the same nameservers, and you've pointed the MX's to a non-HelioHost server anyway, I can't imagine much of an interruption. Maybe an hour or so while the zones are removed/readded. Also, if you don't mind donating $1, you can try our beta script to move the entire Ricky account onto Tommy as-is without having to reconfigure it (you'd need to delete the Tommy account you made first). If you want to do that instead, go ahead and donate, then let us know and we can move your account.
  2. To move to Ricky, you need to delete your account and sign up again. You can do that here: http://heliohost.org/classic/support/scripts/delete I'm not sure if it's still on offer or not (Krydos would know), but if you wanted Tommy instead of Ricky, we were recently testing a new server transfer feature that can move you to Tommy without deleting your account. A donation of $1 or more is required.
  3. The domain has been changed. It might take a little while to start working though, so give it an hour or two if it comes up queued.
  4. Seeing you already have an account now, you'd have to delete that one first (you're only allowed one account). After that, we'd need to delete/rename the forum account for verhoef (which succeeded), then you would need to wait for Tommy to be available and sign up again. If you want, I can change the domain on your vverhoef account to verhoef.heliohost.org so visitors don't use the extra V, but the username to log into cPanel would remain vverhoef. Do you want me to do this instead?
  5. The original verhoef account failed because the domain did not contain a TLD suffix. You put verhoef, but you needed to put verhoef.heliohost.org or a normal domain that you own.
  6. 98.202.246.249 has been unblocked. It was blocked for too many failed logins. Please let us know if it still doesn't work for you.
  7. The files contained malware that was being used to commit a crime. We can't provide you them because we'd then be distributing illegal software. In addition, if the malware stole data such as credit card info, we'd risk accidentally giving it to you. We can't warn you because many users intentionally sign up on our service to run such malware...warning users whose accounts are involved in illegal activity would enable them to destroy evidence.
  8. I see a plain white page with a heading "welcome to the admin module" and a bunch of Latin text. Your domain is working. If you are still unable to access it, please try accessing it using another device and a different internet connection (such as a cell phone on its data plan), and let us know if it works so we can look into it. Please be aware that domains sometimes take a few hours to start working for everyone.
  9. 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. <br /><br />If you still see the suspended page, please clear your cache.
  10. That account is suspended for Phishing.<br /><br />For security reasons, phishing accounts cannot be unsuspended, backed up, or deleted. 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.<br /><br />We apologize for any inconvenience this may have caused.
  11. Our support staff is entirely volunteer, and as such we're not available 24/7. A wait of 12-24 hours is normal for a response, in some cases we can take 2-3 days. It depends on when we have free time to come on here and respond to the requests. Support through our forums is also faster, as we work the forums before the email requests, and most of the other admins only respond to forum posts. Krydos (the one whose been helping you), and myself (wolstech) are the only ones who do the emails. As for your request, I've never heard of incapsula before you mentioned it, so I can't speak to its compatibility with our service. My recommendation would be this if you want to use CloudFlare: Purchase a domain through Namecheap (https://www.namecheap.com/?aff=102467), point the nameservers to ns1.heliohost.org and ns2.heliohost.org, then add the domain to cPanel. After that, wait for it to not be queued anymore, then use the CloudFlare plugin's "full zone" setup option to configure the CloudFlare (do NOT use the CNAME option, I've noticed some strange issues using it). Finally, change the domain's nameservers to the ones given to you by CloudFlare (you may need to log onto your account through CloudFlare's website to get them). If you want to make sure it works first, get a Freenom domain and test the above using that before buying the real domain from Namecheap.
  12. Indeed suspended for high load... Escalating for the file information. I've unsuspended you in the meantime. I would recommend disabling your site until you get the information (for instance add a deny from all in the .htaccess file) if you're unsure how to fix your high load so you won't get suspended again.
  13. That account cannot be unsuspended. Krydos might have more infomation. Escalating.
  14. Blocked again, this time for too many failed FTP logins. You probably have the wrong password saved in your FTP client...
  15. You need to delete your account and sign up again. We cannot reset accounts.
  16. It was for having too many failed cPanel logins. You're unblocked. 80.98.17.69 Tommy 2017-06-10 05:42:03 5 in the last 3600 secs lfd: Failed cPanel login HU/Hungary/catv-.catv.broadband.hu If you still cannot log in, I would recommend resetting your password as a next step: https://tommy.heliohost.org:2083/resetpass?start=1
  17. What is the IP address? We need the IP you're accessing our service from in order to determine if you're blocked.
  18. 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. <br /><br />If you still see the suspended page, please clear your cache.
  19. Please be aware the emails post publicly as well over in the email support forum. The email support is not suitable for sending private information.
  20. You can only have one account. Why do you have 3? Please delete two of them or they will all be suspended. If you're unaware, you can use Addon domains or Aliases to host more than one domain on a single account.
  21. They don't exist anymore. They were lost when the hard disk failed in the server (and even if it hadn't, an account inactive for 421 days likely would've been deleted for disk space anyway). You should sign up again if you want to continue using our service. I would recommend Ricky (which is the Stevie hardware, just renamed after it was repaired) or Tommy if you need good uptime.
  22. That's normal for Johnny. if you want it to occur faster, move to another server. Ricky usually does them in a few hours (though it can be up to 24). Tommy does them instantly.
  23. Historically, Tommy's uptime is better. Tommy recently has been occasionally having long load times (>1s), but virtually never goes down. In addition, Tommy offers instant domain setup as opposed to Ricky and Johnny (which have that up to 24 hour wait for Apache to restart). Tommy also has Java and ASP.NET available if you need them. You can see the red bands on Ricky here vs. Tommy: http://heliohost.grd.net.pl/monitor/
  24. Glad to hear you got it working. Let us know if you need anything else. (And yes actually: https://heliohost.org/donate/ )
  25. The apps subdomain is acting strangely...it threw a 500 error on me twice before the content loaded. It also has a forced HTTPS redirect which may also need to be removed. I would rename the .htaccess file to start.
×
×
  • Create New...