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.

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.

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.

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

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!

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.

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

Our old nameservers broke, and we had to transfer all of the zone records to the new DNS servers. It seems like some of the zone records didn't get transferred correctly though. I flagged your post in the Staff channel, and the DNS has been recreated for you. Your website loads for me now. If you can't see it, please try clearing your browser cache. If you're a Discord user, you can keep an eye on the HelioHost #News channel for updates when maintenance is happening. If you haven't yet joined the Discord, here's the link to join if you want. For other users who may see this post: If your website is down and it says DNS_PROBE or some similar error please let us know (by making a new post in the support section at: HelioHost > Customer Service) which domain(s) of yours is having the problem, so the DNS can be recreated for you.

Thanks. You guys are awesome!

Is the VPS running faster now?

Indeed it is mod security. You can see the error in Plesk in the Logs for your domain. ModSecurity: Access denied with code 403 (phase 1). Pattern match "\\\\D" at TX:1. [file "/etc/httpd/conf/modsecurity.d/rules/comodo_free/30_Apps_OtherApps.conf"] [line "4530"] [id "240950"] [rev "2"] [msg "COMODO WAF: XSS & SQL injection vulnerability in Pragyan CMS 3.0 (CVE-2015-1471)||salt.wiki.gd|F|2"] [severity "CRITICAL"] [tag "CWAF"] [tag "OtherApps"] [hostname "salt.wiki.gd"] [uri "/User:Lia"] [unique_id "aZnLyrW2MUbixOOUfFzWWQAAAok"], referer: https://helionet.org/ You can actually whitelist these yourself in the Web Application Firewall page of Plesk. I went ahead and added rule 240950 to the exception list for you. The changes will take 2 hours to take effect.

thank you, team.

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

Domain added. Please be sure to configure DNS. The domain can take up to 2 hours to function.

No problem. Let us know if you need help with anything else.

Domains must have a suffix or TLD on them. Do you want these to be montiforever.helioho.st and svariongames.helioho.st?

It doesn't work for numerous reasons: First, you apparently deleted and recreated your cgi-bin folder, which breaks the ability to run CGI on the account. Second, you had the permissions on test.py set to 777 when they need to be 750. Third, you translated the header values. Headers and server commands must be in English because these are machine-read values defined as part of international standards. print("Tipo di contenuto: testo/html\n\n") I've fixed all the issues for you and the script is now working.

I've never used phpMyAdmin on Hestia before, but I would assume you can login using your database username and database password.

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

Thanks!

TL;DR: How should one follow through with additional CSRs created via Plesk when submitting them to CAs? Webroot seems to be unavailable due to nginx blocking access to /.well-known/acme-challenge. Hey! I apologize if this question has been asked before in the forums, but I could not find a proper answer to what I've been looking for after a day or two of messing around with things. I would like to know what would be the correct way to get a CSR emitted via Plesk to be signed from a CA like Let's Encrypt. After looking through the wiki, I found out that we're using SSL It! to automatically generate SSL certificates for our websites, and that's great! But I'd like to issue a second certificate, separate from the one used by the website (for security reasons) for me to use on TLS authorization during connections in my applications. They currently run in my own computer (since I don't own a VPS yet), and it would be nice to be able to validate that I'm indeed connecting to the right server, which would be impossible with a self-signed certificate. Thing is, with the old cPanel (after verifying in Ashoat's old GitHub heliohost-wiki repo - Link), it was possible to create a /.well-known/acme-challenge/<requested-file> path that was publicly accessible - and therefore, would pass the webroot challenge of ACME clients like certbot. After the move to Plesk, and I assume with the advent of other changes, nginx has been set to forbid access to the acme-challenge path and throw a 403, and I'm unaware if there is a way to properly allow access to files within that path. I appreciate the time you guys put into reading this wall of text (I've put a little TL;DR up there if it ends up being a lot..), and I'm welcome to both suggestions and opinions as to what I should be doing, and most importantly: should NOT be doing ? - Fallbork

Remote access enabled.

Soo as it turns out, on Jonny you can safely place your .env file in the root of your app and the server will automatically prevent it from being served to a client. for this sample project, the path is load_dotenv("/home/dkobrin.helioho.st/flask.dkobrin.helioho.st/MyNewFlaskApp/.env") as an extra layer of safety I am also adding the following to my .htaccess file instructing Apache to deny requests for .env files #hide .env files from http access <FilesMatch ".env"> Order allow,deny Deny from all </FilesMatch>

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

