Leaderboard

The free plan is now back, and better than ever! The Johnny rebuild has been completed and free signups will be opening in about 30 minutes. If you don't already have an account you can signup at https://heliohost.org/signup/ We expect signups to fill pretty quickly, so be ready to click as fast as you can. On May 9th we emailed all of the active Johnny users, and offered them a free trial on Morty to get their websites back online during the rebuild. If you are one of those free users currently on Morty we will be emailing you to ask if you want to stay on Morty or go back to Johnny. If you want to stay on Morty you can use this link https://buy.stripe.com/7sI8wOe4p40y9q0147 to pay $5 which will last about 6 months without overages. If you make a payment let us know so we can make sure it gets applied to your account. If we don't hear back from your we will move you to Johnny automatically in a few days. If you decided not to accept a free trial, you can recreate your Johnny account by going to https://heliohost.org/status/ and entering your email or username. The website will recreate your account for you on the new Johnny server. The new account will be empty so if you want to restore your previous website you'll need to download your backup from https://heliohost.org/backup/ or use a backup that you made yourself. Keep in mind that if your backup is missing anything we may still be able to recover it for you. Just let us know what you're missing, and we can take a look. The new Johnny also has a number of upgrades such as Python 3.14, MariaDB 12.2, PostgreSQL 18.4, etc. If your script isn't working, make sure you're using the correct shebang version. Let us know if you have any questions.

Cool, sounds good. I'm going to mark this as solved, but I understand that webstats still isn't working on Tommy. It's not worth trying to fix it since we're going to be replacing the old Tommy server anyways soon.

I manually ran webstats twice on Tommy and it still didn't update your stats. Tommy is well overdue for a rebuild so it seems like more and more things are breaking. We will be setting up a new Tommy in the next month or two and moving everyone over to it. If you want webstats to work sooner you can upgrade to Morty at https://heliohost.org/dashboard/move/ Since you're here, I have a question for you. Is your site a commercial site? Are you selling cars, or what is the point of your website?

Yeah, that IP is not blocked. Seems like they noticed the loophole you were using and blocked it.

That IP address is not blocked on our end from what I can see. DNS on your domains looks fine (we usually recommend just setting the MX records directly to tommy.heliohost.org for simplicity, but this is not going to cause the issue you're describing and the configuration you're using should work). Krydos can confirm the firewall stuff on our side. If there isn't anything found, this may be an Azure issue.

Your current balance is $6.6407 plus $15 plus $3 bonus brings your new total to $24.6407. Based on your load for the last 30 days your new estimated expiration date is 2026-08-24. If your load increases this could run out sooner or if your load decreases it could last longer though. We'll email you occasionally to let you know how your balance is being used. Thanks for increasing your Morty balance.

This support request is being escalated to our root admins.

Krydos can install this for you.

Thank you, I am forwarding him how to archive the account.

thank you !!!!

This user has been advised repeatedly to stop making duplicate posts: 1st time: Sept 3 2025 6:09AM: https://helionet.org/index/topic/65533-regarding-domain-add-remove/#findComment-293641 2nd time: Sept 3 2025 6:09AM: https://helionet.org/index/topic/65534-regarding-domain-add-remove/#findComment-293642 3rd time: Today June 12 2026 5:44AM: https://helionet.org/index/topic/68266-please-add-python-modules/#findComment-303200 4th time: Today June 12 2026 5:48AM: https://helionet.org/index/topic/68265-add-python-modules/#findComment-303202 @prabhatyadav2003 While you await assistance, kindly review our Three Strike Policy here: https://wiki.helionet.org/Suspension_Policy#Three-Strike_Policy since we've now needed to ask you multiple times to stop making duplicate posts for the same issue. Since all staff are unpaid volunteers who donate their free time outside of real-life commitments (paid job, school, family, etc.) we prefer to eliminate unnecessary duplication of time and work. For guidance on where and how to ask for help, see: https://wiki.helionet.org/FAQ#Where_do_I_ask_for_help? To understand how Community-Powered Technical Support works, visit: https://wiki.helionet.org/FAQ#How_does_community-powered_support_work? For support response timelines (SLAs and ETAs), check: https://wiki.helionet.org/ETA Asking the same question in multiple places can lead to wasted staff time and effort, resulting in slower support timescales for you and other users.

