wolstech

We keep VPSes for ~30 days past their shutdown date as we only have a limited amount of resources. Below are the dates associated with your VPS. We kept it running for 2 full months without payment (January 11 to March 11, with a warning sent on March 3), then gave you another 30 days to renew it after it was turned off. You had the opportunity to renew it at any point between January 11 and April 10 (3 full months) and failed to do so, so it was deleted. VPSes are not free, and users who do not make their payments in a timely manner are subject to cancellation so the resources can be sold to someone who will actually pay. We've got to keep the lights on somehow. Signed Up 2020-06-22 07:23:05 Expires 2026-01-11 18:16:02 Warned 2026-03-03 18:11:48 Shutdown 2026-03-11 20:01:13 Deleted 2026-04-10 21:30:02 At this point, your next step is to use the link Krydos provided in the last email if you wish to have your service restored. Since it's past its deletion date, your IP address and VPS slot number will change when the VPS is recovered. Here is the link again if you wish to resume service: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=VUKC33MKF2CSY

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.

Cases can take up to 24 hours to receive a response. Repeatedly replying to your own case will delay response time, as our system moves you to the back of the line each time a reply is added. Also, as a reminder, all of our staff are unpaid volunteers who assist here in their free time, and have responsibilities outside of HelioHost such as a full time job. As a result, staff are not always online. Please be patient until you receive a response, as we work cases in the order received with the oldest requests first.

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

After reviewing your request, it appears your account is not the only one affected by this issue. PHP is intermittently failing for all Johnny users. As of this reply your website is working properly. We're looking into the cause of the intermittent PHP failures. Note that this issue is specific to Johnny users. Users of our Tommy and Morty plans are not affected.

Try clearing your browser cache. If that does not resolve it, it's probably an issue upstream somewhere, likely either a stale cache at your ISP or a DNS configuration issue. Since you do not use our DNS, and you have genrwork's DNS hidden behind Cloudflare, we are unable to troubleshoot this further. If you would like us to troubleshoot this, please turn off the Cloudflare Proxy and any associated gateways/security pages like Cloudflare Turnstile on genrwork.com. As for the domain udomz.com showing that domain setup page, it's because it is currently disabled due to not being pointed to our servers. Domains with DNS records that do not point to our IP addresses are automatically disabled to reduce server load.

DKIM, SPF, and DMARC have been set up for the domain douglaswebster21.helioho.st. We recommend sending a real email (not just the word "test" or a blank email) to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

Your account has been reset. When the process finishes, you'll receive an email with a link to set up a new account. During that process, you can pick a new main domain. If you need any of your old data, a backup will be available at https://heliohost.org/backup/ once the reset has completed.

Glad to see you figured it out Please let us know if you need anything else.

Resetting your account is just “delete account and reinvite user” internally. Make sure you use the link in the email, it should let you create an account without paying since it’s a reset. If the email link is trying to make you pay for some reason, let us know and we can resend the invite.

I only deal with XMR and Aeon because they require separate processing. All other currencies are handled through coinbase on our end, which is done by Krydos. But yes, we can accept LTC or any other currency listed on the donate page: https://heliohost.org/donate/ Please provide the transaction ID and coin used after sending crypto. The amount credited will be based on the amount received in our wallet (which is after fees/gas/etc.) so be sure to account for those when sending.

It looks like the donation from February 26 was never added to your account (you do have to contact us to refill Morty accounts after you send money, it won't happen automatically). I've credited the $11.30 donation from Feb 26 as Morty balance for you. With the bonus, your balance is now ~$13.56. Thank you for your payment The space appears to already be added (that process is automatic unlike balance refills). The space was added on March 27 through the dashboard.

The load specifically was because you left an SFTP session open. My guess is you opened a connection, uploaded something, and then just left the FTP client running and forgot about it. Please make sure you’re disconnecting from SFTP when you’re finished using it.

Are you trying to sign up for Johnny? The Johnny option on the Plans page does that intentionally when its full for the day to keep people from registering. See https://wiki.helionet.org/Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny for more information on how to get an account on that server. The other options are available 24/7 but are not free. Tommy: https://heliohost.org/tommy/ and Morty: https://heliohost.org/morty/

Oh...legacy account. Yeah old cPanel accounts used to do that (put addon docroots inside the main domain docroot). We typically recommend just resetting the account if its old enough to be set up that way because of all the weird bugs these accounts usually have, but the fact you both would lose your legacy .org domain (the new account would be keibeeit.heliohost.us since the .org ones are now limited to staff), have third party email DNS set up manually by us, and have an (also really old) Lily account attached to it that would need to be manually fixed after resetting make resetting kind of impractical if the account otherwise works. The document root for domain keibee-it.com has been moved to ~/keibee-it.com for you and will take effect within the next 2 hours. It may show a 404 error or other strange behavior until then.