Leaderboard

Hi all, I've managed to follow the link again and create an account thanks for the quick responses

Looks like the Apache restart finished or has been unstuck, though the server is still seeing quite a bit of load. Your website is currently up.

Apache looks like it got stuck while restarting as there's a large number of other maintenance tasks piled up behind the restart in the queue. I'm waiting for a response in a staff channel about it...

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.

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

Please be aware that 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, when the contents of a post contains the typical characteristics of AI-generated content (very wordy and verbose, predictable paragraph structure), this can be less interesting for our human volunteers to read and respond to. All staff are real humans. We like to read and reply to posts made by real humans, even if they contain spelling mistakes or errors if English is not a person's first language. All those human staff members are unpaid volunteers who assist here in their free time. They have responsibilities outside of HelioHost such as a full time job. They are not always online to read forum posts. In the meantime, please ensure you review our support response timelines (SLAs and ETAs), at: https://wiki.helionet.org/ETA For guidance on how Community-Powered Technical Support works, visit: https://wiki.helionet.org/FAQ#How_does_community-powered_support_work? Help is generally provided within 24 hours, and we encourage users to bump their requests if it's been more than 24 hours with no response, in case we missed it somehow. Our best efforts to respond within 24 hours can be impacted by several factors, including but not limited to: Time zone differences (most staff are based in North America) Work School Family Other real-life commitments Please be patient until you receive a response, as we work cases in the order received with the oldest requests first.

Your account was suspended for sending 1117 emails. Can you explain how this happened?

Domains added, they'll take effect in about forty five minutes.

Account has been reset, and a new invite has been sent to your email address. You can also download a backup of your account before the reset at https://heliohost.org/backup

Domain changed, it'll take effect in about 70 minutes. If you're not using HelioHost's nameservers, you'll need to create a new A/AAAA record to Johnny's IP address for it to work.

IP unblocked.

This support request is being escalated to our root admins.

Hello! Domains like "helio.st" are not available in our free domains. I've guessed that you meant "familybudget.helioho.st" and added that one. Please note that it may take up to 2 hours for the domain change to take effect. If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache I also removed the familiybudget and api.familiybudget subdomains as requested. Please note there is a risk of data loss when domains are removed, since the folder for the domain inside Plesk will be deleted. I made a full account backup for you before I removed the subdomains, in case you need any of the old files. You can download the backup here: https://heliohost.org/backup If you're not sure how to extract the backup files, please follow our how-to guide here: https://wiki.helionet.org/Account_Backups

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.

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.

I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

Here are the DNS records gab.pt.eu.org. 14400 IN TXT "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" _dmarc 14400 IN TXT "v=DMARC1; p=quarantine" _domainkey.gab.pt.eu.org. 14400 IN TXT "o=-" default._domainkey.gab.pt.eu.org. 14400 IN TXT ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAlhoaveQHXrnhdK5QpkflFQXGGchTtTizdX3qnpBLQjPvOi4PNkgA2Rn2G9AYDg9z8MFH86l+MOYuOy9gOhoVHMZvVtDM5i+g/YOfKz3l5YxNb8+ltLjivU2541UyryG6leONKkOb2+mWC2vZJ7o3+Wl0G6pXHuo8xZC03t6F8ywjFoD3lbJbutc+tc+yXJIrA" "cyEAOhdk0KdRvK/RDlVJQS02F/eXEovAnwU/lGYEifYuLelEtpxiplCAT2oMFkSRbzxqsvg990jbAdrtaHgmIicRal3P53VJJGQ3v+21dJFKjkwgAxve94FaXchvJSUKonQn/VBnuXgWXJQsIvPvQIDAQAB;" ) You can either change your NS records to ns1.heliohost.org and ns2.heliohost.org or copy those into your external DNS provider.

You can temporarily change the nameservers to ns1.heliohost.org and ns2.heliohost.org and once DKIM, SPF and DMARC have been setup on the domain, you can just copy the records for use with cloudflare and switch the nameservers back after you're finished. Escalating so a root admin can setup the records for you.