it's okay now. thank youuuu @Unknown025!!!

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.

oopss... haha. I made mistake, I should be mentioning wolstech, but I accidentally mentioned kryd0s instead hahahhaa. but yeahhh. thanks a lot @wolstech, @Krydos, @KazVee, and all others!!!

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

Unsuspended. it may take a few minutes to start working again.

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.

First, stop creating posts every few hours. Support requests can take 24-48 hours for a response or longer (especially since it's a holiday weekend here in the USA). We're volunteers and not around all the time...we have real lives and are not paid to run HelioHost. Every time you make another post, you're moved to the back of the line for support./ We always work the oldest requests first since they've been waiting patiently the longest. If you continue to spam the forum, you may be banned from support. Second, you can't have an account for a family member because: You previously violated the multiple account policy. You didn't request and receive written permission in advance as required by the Terns of Service Data for the third account suggests a possible attempt to evade enforcement of the TOS by using a VPN. The account pokemonwawi has been unsuspended again. You can keep this account, and ONLY this account. DO NOT attempt to create any additional accounts, and DO NOT request the unsuspension of any other account. A third violation for multiple accounts may result in a permanent ban. Also, you do realize you can host more than one website on a single account right? If you want more domains, just ask. A single user can have up to 10 domains.

Users have a concurrent connection limit of 10 for mariadb, so this would be a reduction.

Thank you for the clear answer. Ok...so your issue is that your friend isn't allowed to do that per our terms of service. Accounts must be created and maintained ONLY by the actual owner unless permission is requested in advance, so the account is in violation simply because you asked him to violate the TOS on your behalf. If you would like your own account, you are welcome to it, but you will need to sign up under your own email address, and under no circumstances are you allowed to share a PC, network connection, or content with him. He is not allowed to maintain the account for you, and you cannot store any content for his website (or vice versa). If we detect this again, both accounts will be permanently banned from our service. Would you like me to delete the voltars account so you can sign up again under your own email address? If so, let me know what email address you would like to use and I'll reinvite you for your own account.

You've got to admit this does not scream "I'm a legitimate email provider" We see criminals, phishers, spammers, etc. sign up with email addresses that when checked have messages like this all the time. Unsuspended.

Sure. Account reflux has been unsuspended. It may take a few minutes to work again. The other account can just be abandoned. It will delete itself in time since it's suspended. If you'd like to request it be deleted, please post from its matching forum account and we can do that.

A huge thank you goes out to the 66 generous donors who have helped us complete our latest fundraiser in record time. Based on previous fundraisers we expected it to take about 6 months to raise the $2500 to buy a new server, but we have already reached our goal in exactly 1 month. If you're a donor and haven't received your thank you gifts yet, please let us know so we can get that set up for you. Now that we have raised the funds that we asked for, we will use the money to buy a new server with 192 GB memory, 40 CPU cores, and 10.5 TB of hard drive space named Stevie. Since we're a small non-profit run by volunteers it will take at least a few months to get everything set up, but we'll make an announcement when we're ready for the Java beta testers to start helping out testing the new server. We're also really excited to be able to increase the amount of free hosting space that we have. Johnny continues to fill in less than a second at both noon and midnight most days even though we've increased the number of available free accounts granted each day by quite a bit. This fundraiser should be able to nearly double the amount of free hosting space that we have. We'll make more announcements as the hardware gets installed, and the new server gets set up. Keep an eye out for the latest HelioHost news.

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.

I see this php error message: PHP Warning: Version warning: Imagick was compiled against Image Magick version 1692 but version 1693 is loaded. Imagick will run but may behave surprisingly in Unknown on line 0 Can you reproduce this error with any php file?

The fonts are stored under /blitzortung/fonts/ . Does this help you to diagnose the error?

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.

Please clear your cache. The domain plj.my.id is working for me.

Thanks Sir all good now, wow the server is faster, you are the best

The server is still broken and has not been rebuilt yet. We just recovered the data and made it available in backup form. The server will likely take several additional weeks to rebuild. Once that’s done, the plan is to replace that message when logging in with the option to either restore your backup into an account, or reinvite yourself without waiting for open signups if there is no backup available for you.