Leaderboard

HelioHost is happy to announce that we're disabling ads across all of our websites and hosting plans, including the free Johnny plan, starting now. Back in 2008 through 2016 or so HelioHost was 100% funded by ads, and we made so much ad revenue that we even managed to save up quite a bit of money in our bank account too. It might come as a shock to some of you, but it isn't free for us to provide free hosting, so we still have to pay for stuff like electricity and internet access. As the years went by Adsense kept paying less less and less each year, and our bills kept adding up to be higher than the ad revenue. So our bank accounts kept dwindling lower and lower. There were a few scary years in there where we had to make some hard decisions whether or not to just give up and shut down entirely. We didn't think anyone would be willing to donate to us, but we didn't really have a lot of other options, so starting in 2016 we began asking for donations. We were then, and still are, completely shocked by how generous people can be. After finishing a record setting fundraiser to purchase a new server earlier this year, we discussed it and decided that we don't need ads at all anymore. As long as people keep donating towards our non-profit mission to provide free or low cost hosting, we don't need to bombard you with annoying advertisements. Thank you to all of our donors for making this possible.

You've probably heard of Apache and Nginx, but have you heard about Caddy? In this video we show you how to install the Caddy webserver software on your VPS. Caddy is known for issuing SSL certificates automatically, and being easier to configure than his more famous relatives. It's worth checking out! https://youtu.be/Vq-cKnQGevU It's been a bit since we released a new video, but hopefully you enjoy this one. Some users find it much easier to follow a video guide rather than reading the text guides we have at https://wiki.helionet.org/ Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

One of the most common questions we get is "Can I run a Minecraft server on HelioHost?" The answer is yes, and we've made a video tutorial on how to get started. https://youtu.be/JAXDD7VYHUk We are going to try to continue releasing new videos every 2 weeks, because some users find it much easier to follow a video guide rather than reading the text guides we have at https://wiki.helionet.org/ Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

We have made some changes to the Tommy server to help reduce the number of 503 errors, and speed up the execution of PHP scripts. The feedback we've gotten so far seems to indicate that it is working. We have also noticed that the changes have sped up the time it takes for Apache to restart which should reduce downtime as well. Since the DDoS was targeting the webmail subdomain of random domains hosted on Tommy we just went through and disabled Roundcube on every account. We figure most people probably don't even use the webmail anyways so it is a waste of system resources to have it on by default. If you regularly use Roundcube webmail you can re-enable it yourself on your domain if you need to. Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > Ok After enabling webmail again you will need to wait for up to 2 hours for an Apache restart before it will work. In the meantime if you go to webmail.yourdomain.helioho.st it will show the queued page with an estimate of when webmail should start working again. We will also be disabling webmail on Johnny to help with the 503 errors on that server too. We will likely need to disable free signups for a day or so because the server gets really slow while all the webmails are being disabled so account creations tend to time out. Let us know if you have noticed an improvement on the PHP performance of Tommy, or if you have any questions.

Over the past week or so both Johnny and Tommy have been experiencing occasional slow loading and 503 errors on PHP pages from time to time. This is definitely not normal because we've been using Plesk since 2021 and none of us can even remember the last time we saw a 503 error, and then suddenly they are happening quite frequently on these two servers. We are investigating the issue, and are hoping to resolve it soon. In the meantime, here are some ideas you can do to improve the uptime of your PHP based website. 1. Morty hasn't been affected at all by the 503 errors on PHP pages at all so far, so this is a great time to upgrade to our fastest flagship server starting at only $1 per month. You can check out the discounted Morty packages at https://heliohost.org/dashboard/move/ and move yourself over without talking to an admin by using our fully automated upgrade process with zero downtime for your website if you're interested in trying it out. 2. VPS also have not been affected by the 503 errors either. They start at $4 per month, and aren't affected by other users on the same server as you, because on a VPS you're the only user. Being able to have root SSH access is also a great perk of being a VPS customer. You can check out the plans at https://heliohost.org/vps/ 3. If you don't want to upgrade it is possible for some PHP websites to be converted to static websites. Since it is only PHP being affected by these 503 errors converting your site to use only static html, Javascript, and CSS will allow your website to load faster, have less errors, cause less server load, and greatly reduce the chance of your site getting hacked. It's not possible for all websites to be converted though so this isn't an option for everyone. 4. You could also switch to a language other than PHP. For instance, Python websites using CGI, Django, or Flask haven't been affected by the 503 errors at all. Node.js hasn't been affected by the 503 errors either, but if you decide to try Node.js we recommend keeping a close eye on your load graph at https://heliohost.org/dashboard/load/ because it's easy to go over your 200 GB memory limit. In order to diagnose these 503 errors, the first step we're going to take is implementing additional logging and performance monitoring so we can see exactly when and why the errors are occurring. Let us know if you have any questions, or have any additional information to assist in our investigation.