Subdomains added. it can take up to 2 hours for them to start working.

Your current balance is $6.4075 plus $15 plus $3 bonus equals $24.4075. Based on your load from the previous 30 days this should last you until 2026-11-07. If your load decreases it could last longer, if your load increases it could run out in less time. Thanks for increasing your Morty balance.

This support request is being escalated to our root admins.

Thanks

Working for me. if it still persists, try clearing your browsers cache. Usually 503 errors after changing settings or increasing disk space like in this scenario need an Apache restart to resolve.

I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

This support request is being escalated to our root admins.

Earth VPS is $15 per month and you paid $10 for the Morty account, so that will last you about 20 days. This link will allow you to set up a $15 per month subscription with a 20 day free trial period at the beginning since you already paid $10. https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FAPWJ54ESVHXQ I have already deleted your Morty account, and started your Earth VPS building using the same username and password as you picked when you signed up for Morty. Building the VPS and running all the latest updates takes 10-30 minutes, and you'll receive an email when it is done. If you're having trouble logging in after receiving the email you should be able to reset the password at https://heliohost.org/reset/

An administrator can do this for you. Which VPS plan are you looking to convert to?

Yes, I received it and setup my account again. Thank you. Best Regards,

Sure.

Your account has been unsuspended. Apologies for the inconvenience on this. It may take a little before your site's domain works again.

A backup of your account will be available shortly at https://heliohost.org/backup/ Instructions for unpacking it are here: https://wiki.helionet.org/Account_Backups#How_to_Extract_Your_Account_Data_from_the_Backup_File To be completely honest, I'm surprised this site is even suspended for financial services (this line of our TOS is meant to prohibit things like banking websites, offering loans, etc. Your site looks like it runs entirely on fake money and even has a disclaimer as such, though I was not the one who suspended it. Crypto sites that are properly designed using Web3 or similar technologies inherently do not have the same data security issues (and associated regulations) that regular financial services face (which is what that line aims to address, though that said the same sorts of risks and scams can apply such as transactions meant to drain a wallet, phishing sites, etc.). If anything, by looking at the code, I'd think the online gambling line of our TOS is more of an issue than financial services (due to the presence of play.html...online gambling with any form of real money or crypto is banned in CA where our servers are located, so we are forced to prohibit that). I'll let Krydos answer the question on what he wants removed since he suspended it.

The backup of the atlas folder and process.php have been uploaded and are in your home folder. I've also re-added the boomarenio.site domain for you that was on your old account. The domain may take up to 2 hours to function.

Looks good! You could also just use the nameservers if you wanted to, that way if the server IPs ever change, you don't need to change your DNS to the new IPs. The server IPs do not change often, I've only seen this done to mitigate a sudden DDOS attack. It can take 24-48 hours for DNS to propagate (although personally, mine has never taken that long), but when I check your new domain with dnschecker, it looks to have propagated already! For others who may find this post, we have info on how to check that DNS is properly configured in our Wiki here: https://wiki.helionet.org/Namecheap_DNS_Records#Wait_24_-_48_hours_for_DNS_Propagation

I’ll upload the files we kept later this afternoon for you when I get to my PC. Once I do so, you’ll see them sitting in your home folder.

I've added those domains to your account for you. Please note that it may take up to 2 hours for the domain changes to take effect, and they will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours they don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

It was suspended specifically because you set a job to run every 5 minutes to start your bot. This is not a recommended or supported way to do this. The bot itself was perfectly fine and caused basically no load...just start it once (manually) and let it run and do its thing. Stop and restart whenever you update the code. It is best practice to not run a script every few minutes to start it over and over, as doing so causes tons of load (using shell commands is load-heavy, so running them repeatedly just wastes your daily CPU allotment, this is one of a few reasons why exec is disabled for PHP via Apache). Please do not do this again. The recommended ways to start and stop a bot can be seen here (this article is for discord but the concepts apply to other Python-based bots as well): https://wiki.helionet.org/Discord_Bot#Starting_and_Stopping_Your_Bot I've deleted the scheduled task and unsuspended you. It may take a few minutes before you can log in again.