Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,022
  • Joined

  • Last visited

  • Days Won

    617

Everything posted by wolstech

  1. It's likely because the system still thinks you have a Ricky account even though Ricky has been retired. Do you have the donation's transaction number? We can remove the record for the Ricky account and resend the invite to you.
  2. Added. It'll take up to 2 hours to work. Please make sure your name servers are set to ns1.heliohost.org and ns2.heliohost.org, or if you use external DNS that an A record exists pointing to 65.19.141.67 and an AAAA is pointed to 2001:470:1:1ee::2009
  3. Those settings are wrong (Postgres is on port 5432 and requires a request for remote access as well). Closing since it's no longer needed.
  4. I already answered you here: https://helionet.org/index/topic/56399-whats-the-out-going-email-server-info-for-the-tommy-server/
  5. Your A record should point to 65.19.141.77. I also re-enabled the domain because it was disabled (domains that aren't pointed to our servers are periodically disabled to improve performance). It might take 1-2 hours for it to work once you set the DNS record.
  6. SMTP should be tommy2.heliohost.org on port 25 (plain) or port 465 (secure). I want to say 587 works as well, but not positive on that. The server requires authentication using the email address and the password you use for it. Please keep in mind there is a 50 messages per day limit on sending email (note that each recipient on an email counts as one message, so one email sent to two people counts as 2 emails). Exceeding the limit will result in the mail service being removed from your account for overuse. Also, be aware that SPF and DKIM are not configured by default so many mail providers, notably Gmail, will reject your emails. You should set at least one of these up if you intend to send mail. If you're using our name servers, let us know what domain will be sending mail and we can set it up. If you use external DNS, Plesk provides instructions for DKIM and you can use "v=spf1 a mx ip4:65.19.141.77 ~all" for the SPF record.
  7. It's because his account is on the backup IP we used to keep it online during the recent DDoS. Tommy's .106 IP does not have reverse DNS configured, so accounts on it cannot send to Gmail. Krydos can fix it.
  8. What is the username of the account? I don't see any accounts recently suspended...
  9. If you're using the Plesk SSL, uncheck the option for wildcard certificates and run it again. It'll install without any DNS verification at all. We don't support wildcard certificates at the moment, and most users don't need them anyway.
  10. I see a working WP installation at that domain. Please clear your cache. It may also help to use a different browser.
  11. Added. It may take up to 2 hours to work. In the meantime, please make sure your domain has name servers set to ns1.heliohost.org and ns2.heliohost.org, or if you use external DNS that an A record is pointing to 64.62.151.106 and an AAAA is pointed to 2001:470:1:1ee::2002.
  12. Changed. It may take up to 2 hours to take effect.
  13. It's because the IP address on our name servers for the domain does not match the account IP in Plesk. Krydos can fix this.
  14. You can't do it yourself if you're using our name servers, but Krydos can add it for you if you post the record that needs added and the domain it needs to be added to. If you need to update DNS frequently, you could also consider switching to external DNS like cloudflare.
  15. For now you have to ask us and we'll post the usage chart for you if you want to see it, but eventually you'll be able to see it in the dashboard at https://heliohost.org/dashboard/load/ Unsuspended.
  16. You caused a significant amount of load and brought the server to a crawl for 3000+ other websites...your CPU usage was more than twice that of the second heaviest account. This was your load over the past 24 hours...during those big spikes, each which lasted an hour or more, your account was slamming the CPU and the memory usage wasn't much better (that cliff at the end is where I suspended you and your load went to 0, which brought the server back to a tolerable overall load). Some software products are especially bad about this, Wordpress (especially with plugins) being the most common offender. Other software like Moodle, Magento, and Prestashop are also common causes. How do you plan to fix this?
  17. Added. It'll take up to 2 hours to work. Please make sure DNS has an A record pointed to 65.19.141.77 and AAAA pointed to 2001:470:1:1ee::2002.
×
×
  • Create New...