Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/16/26 in all areas

  1. 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.
    2 points
  2. 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.
    1 point
  3. This support request is being escalated to our root admins.
    1 point
  4. 1 point
  5. I'll go ahead and mark this as [Solved] since there are no outstanding queries for support. If you run into any issues, please open a new ticket. Thanks!
    1 point
  6. Please do not post multiple topics for the same issue. Requests can take up to 24 hours to receive a response.
    1 point
  7. 1 point
  8. That's good to know. Those files can vary quite widely by server version and database content, so the fact an off the shelf AI can convert the binary InnoDB database files back into .sql format without issue is quite impressive. Thank you for the info.
    1 point
  9. Nope not mistaken. An alias is exactly what you need if you don't want it to redirect. Alias has been added. Please be sure to configure DNS using our name servers or by using A and AAAA records pointed to the IPs shown in Plesk. The alias can take up to 2 hours to function.
    1 point
  10. .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).
    1 point
  11. 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.
    1 point
  12. 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
    1 point
  13. 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.
    1 point
  14. DKIM, SPF, and DMARC have been set up for the domain dark.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. You suspect correctly. It supports Johnny domains now.
    1 point
  15. 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).
    1 point
  16. Also, please note that once you change it in Plesk it can take several hours before the dashboard reflects the change.
    1 point
  17. An administrator will be able to do this for you.
    1 point
  18. 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
    1 point
  19. 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.
    1 point
  20. Domain changed. It may take several hours to start working.
    1 point
  21. 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/
    1 point
  22. 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.
    1 point
  23. 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.
    1 point
  24. 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.
    1 point
  25. 24 hours... ๐Ÿ˜“ Well, now we know if someone else has trouble with git, I guess! Glad it's all sorted out! ๐Ÿ™‚
    1 point
  26. Thank you so much for your help! I wanted to let you know that the repository has finally loaded. It took about 24 hours to finish, but it is no longer stuck in the queue. Since it loaded, we won't need to do the account reset. Thank you again for your support!
    1 point
  27. 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
    1 point
  28. Domain added. It can take up to 2 hours to start working.
    1 point
  29. Sure. That domain has been added back.
    1 point
  30. That domain has already been added.
    1 point
  31. 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.
    1 point
  32. thank you. Working now. Have a great day, you made mine
    1 point
  33. Installed. You can see the current list of installed modules for Morty's Python 3.14 at https://morty2-info.heliohost.org/pyinfo/info3.14.py
    1 point
  34. 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.
    1 point
  35. Please post the full, uncensored URL that's experiencing this problem so we can review the issue.
    1 point
  36. There is no ETA for when adding/removing domains can be handled by users. Please see this page in the technical documenation Wiki which explains more: https://wiki.helionet.org/Addon_Domains#Addon_Domains Users cannot yet manage domains on their account themselves. We plan to add this feature in the future, but there is no ETA for when it may be implemented.You can read more about ETAs here: https://wiki.helionet.org/ETA In the meantime, HelioHost staff will be happy to help you manage your addon domains. Since there are very few unpaid volunteer staff spending their time keeping HelioHost running, requests for features and fixes have to be triaged and handled in a priority order. I think right now, the focus is on getting the servers fixed. There's also Java language support in the works, and the ability for users to add/remove their own domains is on our to-do list as well. In the meantime, to free up staff time to implement the necessary repairs and new features even quicker, you're welcome to help lessen the load by answering other users' questions if you can. Most of the information about HelioHost can be found in the Wiki, which can be found here and has a great keyword search function: https://wiki.helionet.org/ If there's something you searched for in the Wiki and can't find an answer to, we welcome user-created contributions to the technical documentation as well, so just let us know you'd like a new account to start adding information to the Wiki, and we'll definitely be happy to set that up for you, too.
    1 point
  37. It's no problem at all. We just don't want to miss anyone's requests by accident! ๐Ÿ˜…
    1 point
  38. Thank your very much for the kindest advice๐Ÿ™ I am sorry for replying to the thread marked as solved. Won't happen again. ๐Ÿ™
    1 point
  39. Yeah, sorry about that. Had the issue with Bad Gateway, no webmail etc but Plesk worked and FTP. Thats why i thought it might be related and hooked up on the other Thread. Makes sense to open a seperate one. Next time And yeah, suddenly it started working again. So it was maybe just a hiccup. Should have waited another 10 minutes Thanks for the compliment about the car ๐Ÿฅฐ Actually we have 2 of them. Same build. Both in the family for 17 years now
    1 point
  40. I split your request to make a new thread since it's easier to troubleshoot different issues separately. I checked your site and it loaded for me (amazing car! ๐Ÿคฉ). Looks like you resolved the issue yourself so I'll mark this as [Solved]. Next time, if you run into an issue on your account, unless it seems like something that could be hosting-related or server-wide (which I can see in this case why you thought it could be a Tommy server issue!), please go ahead and make a new thread so your posts don't get accidentally missed in a request created by another user. If it does turn out to be a common issue, admins can always merge threads later and tell everyone they're affected by the same issue.
    1 point
  41. Not only have you bumped your own post in this thread (which can delay responses to you since we tend to look for the oldest timestamp first), but you've also posted the same question in another thread here: https://helionet.org/index/topic/67733-when-it-rains-it-pours/#findComment-301442 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.
    1 point
  42. Missing DNS zone fixed. It may take a little while before the changes propagate.
    1 point
  43. First of all, sorry for the long downtime on our main website. Over the past few years our main database has just been getting slower and slower. It was last rebuilt in 2017 so it was well overdue for an upgrade. A few days ago the main database was so slow that we decided to take it offline, and rebuild it with a modern operating system and up-to-date software. We expected the downtime to last a few hours, but then during the upgrade everything fell apart. While Cody was down, his twin brother Brody got so sad he died too. This happens sometimes with twins because they can't live without each other, which is cute but also very tragic. So then, with both a dead Cody and a dead Brody, we had no nameservers, no main database, no website, no forum, no wiki, etc etc etc. But here at HelioHost we never give up. No matter how many servers explode, or how many evil for-profit corporations try to destroy us we will never give up. It took a few days, but our main website is back online, both of our nameservers are back online, our forum is working again, and a lot of the stuff going on behind the scenes are working again too. That said, there is still plenty of stuff that isn't working yet. The main issue seems to be that during the upgrade of the nameservers a lot of DNS zones got lost, so some websites are offline. If your domain gives a DNS error when you try to visit it in a browser let us know and we can take a look. It usually only takes a few seconds to recreate the DNS for you. We're still working on getting everything functional again, but we're making progress. Thanks for everyone's patience during this crazy rebuild.
    1 point
×
×
  • Create New...