HelioHost is happy to announce that we now support PHP 8.5 on the Morty plan. The Tommy plan will be upgraded to have PHP 8.5 soon, and after that Johnny will have it installed too.

Should be fixed. /tmp was full again...

Here is the second video in our Minecraft series. This video documents how to set up a modded Minecraft server on a HelioHost VPS. https://youtu.be/Fgmzvrtu7sA We are going to try to continue releasing new videos every 2 weeks, because some users find it much easier to follow a video guide rather than reading the text guides we have at https://wiki.helionet.org/ Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

it reflected now. thanks @MoneyBroz!

found it, @Krydos! Github Webhooks - Heliohost Wiki I can't contain my excitement right now, haha. thanks for adding it on wiki.

Happy Memorial Day everyone! HelioHost has released a new YouTube video on how to issue a Google Trust Services certificate on a VPS. Check it out and subscribe at https://youtu.be/qXp6pw_aV0w We are going to try to continue releasing new videos every 2 weeks, because some users find it much easier to follow a video guide rather than reading the text guides we have at https://wiki.helionet.org/ Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

One of the biggest problems on forums these days is lack of good forum etiquette. What some of the newer users of message boards don't understand is that forums have a very different environment from a chatroom, an instant message conversation, or even an email correspondence. Users of respectable message boards are expected to act maturely. And therefore, to help some of our newer users, I have created this guide to maintaining good forum etiquette. Use spelling and grammar correctly. Always capitalize the first letter in a sentence, even if you only have one to post. Always use periods. Capitalize only when necessary. Remember, all caps means you're yelling. Use commas and punctuation marks. The only excuse you can have for bad spelling or grammar is that you are not a native of an English-speaking country, and even then, you should do your best to learn English.Don't post just to up your post count. In fact, don't even pay attention to your post count. The senior members of a forum aren't respected because they have lots of posts, but because they are good contributors. You should strive to do the same.When you post, make it in-depth. Never just say "I agree" or "Good idea." Describe your idea. Say "I agree because..." or "Good idea. I think..." We want to hear a developed opinion, not just a short statement. Two or three word posts aren't really contributing anything to the forum.Know what you're talking about. Most forums are a community of experts and enthusiasts, and they love to discuss their passions. However, if you go into a topic you don't know much about and say something ignorant, it'll really tick them off. Especially if you stated it with authority.Never ask someone a question you can could easily get answered through a search engine or an encyclopedia. People expect you to find things out on your own instead of getting other members to do it for you. Laziness is frowned upon.Make sure never to turn a topic into back-and-forth conversations on random things. Topics are made for a reason - to discuss something. If you go into a topic and turn it into something completely irrelevant from what it was intended to discuss, you're only ruining it for the users who seriously want to discuss that topic.Don't just go through every topic in a forum posting in each one. Most people will find it hard to believe that you actually have something important to contribute to a topic if you post all over the place.Don't overdramatize unimportant things. There is no need to post a sorry thread if you broke a rule, or make a big deal when something doesn't apply to you. If you made a mistake, no big deal. If you follow these rules, people will forget all about it in a month or so.Don't freak out if no one responds. People have things they need to deal with outside of HelioNet. If you have a question and it has gone several days without being answered, kindly bump the thread up so others may see it.These are just the basics of forum etiquette. You'll learn much more as you post and interact with the community. We won't chastise you for a mistake, but we expect you to do your best to follow this guide. Good luck, and happy foruming © Copyright Helio Networks 2006-2009

