Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,050
  • Joined

  • Last visited

  • Days Won

    617

Everything posted by wolstech

  1. It's not. The new one will not be deployed.
  2. Considering the topic's age, that's unsurprising. Feel free to post new ones
  3. Wouldn't be surprising considering Freenom is already terrible in every other way imaginable...
  4. The NS records are in fact there, just wrong. They need to be "ns1.heliohost.org" and "ns2.heliohost.org", not "ns01.heliohost.org"/"ns02.heliohost.org" (there's no 0 in the correct entries). Also, there are no third and fourth name servers, so those should be removed entirely. @Krydos: Byron's tool is a bit odd with the NS option. If the records are pointed to servers that don't exist, they sometimes won't show unless you pick "ALL".
  5. This is normal. Java is enabled only on one protocol at a time. When you request it, it's enabled on plain HTTP. Remove your https redirect and your site will function properly. Or, we can enable it on HTTPS, but then regular HTTP connections will give a 404 error instead.
  6. No problem. Glad to see it's working now
  7. Assuming the script will run on our servers, use localhost, or 127.0.0.1 if it needs an IP. If accessing remotely, be sure to allow your IP in the Remote MySQL section of cPanel, then use johnny.heliohost.org (or 64.62.211.131) as the host. Is there a specific error it's giving you?
  8. cPanel does not play nicely with odd browsers, browsers that block cookies, or with networks that change IPs too often (not your issue, it gives a different message). I'd start by switching to Chrome or Firefox. The fact you can even get to the "Continue to cPanel" button means your username and password are correct, but I'd next suggest resetting it anyway: https://johnny.heliohost.org:2083/resetpass?start=1 If the above two things don't fix it, let me know and I'll escalate this for you.
  9. Unblocked. The username and password for heliohost.org is the same as cPanel, they're just two different ways to log into the same system. The forum password can be, but does not have to be the same password (though it will be if the forum account came with your hosting account).
  10. DNS can take up to 24 hours to update. Just because your registrar knows you changed your NS, doesn't mean everyone does. It takes a little while for everyone else to find out (generally because DNS servers have caches that need to expire).
  11. Is there a reason you need so many connections? Most users who see this error are seeing it because their code doesn't properly close connections when it's done using them. Our limit is I believe 4 concurrent connections per user.
  12. CNAME setup should work on free CF accounts just fine. It must be done through cPanel though since it uses our nameservers instead of theirs. You won't even see mention of it on their website. I don't know much about it though since I use full zones myself (much more powerful and flexible if you don't mind the nameserver dance to add domains). To set up both domains on CF, you just treat them as if they weren't related. CF doesn't know they're on the same account or how they're added, and couldn't care less if it did. It just needs to know they're both hosted here. Set the addon domain to our servers and add it so it works (you've done this). Now go back to CF's website, and set up CF just like you did for the main domain. Create a zone for it, copy the DNS settings, then change the addon domain's name servers.
  13. This support request is being escalated to our root admin.
  14. We're looking into the cause still, but no need to worry about it. The two outages are believed to be related though. The first outage was due to data center power outage caused by a direct lightning strike. The second outage was the server crashing because it ran out of memory (we don't know why, but corruption from the improper shutdown is a likely cause).
  15. Yeah, I prefer the CF website too. Just figured I'd mention it since some users like it for the "CNAME Setup" it offers (which lets you have CloudFlare without messing with changing nameservers). The CNAME Setup option is completely incompatible with the CF website though, and in fact actually bars you from using the CF website if you pick it (it just says you must manage through cPanel).
  16. We have CloudFlare in cPanel now too, so you don't even need to log into CloudFlare separately if you don't want to. If you use the cPanel plugin for CloudFlare, the "Full zone setup" option is functionally the same as doing it manually through CloudFlare.
  17. That account is not suspended. If you see a suspended page, please clear your cache.
  18. 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/renew. To prevent this from happening in the future please remember to visit https://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.
  19. 65.19.143.6 is the shared IP. Important ports are: Port 21 FTPPort 25 SMTPPort 80 HTTPPort 443 HTTPSPort 2083 cPanelPort 2096 Webmail.
×
×
  • Create New...