wolstech

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

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.

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.

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.

Are you waiting up to 2 hours for an apache restart? Node doesn't fully disable/enable immediately. It needs an apache restart to take effect.

You got suspended for using too much memory. The limit is 200GB per day. Please fix the issue quickly. Unsuspended. It may take a few minutes before you can login again, and domains can take up to two hours to function.

You're the first person to report that the logs are slow only when node is enabled... that's an interesting observation. Morty would likely make it faster since the entire server is quite a bit faster than Tommy, but I'm actually kind of curious as to why this only happens to you when node is enabled. Maybe Krydos has some input on this?

It was suspended for high load caused by systemd, which is likely due to excessive use of cron. The scheduled jobs have been turned off on your account and you've been unsuspended, please fix the issue quickly. It may take a few minutes before you can sign in again, and domains can take up to 2 hours to function.

That domain is working properly for me. Please clear your cache. Note that this error is usually caused by running out of disk space, and you are very close to your limit (975 of 1000MB). I suspect you were over your limit earlier and have since dropped below due to something like log rotation freeing up space.

error_log for domain twoofswords.net has been discarded. The best fix for this is to enable log rotation and set a max size that's reasonable (like 10MB) with a low maximum number of logs (like 3). That way the server will rotate them out and then eventually delete them for you. I've gone ahead and set up the rotation for you on that domain so this won't happen again.

Escalating to have this enabled for you.

Account senex has been unsuspended. It may take a few minutes before you can login again, and the domains can take up to two hours to function.

Can you explain why all of the accounts have very similar usernames? (Also, on the off chance these are a result of you just needing multiple websites, you can have multiple sites on 1 account...a Johnny account can have up to 5 websites/domains on it).

Domains that are already added as an add-on domain cannot be switched to the main domain without resetting your account. https://wiki.helionet.org/Changing_Your_Main_Domain#Account_Reset_is_Required_to_Swap_Main_and_Addon_Domain

The pending suspensions for luisgalvan and backupchiquipoli have been canceled.

There are actually 3 accounts associated with you this time (two of which are the luisgalvan and backupchiquipoli accounts you've been allowed to keep already). Did you or someone you know create a third account without contacting support for permission? Also, did you at any point use a VPN to access your accounts?

Yeah you had a ton of load coming from Python (note these numbers have dropped off a bit because you've been suspended for a little while). 66.38 GB 120.2 /usr/bin/python3.12 -u -O /home/dragoe.helioho.st/httpdocs/AppFiles/Moonlark/moonlark.py -n DragoE 56.11 GB 28.1 /usr/bin/python3.12 -u /home/dragoe.helioho.st/httpdocs/AppFiles/Watchman-main/Watchman.py There was also resources being used by the system due to the long-running python processes (about 14GB as of this post), which you can't really do anything about...it's just the nature of linux managing sessions. Please reduce the memory consumption quickly. Unsuspended. It may take a few minutes to work again. Domains can take up to 2 hours to function.

If you have the certificate file (and matching key file), you can likely install that instead of Lets Encrypt. Not sure how you do that on Hestia, but I'd imagine there's an option or guide for it. It should work provided the certificate is not expired and the common name and subject alternative names (SANs) are correct (the domain/subdomain you're securing needs to appear in one of those fields on the certificate unless its a wildcard certificate). A domain's certificate is sent to the browser by whatever server is serving that domain, so you'll need to install the PositiveSSL cert on your VPS if you want to use it once your (sub)domain is pointed to your VPS.

Information sent by PM.