When asking for a domain to be added, please make sure to provide the full addon domain name you want, including the top-level domain (TLD): If you're using HelioHost's domains, specify either helioho.st or heliohost.us If you've purchased a custom domain, specify the TLD (such as .com, .net, etc.) Since your current main domain is one of the free HelioHost domains ending heliohost.us, I guessed that you meant you wanted butangfindr.heliohost.us added, and I have now added this to your account. 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 If this is not the domain you wanted added, please confirm the full domain including TLD. You can find more details on how to request addon domains, and all the details that should be included in your request, in our technical documentation Wiki site on this page: https://wiki.helionet.org/Addon_Domains#How_can_I_create_an_Addon_Domain?

Domains added. They can take up to 2 hours to function.

Installed. https://php83.krydos3.heliohost.org/

So you're trying to consolidate existing properties on Google...got it. Record added.

Set. root@control [~]# dig +noall +answer -x 65.19.154.91 91.154.19.65.in-addr.arpa. 21600 IN CNAME 91.subnet64.154.19.65.in-addr.arpa. 91.subnet64.154.19.65.in-addr.arpa. 14400 IN PTR mail.bochard.net. root@control [~]# dig +noall +answer -x 2001:470:1:1ee::124 4.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.e.e.1.0.1.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 14400 IN PTR mail.bochard.net.

This support request is being escalated to our root admins.

Understood. That should be fine, just make sure it's clear that your sites are demos (e.g. put a demo notice on them or the like).

You had several backups taking up a total of about 741 MB of space. I deleted those for you. If you have some scheduled backups you may want to disable those, or script them so they send the backup somewhere external because any undeleted backups count towards your 1000 MB limit. If 1000 MB isn't enough you can increase the storage space yourself with the link MoneyBroz posted. Are you able to login now?