Plesk generates the private key for the DKIM and stores it securely along with the private keys for SSL. When you send an email from Plesk with DKIM enabled it Plesk uses the private key to generate a DKIM signature that remote mail servers can use the public key provided via DNS to verify that the email is legitimate.

Please do not post multiple topics for the same issue. Requests can take up to 24 hours to receive a response.

Please do not create multiple topics for one request. Posting more than one topic on the same request/issue can result in a delay in service to you. You already posted here:

.htaccess file is going to be your best friend here as moneybroz said above. We've had to block these scanners on our own sites as well as help other users with the same (usually on our other plans after they got suspended over it).

Just add these two lines in the .htaccess file for the domain being attacked, deny from 139.59.136.0/24 deny from 146.190.103.0/24 If the attacks continue from this same range, change the above to deny from 139.59.0.0/16 deny from 146.190.0.0/16

No, the backup from May will not contain databases. We were only able to recover the contents of the Home folder as of the day of the crash. The database server was damaged by the crash and associated disk issues, and the majority of the data was lost. If anything at all is recoverable, it's going to be raw server files that represent the table, and you'll need to spend some time trying to extract the data from them. The data will not be something that you can just import into a new account. Escalating to Krydos.

Sorry for the delay. I've been travelling the last few weeks, and somehow managed to miss this one. The requested DNS record has been added. In the future, if you don't receive a reply within 24 hours we encourage users to bump their support requests to make sure we don't miss it.

Invoice sent.

Great to hear you enjoyed the experience here and learn something from it! You should be able to cancel your VPS here: https://heliohost.org/dashboard/cancel/ If that doesn’t work, let us know and I’ll have Krydos cancel it for you.

Installed. You can see the current list of modules and their versions for Morty's Python 3.14 at https://morty2-info.heliohost.org/pyinfo/info3.14.py

Thanks for upgrading. I have set your balance to $24 after the $19 payment and $5 bonus. This should last you about two years without overages. We're going to move you to the upgraded Morty2. Morty2 is actually even faster and has newer software than the old Morty that you were on before, so it's even more of an upgrade.

Remote access enabled. host=65.19.154.90 port=5432 user=dvdbrugnoli_RestaurantManagerADMIN dbname=dvdbrugnoli_RM password=<set in Plesk>

Correct. SQLite3 is actually built into every Python 3.14 by default too, but we recommend using MariaDB or PostgreSQL because they're easier to get working, and better performance. This module is really ancient and doesn't even work with Python 3.0. For Python 3.14 I installed Beautifulsoup4 instead. You can see the current list of installed modules for Johnny's Python 3.14 at https://johnny-info.heliohost.org/pyinfo/info3.14.py

