wolstech

Your account has been unsuspended and the mailbox passwords for all of your mailboxes have been randomized. You'll need to reset your mailbox passwords to use them. I also removed the forwarder from diretoria@escolasmt address. Forwarded emails count as sent messages (and you had 4 recipients, so each email it received caused 4 emails to be sent). We highly recommend not using forwarders, as just receiving mail will cause you to exceed your mail limit through no fault of your own. Users are limited to 50 sent emails per day for the entire account, so with that forwarder, receiving just 13 emails would've caused you to exceed the limit.

Apologies for the delay on this, I'll take a look at it in a little while when I'm at a computer for you.

Unblocked. It was listed as DDOS, so was the firewall trying to mitigate downtime on Johnny due to an attack (the user whose site was the target of that attack since been banned). During these attacks, anyone who opens more than a few connections to the server is prone to being blocked, including users unrelated to the attack and visitors to your website. In the event of another attack it is completely possible you'll get blocked if you access your site during the attack.

Yes we do. It can be configured via .htaccess.

Glad to hear it's working. Please let us know if you need anything else.

There was one IP address blocked in these ranges. It has been unblocked, can you try it again now? If it still doesn't work, I'll have Krydos take a look.

The firewall probably blocked it. Do you know what IP address the connection comes from?

Your account is being reset. You'll receive an email when the reset is complete to create a new account. As for the space usage, it was caused by 539MB worth of laravel logs in ~/httpdocs/storage/logs because your app was crashing repeatedly. The logs were almost entirely stack traces caused by a missing route.

After you were unsuspended, your site was promptly attacked by 250+ IPs all at once, which caused substantial downtime for thousands of other websites. In addition, upon further review, we've determined that your account is also violating the terms of service (specifically the clauses that prohibits offering modifications or cheats for online games as well as copyright infringement, your script is apparently some kind of keygen or licensing tool for PUBG or a PUBG cheat). Due to the substantial downtime caused by your site as well as the TOS violation, HelioHost has chosen to issue a permanent ban from our services. You will need to find a new host.

You got suspended because your site suddenly started consuming an excessive amount of CPU and slowed the server down. The usage was coming from PHP. Either your site suddenly saw a massive surge in traffic (e.g. got posted on reddit), it got hit by a bot attack that caused excessive traffic/usage, or something on your account malfunctioned (e.g. buggy code stuck in an infinite loop). Please resolve the issue quickly. Unsuspended. It may take a few minutes before you can log in again, and up to 2 hours for domains to function.

Domain added. Please be sure to configure DNS either by using our name servers ( ns1.heliohost.org and ns2.heliohost.org ) or by using A records pointed to the IPs shown in Plesk. The domain can take up to two hours to function.

CF is just short for Cloudflare and the system is looking for their name servers specifically. If a domain's name servers end in .ns.cloudflare.com the system ignores the domain's IP addresses entirely. I think these domains used to be verified via file, but I'm not even sure we actually still do this because certain features like Turnstile would be incompatible with it (Krydos would be the admin who would know if we still validate CF domains). I know Lets Encrypt sometimes has issues renewing certs on domains that use Cloudflare for this reason. When people have issues renewing certificates, the first response we always give is "temporarily turn off Cloudflare's proxy and security options and try again" and it always fixes it.

Domains that use CF are explicitly excluded from the DNS checking because it would be impossible for the Cloudflare security features to work otherwise. It's the only provider that has such an exception. CF domains used to be validated using a file-based method that doesn't involve DNS, i'm not sure if this is still performed or not.

If you enable the domain but don’t change the DNS, be aware that the server will eventually disable it again, typically within 7 days. Domains must return either one of our IPs as the A (or MX, if it’s mail-only) record, or have Cloudflare as name servers (using CF triggers our system to handle domains differently because of the proxy/security features), to avoid being disabled.

The udomz.com domain is not hosted with us at the moment. It is attached to your account but is disabled because it has DNS records that do not point to us. We see the below DNS records for udomz.com, which are incorrect. Either the NS records need to be changed to ns1.heliohost.org and ns2.heliohost.org, or the A record needs to be changed to the same .90 IP as the genrwork.helioho.st domain. If you change the DNS to point to us, you will also need to go into the domain in Plesk, set its status to Active, and wait up to 2 hours for it to become functional. If you do not want the udomz.com domain to be hosted here (or it's not your domain and was inadvertently added), let us know and we can remove it from your account instead. Incorrect A record for udomz: host: udomz.com class: IN ttl: 60 type: A ip: 151.101.41.242 Third party NS records: host: udomz.com class: IN ttl: 78276 type: NS target: ns1.vercel-dns.com host: udomz.com class: IN ttl: 78276 type: NS target: ns2.vercel-dns.com