This sort of traffic is basically normal for any website that's been around for more than a few weeks. It's almost entirely malicious bots that are searching for things like a vulnerable Wordpress installation to break into or configuration files with database credentials so they can steal your data. The nginx errors are usually because the server is overloaded. That's pretty normal for Johnny when server load is up. Apache restarts can also cause these. They're less of an issue on Tommy and nonexistent on Morty. We generally just advise users to block unwanted traffic like this in .htaccess if they are causing load issues, though in your case you said they're hitting nonexistent files and getting 404 errors, which cause so little load that you likely won't even see it register on the load chart. We do not have an edge firewall or similar (we can't afford one due to our funding structure), though the server itself has a software firewall that we've used in severe cases to address an account under attack. If you're would like, you can also file an abuse report with the owners of the incoming IP addresses in question. You'll need to find the company that owns the IP (pretty easy to do by googling it), then follow whatever that company provides for an abuse complaint. I've had success reporting addresses that are based in the US and EU, but you're unlikely to receive responses from hosting companies in countries like Russia and China (if they even accept abuse reports), where this sort of activity is tolerated (if not legal).

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

Krydos can do this for you.

You can start by answering simple questions that users ask, such as how to add a domain or why is my website showing 504 errors for example. Most of these answers are found on the wiki. Eventually if you continue to be helpful you can get promoted to helper and even a Moderator, that's how all of us started out.

I've checked with the rest of the staff and because we're switching the main domain to be an addon domain, it's best to do a full account reset so the domain switching doesn't break anything on your account. I've now reset your account, and you should receive an email shortly so you can take the next steps to recreate it. Please make sure to enter the domain you want as your new main domain. Once the account has been recreated, let us know and we can then add the other addon domains and the subdomains you wanted. I made a backup before the reset, so if you discover you need any of your 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

Here is how your storage space is being used. Backups 0 MB Emails 0 MB Files 259.78 MB Trash .95 MB Logs 0 MB PSQL 0 MB MariaDB 20.73 MB Total 281.46 MB 1.5M /home/pokemonwawi.helioho.st/httpdocs 224M /home/pokemonwawi.helioho.st/disneywawi.helioho.st 12M /home/pokemonwawi.helioho.st/sora.moss.helioho.st 9.4M /home/pokemonwawi.helioho.st/maplewawi.helioho.st 656K /home/pokemonwawi.helioho.st/savanna.drumz.helioho.st 156K /home/pokemonwawi.helioho.st/mycrypto.helioho.st 676K /home/pokemonwawi.helioho.st/pricebot.helioho.st 13M /home/pokemonwawi.helioho.st/test.helioho.st 32K /home/pokemonwawi.helioho.st/test2.helioho.st 124K /home/pokemonwawi.helioho.st/pokepricebot.helioho.st 24K /home/pokemonwawi.helioho.st/.nodenv 4.0K /home/pokemonwawi.helioho.st/.phpenv 120K /home/pokemonwawi.helioho.st/.rbenv 12K /home/pokemonwawi.helioho.st/.npm Your total storage usage is only 281 MB so I guess you already figured out where the 700 MB was. One thing that confuses people frequently, is if you delete files it can take up to 24 hours for the storage total to reflect the change. So if you're using 700 MB, and then you delete 419 MB Plesk can continue to report that you're still using 700 MB for up to 24 hours even though the files have already been deleted.

Thanks for the donation. Your storage space on the hhfn account has been increased by 2000 MB to 5000 MB total.

Thank you, and I will keep this in mind. Have a great weekend, Mike

thank you can you also install this modules pls it's not there " redis"

Your account is suspended for High Server Usage, specifically using 200.38 GB memory when the limit is 200 GB. Node is one of the top reasons for users getting their accounts suspended, since it uses a lot of server resources. We have a Node.js guidance page in the Wiki here: https://wiki.helionet.org/Node.js and if you use Node, we recommend you structure your app in the same way as the example app in the tutorial. Following this structure will make sure your Node app uses Passenger, to help try to keep the load within the limits allowed on the shared hosting server. I have unsuspended the account now. Please fix the issue quickly or else the same high load is likely to happen, which will lead to the system suspending your account again and there are a limited number of unsuspensions that can take place for the same reason.

Not sure if I am at the right section of the customer support to report this but just made a donation Transaction ID: 34611125JC9001140 Does my files automatically get back to Morty or do I have to request it? I did receive the notification to increase my donation but it slipped my mind until now. Thanks Duuuhhhh... just received the email about account moving to new server. Guess that solves the above.... Suhorrrrry....

Thank you for the fast reply and help. I will do what is needed, thanks.

Related email support case: Morty accounts are exempt from the multiple account policy, so no exception is needed for that. Notes have been added to the account indicating that he gave approval for you to maintain it.

Yeah, it's good that you told us first. When people login to multiple accounts they tend to get suspended because you're only allowed to have one account. If your client wants to grant you access to login to their account they can let us know from their own email address, and then you can give us support requests for either account.

I've changed your main domain to "noterapida.com.ar" and added "igna.site" as an addon domain. You'll need to create an A/AAAA record or switch to HelioHost's nameservers for noterapida.com.ar to work. Changes should take effect in about an hour.

sorry for the mistake, you are right I activated marty ? thanks for adding the domain I changed the dns, now I wait , all is well thanks you

questlog.tenkyuu.dev has been added, and sandbox.tenkyuu.dev was removed. It can take up to 2 hours for the new domain to start working. Since removing a domain from your account can cause files for that domain to be deleted as well, I created a backup of your account before the removal, which you can download at https://heliohost.org/backup/

Thank you to everyone who helped beta test our WSGI restart access for Flask and Django apps. We now have enough data from the testing to end the beta. We have determined that enabling WSGI restart access uses at a minimum 260 GB memory per day per domain. Obviously this is a death sentence for any Tommy or Johnny account, since you're only allowed to use 200 GB per day, so WSGI restart access is now a feature only available on Morty. We have gone through all of the accounts on Morty, Tommy, and Johnny and disabled the WSGI restart access so there are no surprise suspensions or surprise bills. If you're on Morty and your WSGI access was removed please feel free to re-request it. If you do request WSGI restart access on Morty for one domain be aware that you're probably looking at a bill of $1.91 or more per month as long as it is enabled. If you enable WSGI restart access on two Morty domains you'll probably end up paying about $5.86 per month. Being able to clear the server cache is definitely helpful for debugging your Flask or Django app, so if you want to enable WSGI restart access on Morty temporarily for debugging, and then disable it for the lower bill later, that is fine with us. Please be aware that we attempt to respond to all support requests as quickly as possible, usually within an hour or two, but occasionally it can take up to 24 hours to complete if it's a holiday, the middle of the night, we're all busy, etc. etc. 24 hours of WSGI restart access only costs about 3 cents though, so no need to panic.

Thank you for the information. How will the billing and payment be handled to keep WSGI activated? Considering the estimated cost of $5.86 to keep the restart active for two domains, would migrating to a VPS be the best option in this case?

Just yours That's what we are investigating.

I checked my Tommy account and the Scheduled Tasks option isn't showing up for me either. Thanks for letting us know. ? I've flagged this in the staff channel, and a root admin will update this thread once they've had a chance to look into the issue.

We don't know what's causing this problem, but it affects everyone on Tommy and Johnny. It started a few weeks ago and we initially thought it was affecting only a few users and was related to a DDoS against our webmail service, but that doesn't seem to be the case as the issue is now widespread. Investigation into this issue is ongoing. Please see this News posting for more information and updates as they become available: https://helionet.org/index/topic/64305-503-errors/?do=getNewComment

Your account was suspended for High Server Usage due to using 200.28 GB memory when the daily limit is 200 GB. I have unsuspended the account now, please give it a few moments to get back up and running. Please fix the issue quickly since if there are no code changes made, it's very likely the system will suspend your account again. If you're not sure how to reduce your account load, let us know more about what apps / programming language you're using and we can offer tips to try to keep the load down. For example, WordPress and Node are among the top reasons for accounts to be suspended.

Hello and good luck to you all. Was a good mess, the consequences of which eliminating takes a long time. But now to the point. I have already informed you about this and then it seemed to have been fixed, but everything is stil the same for me, i.e. there are difficulties with changing passwords and they do not synchronize automatically until now. I have also deleted all cookies, cleared all caches, etc but still no success.. So, so far I have one password for Plesk login, another password for ftp/ftps and a third password for the forum. And there is no way to change them. Although everything is OK until I save and log out, but in reality nothing was saved and everywhere everything is the old way. I think you will find the reason and also the solution someday. This is just an info thought to let you know that this problem still exists. Good luck again and all the best.

Oh ok, thanks for fixing the website

It still not... I dunno why is this not working

It not only tells people this in the email when they are moved, but it actually mentions it in BOTH emails when your account begins to move and when the move is complete.

this is after i clear my cache

There isn't an ETA for that, but i assume around 2 - 3 weeks or so once it's started. maybe longer.

Johnny's Apache is broken due to the disk issues as mentioned in a previous News post. Plesk is sort of working on Johnny, but any accounts on Johnny that do still exist will not work properly. Any changes you make on a Johnny account at this point will be deleted as part of the Johnny server rebuild in a few days. For the time being, your only option for a working account is to move to Tommy or buy a VPS.