The configuration we recommend is to use the server hostname (tommy.heliohost.org in your case) as the mail server. Plesk loves to suggest using user domains for the mail server, but our experience is that it tends to cause issues. SSL connections for mail not working is a common problem with doing so, and another is that mail clients may refuse to send mail through it for security reasons (the server identifies itself as Tommy regardless of what domain you use to connect, some clients do not like the fact the domain in its settings and the domain the server identifies as don't match).

Weird. The system is unable to set up SPF/DMARC/DKIM on that domain. Keeps saying it can't find it despite the domain obviously existing. Based on the output, I suspect the DKIM setup tool on our side may not be capable of setting this up on Johnny domains (probably due to the rebuild). Flagging for Krydos...

Also, please note that once you change it in Plesk it can take several hours before the dashboard reflects the change.

You can do this yourself in Plesk > Click your username > Edit Profile and change the external email listed to the new one.

Johnny no longer has Python 3.12, which is part of the issue. It has 3.14 now. You'll need to update relevant shebang lines. https://johnny-info.heliohost.org/pyinfo/info3.14.py I'll assume you want these installed for 3.14. Datetime, json, and OS are built-in I believe. Requests is already present. Escalating to have the others installed: sqlite3, Beautifulsoup

DKIM, SPF, and DMARC have been set up for the domain kittforhire.com. 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.

Domain changed. It may take several hours to start working.

2026/05/31 17:06:15 [emerg] 613206#613206: duplicate location "/" in /home/bawantha/conf/web/anonymizer.bawantha-beliwaththa.me/nginx.ssl.conf_flask.conf:1 It looks like you tried to add a custom nginx directive but you are trying to pass a location context to another proxy when Hestia already passes all traffic to Apache on port 8080, i fixed the error, and restarted nginx let us know if the error still persists. to add the proxy to port 5001 back, login to hestia, go to web and then click edit, on anonymizer.bawantha-beliwaththa.me, after that click Advanced options and then change the proxy template to python or node depending on what you are using, and then set 5001 in the backend port setting. i also made a backup of your code before making any changes which you can find in /home/bawantha/

thank you~!

2026-07-24

Domains re-added. They should work within 2 hours. And yeah, I agree that messaging can be confusing especially for users with external DNS who may not realize the domain needs to be added. The page was written with the expectation that users would be using our DNS (which back in our cPanel days was actually a requirement to add the domain). For users who do use our DNS, an unconfigured domain simply doesn't resolve and returns NXDOMAIN instead of that page, so its obvious its not set up. When external DNS is used, it's possible to force an unconfigured domain to resolve, and the server just shows that page because it has no idea what to do with requests for the domain.

Oh yeah, that domain could be an issue if changing it means having to update/replace the firmware on old embedded devices. I'll put it back for now for you as an alias so you have both. It could take up to 2 hours to work, and will show the same content as the .us domain. In the meantime, please update your service/documentation so that new users and updates going forward will access your service through the .us domain instead. There will eventually be a point where we eliminate the remaining .org domains from user accounts.

Thanks for quick reply and Morty2 information. What a difference between free and paid in performance and uptime! I am loving Morty and I am sure I will love Morty2 even more.

I've changed the main domain on 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/Changing_Your_Main_Domain#Custom_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 Since there is a risk of data loss when main domains are changed, I made a full account backup for you before I made the changes, in case you need any files from the old domain. 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

Domain added. It can take up to 2 hours to start working.

Great! Thank you. - This backup has everything. - Stripe works in my country. I'll do some work with the files, then will request an upgrade, once finished. I'll request some paid domains too. I know you have affiliation with Name Cheap, and I got the URL for this.

Sure. That domain has been added back.

Domain changed. It can take up to 2 hours to function.

Fixed. If you delete the document root folder, you'll break the domain. There are special permissions on those folders that you can't set yourself, so even if you recreate the folder, you still have to contact support to have the permissions fixed.

Yeah, that's a lot of emails. Backups 0 MB Emails 728.44 MB Files 245.03 MB Trash 0 MB Logs 23.35 MB PSQL 0 MB MariaDB 0 MB Total 996.82 MB 172K /home/urbanshed.helioho.st/httpdocs 245M /home/urbanshed.helioho.st/urbanshed.in 12K /home/urbanshed.helioho.st/.composer You're at 996 MB out of 1000 MB so you may be able to login quick and start deleting stuff before it goes over the limit again.

Your account was suspended because you exceeded your storage limit. You have 3 options to regain access to your account: You are able to regain access to your account immediately without waiting for an admin by increasing your account's storage space. This storage space upgrade is good for the life of the account, and has no monthly cost. Tell us which files you would like deleted and an admin can delete them for you to get you back under your current storage limit. If you're not sure which files are taking up all of your space an admin can provide a detailed storage space usage report for you. We can also reset your account for you which deletes all files, deletes all settings, and restores your account back to the default state with 0 MB of storage usage.

DNS recreated.

An administrator can check conclusively what is consuming your storage quota, but it's worth noting that any emails or databases you may have also contribute to that same quota. To resolve this issue, you can upgrade your storage at https://heliohost.org/dashboard/, reset your account, or request an administrator delete any excess files.

There is a new Johnny running on the IP which is why you see a login page and johnny certs, but it's still being rebuilt. All the backend stuff has to be configured. When it is finished, we'll likely send invites for users to create new accounts since we can't recover the old ones. Users who took the free Morty trial will eventually be moved back to Johnny too if they decide not to purchase Morty plans.

This user is actually on Tommy and has 7 domains, which is why I asked for the URL. That said, I just realized it's all of his domains, and it's because his IPs on Cloudflare are incorrect. His DNS is set to Morty's IP but the account is on Tommy because he didn't refill his Morty balance. He needs to correct the DNS in Cloudflare on his end to point to Tommy.

Please post the full, uncensored URL that's experiencing this problem so we can review the issue.