HelioHost Wiki - User contributions [en]

Deletion Policy

2026-04-11T01:46:38Z

Krydos: Added full support request deletion section

== Deletion Policy ==

This Deletion Policy describes our policies and procedures on the deletion and removal of your information and data when you use our hosting service or contact support.

== Community Support ==

HelioHost is a non-profit run by volunteers who receive no pay for helping you with your hosting issues or maintaining the servers. We volunteer for this organization because we enjoy it, and believe in the mission of providing free hosting to people who can't afford paid hosting. We aren't owned by a for-profit company, we don't have a full time staff of paid employees, and don't have a quota of how many people we need to force to upgrade each month. If we aren't having fun volunteering, or if you are rude to us, we will go do something more enjoyable for us. We aren't required to volunteer a certain number of hours each week, and we may come and go as we please.

In order to reduce the work required by our volunteers, and in order to recruit new volunteers, all of our support is community based and public. This means if someone else has had the same issue as you, we encourage you to search our forum and our wiki to find the solution that worked for other previous users. This also means that regular users can help each other out if they know the answer to someone else's question. All of our volunteers started out as regular users who decided to be helpful and answer other users questions. When we see someone being helpful in the community we sometimes offer them a promotion to give them more tools and more access to be even more helpful.

== Privacy Policy ==

Our Privacy Policy can be read at https://heliohost.org/privacy/ If you have concerns about your privacy, please contact us, and let us know how we can help. We will do everything we can to keep your private data private.

== Private Support ==

We do not currently offer private support, but enough people have expressed interest in private support that we do plan on implementing it in some form in the future. Since private support increases the workload on our volunteers and reduces the helpfulness of our user searchable resources, it will not be free. Therefore, only donors will be allowed to use private support. The exact details of the private support and donation level required to access private support will be announced on our news section when it becomes available. There is currently no ETA on when this will be released.

== Support Request Deletion ==

The whole point of community support is for the support requests to be visible to other users so they can solve their own issues by searching or find solutions to their problems, so deleting support requests is detrimental to that goal. Even if your support request is as simple as "add this domain please" it may be useful for someone who doesn't know how to add domains to their account and finds your post. "Oh, I can just make a post like this to get a new domain added!" Generally requests to delete a whole support request will be denied for this reason. If there is specific information in the support request that you consider private let us know, and those portions can be redacted.

== Username Deletion ==

When you signup for an account with HelioHost it is clearly stated during the signup process not to pick a username that contains anything that you consider private information.

{{Info|If you need support, you will be asked to provide this username to identify your account where it will be visible to other users, so don't use anything in your username that you consider private information.}}

Unfortunately, not everyone reads things so occasionally someone makes the mistake of creating a username that contains private information. We can help you fix the issue by following these steps:
# Make a backup of anything on your account that you don't want to lose and download it to somewhere safe.
# Request an account reset in order to change your username.
# During the reset process choose a different username that doesn't contain private information.
# Restore the backups to your account after the reset.
# Contact support to request that the previous username that contains private information be changed to the new username that doesn't contain private information.

{{Caution|If you think your username is private information and you want it removed from a support request you must first either:
# Change your username
# Delete your account
Requests to remove usernames from support requests who haven't already done of the two options listed above will be denied.}}

== Domain Deletion ==

We don't consider domain names to be private information. On the contrary, most people pay good money to get their domains listed in as many places on the internet as possible, because the more links to their site exist, the higher their website will rank on search engine results. We provide this optimization service of giving your website a boost in search engine results for free to any of our users who has a website hosted with us and a legitimate support request.

Frequently, people who ask to have their domain removed from their support requests do so because they are under the incorrect assumption that their website will be "more secure" or "impossible to find" if it isn't listed on our forum. Security by obscurity never works. Just for fun we have tried creating domains with 50 randomly selected letters and numbers that we never post anywhere publicly, but it doesn't matter because the bots always eventually find it anyways. Sometimes it takes a few weeks, sometimes it takes a few months, but eventually the 404 errors for wp_login.php start showing up. If you want your website to be secure use actual security measures, such as SSL which we provide for free, or password protection. Hoping no one finds it is like hoping no one finds your front door key under your floor mat. It's laughably bad security.

After acknowledging that it will not improve the security of your website and also acknowledging that you want your search engine optimization to be worse, if you would still like to have your domain name removed from one of your support requests, we will be happy to help. We generally try to reply to all support requests within 24 hours.

== Suspended Account Deletion ==

Depending on why an account was suspended we may not be able to delete it for you right away. For instance, if the contents of the account need to be held as evidence for law enforcement our policy is to hold the data for at least 60 days. This is our policy because we want to do everything within our power to help stop criminals from committing more crimes.

Since HelioHost is based in the United States we have to comply with United States law. A common misunderstanding is people think that since they live in country X they don't have to follow the laws of the United States. If you use a hosting service that is also located in country X that is true, but if you use HelioHost you have to follow the laws of the country HelioHost is located in, which is the United States. We understand that not everyone is familiar with what is and what is not legal in the United States so we encourage you to read our Terms of Service first, and also talk with us prior to uploading your website to make sure it will be ok.

Deletion Policy

2026-04-11T01:40:06Z

Krydos: Ranted for a bit about people requesting stuff to be deleted.

== Deletion Policy ==

This Deletion Policy describes our policies and procedures on the deletion and removal of your information and data when you use our hosting service or contact support.

== Community Support ==

HelioHost is a non-profit run by volunteers who receive no pay for helping you with your hosting issues or maintaining the servers. We volunteer for this organization because we enjoy it, and believe in the mission of providing free hosting to people who can't afford paid hosting. We aren't owned by a for-profit company, we don't have a full time staff of paid employees, and don't have a quota of how many people we need to force to upgrade each month. If we aren't having fun volunteering, or if you are rude to us, we will go do something more enjoyable for us. We aren't required to volunteer a certain number of hours each week, and we may come and go as we please.

In order to reduce the work required by our volunteers, and in order to recruit new volunteers, all of our support is community based and public. This means if someone else has had the same issue as you, we encourage you to search our forum and our wiki to find the solution that worked for other previous users. This also means that regular users can help each other out if they know the answer to someone else's question. All of our volunteers started out as regular users who decided to be helpful and answer other users questions. When we see someone being helpful in the community we sometimes offer them a promotion to give them more tools and more access to be even more helpful.

== Privacy Policy ==

Our Privacy Policy can be read at https://heliohost.org/privacy/ If you have concerns about your privacy, please contact us, and let us know how we can help. We will do everything we can to keep your private data private.

== Private Support ==

We do not currently offer private support, but enough people have expressed interest in private support that we do plan on implementing it in some form in the future. Since private support increases the workload on our volunteers and reduces the helpfulness of our user searchable resources, it will not be free. Therefore, only donors will be allowed to use private support. The exact details of the private support and donation level required to access private support will be announced on our news section when it becomes available. There is currently no ETA on when this will be released.

== Username Deletion ==

When you signup for an account with HelioHost it is clearly stated during the signup process not to pick a username that contains anything that you consider private information.

{{Info|If you need support, you will be asked to provide this username to identify your account where it will be visible to other users, so don't use anything in your username that you consider private information.}}

Unfortunately, not everyone reads things so occasionally someone makes the mistake of creating a username that contains private information. We can help you fix the issue by following these steps:
# Make a backup of anything on your account that you don't want to lose and download it to somewhere safe.
# Request an account reset in order to change your username.
# During the reset process choose a different username that doesn't contain private information.
# Restore the backups to your account after the reset.
# Contact support to request that the previous username that contains private information be changed to the new username that doesn't contain private information.

{{Caution|If you think your username is private information and you want it removed from a support request you must first either:
# Change your username
# Delete your account
Requests to remove usernames from support requests who haven't already done of the two options listed above will be denied.}}

== Domain Deletion ==

We don't consider domain names to be private information. On the contrary, most people pay good money to get their domains listed in as many places on the internet as possible, because the more links to their site exist, the higher their website will rank on search engine results. We provide this optimization service of giving your website a boost in search engine results for free to any of our users who has a website hosted with us and a legitimate support request.

Frequently, people who ask to have their domain removed from their support requests do so because they are under the incorrect assumption that their website will be "more secure" or "impossible to find" if it isn't listed on our forum. Security by obscurity never works. Just for fun we have tried creating domains with 50 randomly selected letters and numbers that we never post anywhere publicly, but it doesn't matter because the bots always eventually find it anyways. Sometimes it takes a few weeks, sometimes it takes a few months, but eventually the 404 errors for wp_login.php start showing up. If you want your website to be secure use actual security measures, such as SSL which we provide for free, or password protection. Hoping no one finds it is like hoping no one finds your front door key under your floor mat. It's laughably bad security.

After acknowledging that it will not improve the security of your website and also acknowledging that you want your search engine optimization to be worse, if you would still like to have your domain name removed from one of your support requests, we will be happy to help. We generally try to reply to all support requests within 24 hours.

== Suspended Account Deletion ==

Depending on why an account was suspended we may not be able to delete it for you right away. For instance, if the contents of the account need to be held as evidence for law enforcement our policy is to hold the data for at least 60 days. This is our policy because we want to do everything within our power to help stop criminals from committing more crimes.

Since HelioHost is based in the United States we have to comply with United States law. A common misunderstanding is people think that since they live in country X they don't have to follow the laws of the United States. If you use a hosting service that is also located in country X that is true, but if you use HelioHost you have to follow the laws of the country HelioHost is located in, which is the United States. We understand that not everyone is familiar with what is and what is not legal in the United States so we encourage you to read our Terms of Service first, and also talk with us prior to uploading your website to make sure it will be ok.

Stevie

2026-03-23T19:55:25Z

Krydos: /* Stevie */ Recycled.

== Stevie ==

Stevie is the first physical server that HelioHost purchased in July 2008. He ran CentOS 5 for eight years until November 2016 when he suffered a hard drive failure. After replacing the hard drive [https://en.wikipedia.org/wiki/VMware_ESXi VMware ESXi] was installed, and the virtual machine [[:Ricky|Ricky]] was created. Stevie has been empty since July 2023 when Ricky was powered off. Stevie was officially retired in August 2024 when he was powered off forever. Stevie's physical remains were recycled in March 2026, but his spirit lives on in Stevie 2.0. RIP Stevie.

Stevie 2.0 was purchased in February 2025 after a [https://donorbox.org/rebirth-of-stevie successful fundraiser]. He is now equipped with Dual Xeon Gold 6138 CPUs, 192 GB of memory, and runs [https://en.wikipedia.org/wiki/VMware_ESXi VMware ESXi].

Terms

2026-03-15T01:04:31Z

Krydos: /* Terms of Service */ Changed order

== Terms of Service ==

By signing up with HelioHost for any service, you agree to the following Terms of Service as well as the [[:#DISCLAIMER|DISCLAIMER]] presented below. If you do not agree to these Terms, you may not use HelioHost. Users who already have an account must [https://heliohost.org/dashboard/delete/ delete their account] if they no longer agree to the Terms.

By signing up with HelioHost for any service, you agree to the following:

* <strong style="color: #ff4d4d; font-size: 120%;">Each person is allowed to have a maximum of one account between Tommy and Johnny. You may not maintain someone else's account on their behalf. </strong><span style="font-size: 120%;">Exceptions to this policy can be requested by contacting support. Approval of such requests is not guaranteed. This policy does not apply to [https://heliohost.org/morty/ Morty] or [https://heliohost.org/vps/ VPS accounts].</span>
* You must be at least 13 years old to use HelioHost.
* You will not register or maintain an account using a disposable email address.
* Your site will contain no content illegal under US law.
* No phishing. Your site will not collect or attempt to collect personal information by deception.
* Your website will not offer banking, investment, credit/loans, or similar financial services, as our data center does not meet PCI DSS compliance or ISO/IEC 27001 certification.
* You will not host any form of online gambling or betting website that accepts wagers or pays prizes in real money, cryptocurrency, or credits that are redeemable for real money or cryptocurrency.
* No cryptocurrency mining.
* Proxies are not permitted on Plesk plans. Users wishing to host a proxy are encouraged to [https://heliohost.org/vps/ purchase a VPS].
* Johnny and Tommy plans are intended for non-commercial uses, such as hobbyists, development environments, registered nonprofits, and personal websites. Microbusinesses that just launched are acceptable but are subject to review. HelioHost reserves the right to require users switch to Morty or a VPS if it is determined that your website belongs to a commercial business. This is a requirement of Plesk's nonprofit licensing.
* You may not infringe on any copyrights through your site. You may be asked for proof of purchase or license if copyrighted content or commercial software is used on your account.
* No IPTV websites. You will not host a streaming video website that offers access to television or movie streams, regardless of the content on offer.
* Your site will not be of a pornographic nature and will refrain from providing pictures and/or photographs of nude men and women.
* Your site will not email, personal message, instant message, or communicate any kind of "spam," or unsolicited bulk advertising of any kind.
* Your site will not offer any form of social media "marketing" service, including but not limited to services that provide "Facebook Likes", "Instagram Followers", or "X Followers". Your account will not store or operate scripts required to provide such services (e.g. "like bots", "follower bots", "smm panels", "sosmed panels").
* Your site will not offer any service that purports to modify or add game content or credits to third-party online game accounts, or that is designed to interrupt, disable, cause a ban from, or otherwise prevent the normal operation of, a third party online game service or account.
* Everything displayed on your site will be your property. HelioHost assumes no responsibility for any content displayed by customers of our services.
* HelioHost is based in the USA. Federal Regulations prohibit us from accepting donations, providing free services, or providing paid services to anyone in Iran, Cuba, or North Korea.
* You will not intentionally send large volumes of traffic to your website or intentionally cause high server load for the purposes of testing performance, resource limits, or capabilities. Users who engage in such conduct may be subject to a permanent ban without warning or refund.
* VPS customers only: Your VPS must respond to ICMP pings. This is required by our ISP.
* Refunds are provided pursuant to our [https://heliohost.org/refunds Refund Policy].
* You agree to not hold HelioHost liable for any loss of data, content, revenues, relationships, or traffic that occurs as a result of a systems failure or outage. You understand that HelioHost services are provided '''AS-IS and that HelioHost does not guarantee service availability'''. Services are provided in accordance with our [[#Disclaimer|Service Disclaimer]].
* We reserve the right to change the Terms of Service at any time. An announcement will be made to you via email and our normal [https://helionet.org/index/forum/1-news/ News channels] when we make such changes. If you disagree with the changes, you can decline them by [https://heliohost.org/dashboard/delete/ deleting your account].
* We reserve the right to delete, change, or edit your account or your content with or without prior notification, including, but not limited to cases arising from abuse of these Terms.

== DISCLAIMER ==

HelioHost hosting service is provided 'AS-IS' with NO WARRANTY of any kind, neither express nor implied, not even the implied warranties of merchantability, non-infringement, and fitness for a particular purpose. Furthermore, HelioHost makes no guarantees as to the proper operation of the service, availability of the service, or the safety or security of the service.

HelioHost is NOT LIABLE FOR DATA LOSS, equipment malfunction or failure, or other damages (physical, digital, monetary, or otherwise) caused by the use of this service, the improper operation of the service due to abuse, misuse, or malfunction of any kind, or the quality of the service's performance (or its failure to perform). Use the service at your own risk.

== HelioNet Terms ==

Users on [[:HelioNet|HelioNet]] must abide by the following rules:

* [https://www.helionet.org/index/topic/4-the-official-rules-guide/ Official Rules Guide]
* [https://www.helionet.org/index/topic/2-the-official-spam-guide/ Official Spam Guide]
* [https://www.helionet.org/index/topic/3-the-official-enforcement-guide/ Official Enforcement Guide]
* [https://www.helionet.org/index/topic/1544-the-official-etiquette-guide/ Official Etiquette Guide]

Failure to abide by these terms may result in suspension of ALL HelioNet affiliated accounts, including accounts related to HelioHost, to be determined at HelioNet's sole discretion.

Terms

2026-03-15T00:57:47Z

Krydos: /* Terms of Service */ 2026-03-14 Terms of Service update adds 1. no commercial websites on non-profit licenses, 2. proof of purchase or license may be required, 3. no casino or gambling websites, 4. no ddosing yourself

== Terms of Service ==

By signing up with HelioHost for any service, you agree to the following Terms of Service as well as the [[:#DISCLAIMER|DISCLAIMER]] presented below. If you do not agree to these Terms, you may not use HelioHost. Users who already have an account must [https://heliohost.org/dashboard/delete/ delete their account] if they no longer agree to the Terms.

By signing up with HelioHost for any service, you agree to the following:

* <strong style="color: #ff4d4d; font-size: 120%;">Each person is allowed to have a maximum of one account between Tommy and Johnny. You may not maintain someone else's account on their behalf. </strong><span style="font-size: 120%;">Exceptions to this policy can be requested by contacting support. Approval of such requests is not guaranteed. This policy does not apply to [https://heliohost.org/morty/ Morty] or [https://heliohost.org/vps/ VPS accounts].</span>
* You must be at least 13 years old to use HelioHost.
* You will not register or maintain an account using a disposable email address.
* Your site will contain no content illegal under US law.
* No phishing. Your site will not collect or attempt to collect personal information by deception.
* Your website will not offer banking, investment, credit/loans, or similar financial services, as our data center does not meet PCI DSS compliance or ISO/IEC 27001 certification.
* You will not host any form of online gambling or betting website that accepts wagers or pays prizes in real money, cryptocurrency, or credits that are redeemable for real money or cryptocurrency.
* No cryptocurrency mining.
* Proxies are not permitted on Plesk plans. Users wishing to host a proxy are encouraged to [https://heliohost.org/vps/ purchase a VPS].
* You may not infringe on any copyrights through your site. You may be asked for proof of purchase or license if copyrighted content or commercial software is used on your account.
* No IPTV websites. You will not host a streaming video website that offers access to television or movie streams, regardless of the content on offer.
* Your site will not be of a pornographic nature and will refrain from providing pictures and/or photographs of nude men and women.
* Your site will not email, personal message, instant message, or communicate any kind of "spam," or unsolicited bulk advertising of any kind.
* Your site will not offer any form of social media "marketing" service, including but not limited to services that provide "Facebook Likes", "Instagram Followers", or "X Followers". Your account will not store or operate scripts required to provide such services (e.g. "like bots", "follower bots", "smm panels", "sosmed panels").
* Your site will not offer any service that purports to modify or add game content or credits to third-party online game accounts, or that is designed to interrupt, disable, cause a ban from, or otherwise prevent the normal operation of, a third party online game service or account.
* Everything displayed on your site will be your property. HelioHost assumes no responsibility for any content displayed by customers of our services.
* HelioHost is based in the USA. Federal Regulations prohibit us from accepting donations, providing free services, or providing paid services to anyone in Iran, Cuba, or North Korea.
* Johnny and Tommy plans are intended for non-commercial uses, such as hobbyists, development environments, registered nonprofits, and personal websites. Microbusinesses that just launched are acceptable but are subject to review. HelioHost reserves the right to require users switch to Morty or a VPS if it is determined that your website belongs to a commercial business. This is a requirement of Plesk's nonprofit licensing.
* You will not intentionally send large volumes of traffic to your website or intentionally cause high server load for the purposes of testing performance, resource limits, or capabilities. Users who engage in such conduct may be subject to a permanent ban without warning or refund.
* VPS customers only: Your VPS must respond to ICMP pings. This is required by our ISP.
* Refunds are provided pursuant to our [https://heliohost.org/refunds Refund Policy].
* You agree to not hold HelioHost liable for any loss of data, content, revenues, relationships, or traffic that occurs as a result of a systems failure or outage. You understand that HelioHost services are provided '''AS-IS and that HelioHost does not guarantee service availability'''. Services are provided in accordance with our [[#Disclaimer|Service Disclaimer]].
* We reserve the right to change the Terms of Service at any time. An announcement will be made to you via email and our normal [https://helionet.org/index/forum/1-news/ News channels] when we make such changes. If you disagree with the changes, you can decline them by [https://heliohost.org/dashboard/delete/ deleting your account].
* We reserve the right to delete, change, or edit your account or your content with or without prior notification, including, but not limited to cases arising from abuse of these Terms.

== DISCLAIMER ==

HelioHost hosting service is provided 'AS-IS' with NO WARRANTY of any kind, neither express nor implied, not even the implied warranties of merchantability, non-infringement, and fitness for a particular purpose. Furthermore, HelioHost makes no guarantees as to the proper operation of the service, availability of the service, or the safety or security of the service.

HelioHost is NOT LIABLE FOR DATA LOSS, equipment malfunction or failure, or other damages (physical, digital, monetary, or otherwise) caused by the use of this service, the improper operation of the service due to abuse, misuse, or malfunction of any kind, or the quality of the service's performance (or its failure to perform). Use the service at your own risk.

== HelioNet Terms ==

Users on [[:HelioNet|HelioNet]] must abide by the following rules:

* [https://www.helionet.org/index/topic/4-the-official-rules-guide/ Official Rules Guide]
* [https://www.helionet.org/index/topic/2-the-official-spam-guide/ Official Spam Guide]
* [https://www.helionet.org/index/topic/3-the-official-enforcement-guide/ Official Enforcement Guide]
* [https://www.helionet.org/index/topic/1544-the-official-etiquette-guide/ Official Etiquette Guide]

Failure to abide by these terms may result in suspension of ALL HelioNet affiliated accounts, including accounts related to HelioHost, to be determined at HelioNet's sole discretion.

MariaDB

2026-03-14T17:05:43Z

Krydos: Created new section for example config

== MariaDB ==

HelioHost offers MariaDB which is the fully free, fully open source version of MySQL.

MariaDB is a very handy tool available to webmasters who want to take advantage of dynamic web pages which run on languages such as PHP, as well as software like WordPress that may have been manually installed (not installed using [[:Softaculous|Softaculous]]).

More information about MariaDB can be found at [https://en.wikipedia.org/wiki/MariaDB/ Wikipedia] and [https://mariadb.org/ the official MariaDB website].

== Plesk Procedure ==

The following are a list of steps to follow to create a MariaDB in Plesk.

== Navigating to the 'Databases' Section ==

Before you take advantage of MariaDB, you will need to create a database and a user to work with. To access the 'Databases' section of Plesk, use the button available left hand menu. Depending on your resolution (e.g. mobile devices), there may be a menu icon ( ☰ ) that you have to click to display the menu. You can also access the 'Database' section from the 'Websites & Domains' section.

== Creating the Database ==

In the 'Databases' section of Plesk, there's a button '+ Add Database'. On smaller resolutions, the menu icon will appear. On the resulting page, you will have to fill out a form.

== General Section ==

The first section is general. There are three items in this section.

The first item is the database name, this is prefixed with the format'<Username>_'.

The second item is the server. This will be a dropdown of the available database servers. From this dropdown select 'localhost:3306( default for MariaDB )'.

The third item is a drop down to associate your database with a site. The default is no related sites. From this dropdown you can associate your database with any website you have set up. This is a convenience feature to help associate a database with a website and is not required.

== User Section ==

The next section is 'Users'. In this section there are 5 items as well as two buttons.

The first item is a checkbox to indicate whether or not you want to add a user while creating your database. This is checked by default.

The second item is the username, this will have a prefix of the same format as the database name.

The third item is the password. This item is associated with the two buttons. The 'Generate' button will generate a password for you. The second button will display the password on your screen. Generated passwords are hidden by default unless the show button is pressed. You can also enter any password you require. Once a password is entered a 'Password Strength' meter will appear. There is a help button '(?)' with more details regarding this meter.

The fourth item is a confirm password. This must match the password.

The fifth item is a checkbox to indicate a 'User has access to all databases within the selected subscription'. This means the user can access all databases listed in the main 'Databases' section.

The sixth item is access control. You have three choices. You can allow local only connections. You can allow connections from any IP, or you can submit a list of IPs or FQDNs. This list supports wildcards and examples are provided.

Once these sections are complete, you can click 'OK' to create the database.

== DB User Permissions ==

In order to change user permissions and privileges, you have to navigate to the user. This is done from the 'Databases' section. A list of users will be listed next to your databases. Click on the user you want to modify to proceed to the 'Edit Database User' screen.

== DB User Editing ==

The first section of this screen is identical to the [user section](#plesk-create-step2) while creating the database and will not be covered here.

There are two items available while editing a user that aren't available while creating a database.

You can assign roles: Read & Write, Read Only, Write Only, and Customer. There are also data/structure access which will specify which privileges a DB user has. See the [https://mariadb.com/docs/server/ref/mdb/privileges/ MariaDB privileges documentation] for more details on the individual privileges.

== Accessing the Database ==

Below are some tips to connect to your database either through Plesk via phpmyadmin, locally via code, or remotely through code or other client (e.g. MariaDB's mysql command line or some other utility such as a GUI listed on the [https://mariadb.com/kb/en/graphical-and-enhanced-clients/ MariaDB website]).

== Local connections ==

If you are connecting locally, then your 'HOST' is 'localhost'. Your database name is the name you specified, but prefixed with your Plesk username and then an underscore (e.g. PLESK_USERNAME_DATABASE).

== Managing the database with phpMyAdmin ==

By using the phpMyAdmin button on Plesk's homepage, you can control and manage your databases and issue commands. More information about phpMyAdmin is available at the [https://www.phpmyadmin.net official site].

== Connecting Remotely ==

# Login at https://heliohost.org/login/
# Click continue to Plesk.
# Click databases in the left navigation panel.
# If you haven't already created a database see [https://wiki.helionet.org/MariaDB#Creating_the_Database Creating the Database] above, otherwise click the database you wish to connect to remotely.
# Click the database user near the bottom of the database tile. It will be your main account username followed by an underscore followed by whatever you picked when creating the database.
# Locate the access control section near the bottom of the page.
# By default databases are created with local connections only for increased security. If you want to allow any IP address to connect select the 'Allow remote connections from any host' option. If you want to allow only one or a few IP addresses to connect select the 'Allow remote connections from' option, and enter the IP address(es) into the box that appears.
# Click 'Ok' at the bottom of the page to save the changes.
# The host you use will be determined by which server you're on. Look at the URL of the Plesk page you're on currently, and if it says 'morty.heliohost.org/smb/database/list' that means you'll be using 'morty.heliohost.org' as your host value.
# The remote MariaDB port is 3306 for all of our plans.
# The full remote MariaDB config will look something like this:

== Example Remote MariaDB Values ==

<pre>
host=morty.heliohost.org
port=3306
username=username_user
database=username_db
</pre>
{{Caution|Make sure you update the above host based on which server you're actually on, make sure you update the username to match the actual username you created, and make sure you update the database name to match the actual database you created. This is just an example, and if you copy/paste it exactly as displayed without updating it to real values it won't work.}}

== Example Code Links ==

Official MariaDB docs:

[https://mariadb.com/developers/resources/language/php/ PHP Example]

[https://mariadb.com/resources/blog/how-to-connect-python-programs-to-mariadb/ Python MariaDB module example]

[https://mariadb.com/resources/blog/using-sqlalchemy-with-mariadb-connector-python-part-1/ Python SQLAlchemy module example]

Offical PHP and Python module docs:

[https://www.php.net/manual/en/book.mysqli.php PHP MySQLi Docs]

[https://mariadb-corporation.github.io/mariadb-connector-python/ Python MariaDB module docs]

[https://docs.sqlalchemy.org/en/20/ Python SQLAlchemy module docs]

You can find other language examples using your favorite search engine.

MariaDB

2026-03-14T17:04:17Z

Krydos: Removed hosts section, since it's covered in the Connecting Remotely section

== MariaDB ==

HelioHost offers MariaDB which is the fully free, fully open source version of MySQL.

MariaDB is a very handy tool available to webmasters who want to take advantage of dynamic web pages which run on languages such as PHP, as well as software like WordPress that may have been manually installed (not installed using [[:Softaculous|Softaculous]]).

More information about MariaDB can be found at [https://en.wikipedia.org/wiki/MariaDB/ Wikipedia] and [https://mariadb.org/ the official MariaDB website].

== Plesk Procedure ==

The following are a list of steps to follow to create a MariaDB in Plesk.

== Navigating to the 'Databases' Section ==

Before you take advantage of MariaDB, you will need to create a database and a user to work with. To access the 'Databases' section of Plesk, use the button available left hand menu. Depending on your resolution (e.g. mobile devices), there may be a menu icon ( ☰ ) that you have to click to display the menu. You can also access the 'Database' section from the 'Websites & Domains' section.

== Creating the Database ==

In the 'Databases' section of Plesk, there's a button '+ Add Database'. On smaller resolutions, the menu icon will appear. On the resulting page, you will have to fill out a form.

== General Section ==

The first section is general. There are three items in this section.

The first item is the database name, this is prefixed with the format'<Username>_'.

The second item is the server. This will be a dropdown of the available database servers. From this dropdown select 'localhost:3306( default for MariaDB )'.

The third item is a drop down to associate your database with a site. The default is no related sites. From this dropdown you can associate your database with any website you have set up. This is a convenience feature to help associate a database with a website and is not required.

== User Section ==

The next section is 'Users'. In this section there are 5 items as well as two buttons.

The first item is a checkbox to indicate whether or not you want to add a user while creating your database. This is checked by default.

The second item is the username, this will have a prefix of the same format as the database name.

The third item is the password. This item is associated with the two buttons. The 'Generate' button will generate a password for you. The second button will display the password on your screen. Generated passwords are hidden by default unless the show button is pressed. You can also enter any password you require. Once a password is entered a 'Password Strength' meter will appear. There is a help button '(?)' with more details regarding this meter.

The fourth item is a confirm password. This must match the password.

The fifth item is a checkbox to indicate a 'User has access to all databases within the selected subscription'. This means the user can access all databases listed in the main 'Databases' section.

The sixth item is access control. You have three choices. You can allow local only connections. You can allow connections from any IP, or you can submit a list of IPs or FQDNs. This list supports wildcards and examples are provided.

Once these sections are complete, you can click 'OK' to create the database.

== DB User Permissions ==

In order to change user permissions and privileges, you have to navigate to the user. This is done from the 'Databases' section. A list of users will be listed next to your databases. Click on the user you want to modify to proceed to the 'Edit Database User' screen.

== DB User Editing ==

The first section of this screen is identical to the [user section](#plesk-create-step2) while creating the database and will not be covered here.

There are two items available while editing a user that aren't available while creating a database.

You can assign roles: Read & Write, Read Only, Write Only, and Customer. There are also data/structure access which will specify which privileges a DB user has. See the [https://mariadb.com/docs/server/ref/mdb/privileges/ MariaDB privileges documentation] for more details on the individual privileges.

== Accessing the Database ==

Below are some tips to connect to your database either through Plesk via phpmyadmin, locally via code, or remotely through code or other client (e.g. MariaDB's mysql command line or some other utility such as a GUI listed on the [https://mariadb.com/kb/en/graphical-and-enhanced-clients/ MariaDB website]).

== Local connections ==

If you are connecting locally, then your 'HOST' is 'localhost'. Your database name is the name you specified, but prefixed with your Plesk username and then an underscore (e.g. PLESK_USERNAME_DATABASE).

== Managing the database with phpMyAdmin ==

By using the phpMyAdmin button on Plesk's homepage, you can control and manage your databases and issue commands. More information about phpMyAdmin is available at the [https://www.phpmyadmin.net official site].

== Connecting Remotely ==

# Login at https://heliohost.org/login/
# Click continue to Plesk.
# Click databases in the left navigation panel.
# If you haven't already created a database see [https://wiki.helionet.org/MariaDB#Creating_the_Database Creating the Database] above, otherwise click the database you wish to connect to remotely.
# Click the database user near the bottom of the database tile. It will be your main account username followed by an underscore followed by whatever you picked when creating the database.
# Locate the access control section near the bottom of the page.
# By default databases are created with local connections only for increased security. If you want to allow any IP address to connect select the 'Allow remote connections from any host' option. If you want to allow only one or a few IP addresses to connect select the 'Allow remote connections from' option, and enter the IP address(es) into the box that appears.
# Click 'Ok' at the bottom of the page to save the changes.
# The host you use will be determined by which server you're on. Look at the URL of the Plesk page you're on currently, and if it says 'morty.heliohost.org/smb/database/list' that means you'll be using 'morty.heliohost.org' as your host value.
# The remote MariaDB port is 3306 for all of our plans.
# The full remote MariaDB config will look something like this:

<pre>
host=morty.heliohost.org
port=3306
username=username_user
database=username_db
</pre>
{{Caution|Make sure you update the above host based on which server you're actually on, make sure you update the username to match the actual username you created, and make sure you update the database name to match the actual database you created. This is just an example, and if you copy/paste it exactly as displayed without updating it to real values it won't work.}}

== Example Code Links ==

Official MariaDB docs:

[https://mariadb.com/developers/resources/language/php/ PHP Example]

[https://mariadb.com/resources/blog/how-to-connect-python-programs-to-mariadb/ Python MariaDB module example]

[https://mariadb.com/resources/blog/using-sqlalchemy-with-mariadb-connector-python-part-1/ Python SQLAlchemy module example]

Offical PHP and Python module docs:

[https://www.php.net/manual/en/book.mysqli.php PHP MySQLi Docs]

[https://mariadb-corporation.github.io/mariadb-connector-python/ Python MariaDB module docs]

[https://docs.sqlalchemy.org/en/20/ Python SQLAlchemy module docs]

You can find other language examples using your favorite search engine.

MariaDB

2026-03-14T17:03:25Z

Krydos: /* Connecting Remotely */ A few more details about how to enable remote connections.

== MariaDB ==

HelioHost offers MariaDB which is the fully free, fully open source version of MySQL.

MariaDB is a very handy tool available to webmasters who want to take advantage of dynamic web pages which run on languages such as PHP, as well as software like WordPress that may have been manually installed (not installed using [[:Softaculous|Softaculous]]).

More information about MariaDB can be found at [https://en.wikipedia.org/wiki/MariaDB/ Wikipedia] and [https://mariadb.org/ the official MariaDB website].

== Plesk Procedure ==

The following are a list of steps to follow to create a MariaDB in Plesk.

== Navigating to the 'Databases' Section ==

Before you take advantage of MariaDB, you will need to create a database and a user to work with. To access the 'Databases' section of Plesk, use the button available left hand menu. Depending on your resolution (e.g. mobile devices), there may be a menu icon ( ☰ ) that you have to click to display the menu. You can also access the 'Database' section from the 'Websites & Domains' section.

== Creating the Database ==

In the 'Databases' section of Plesk, there's a button '+ Add Database'. On smaller resolutions, the menu icon will appear. On the resulting page, you will have to fill out a form.

== General Section ==

The first section is general. There are three items in this section.

The first item is the database name, this is prefixed with the format'<Username>_'.

The second item is the server. This will be a dropdown of the available database servers. From this dropdown select 'localhost:3306( default for MariaDB )'.

The third item is a drop down to associate your database with a site. The default is no related sites. From this dropdown you can associate your database with any website you have set up. This is a convenience feature to help associate a database with a website and is not required.

== User Section ==

The next section is 'Users'. In this section there are 5 items as well as two buttons.

The first item is a checkbox to indicate whether or not you want to add a user while creating your database. This is checked by default.

The second item is the username, this will have a prefix of the same format as the database name.

The third item is the password. This item is associated with the two buttons. The 'Generate' button will generate a password for you. The second button will display the password on your screen. Generated passwords are hidden by default unless the show button is pressed. You can also enter any password you require. Once a password is entered a 'Password Strength' meter will appear. There is a help button '(?)' with more details regarding this meter.

The fourth item is a confirm password. This must match the password.

The fifth item is a checkbox to indicate a 'User has access to all databases within the selected subscription'. This means the user can access all databases listed in the main 'Databases' section.

The sixth item is access control. You have three choices. You can allow local only connections. You can allow connections from any IP, or you can submit a list of IPs or FQDNs. This list supports wildcards and examples are provided.

Once these sections are complete, you can click 'OK' to create the database.

== DB User Permissions ==

In order to change user permissions and privileges, you have to navigate to the user. This is done from the 'Databases' section. A list of users will be listed next to your databases. Click on the user you want to modify to proceed to the 'Edit Database User' screen.

== DB User Editing ==

The first section of this screen is identical to the [user section](#plesk-create-step2) while creating the database and will not be covered here.

There are two items available while editing a user that aren't available while creating a database.

You can assign roles: Read & Write, Read Only, Write Only, and Customer. There are also data/structure access which will specify which privileges a DB user has. See the [https://mariadb.com/docs/server/ref/mdb/privileges/ MariaDB privileges documentation] for more details on the individual privileges.

== Accessing the Database ==

Below are some tips to connect to your database either through Plesk via phpmyadmin, locally via code, or remotely through code or other client (e.g. MariaDB's mysql command line or some other utility such as a GUI listed on the [https://mariadb.com/kb/en/graphical-and-enhanced-clients/ MariaDB website]).

== Local connections ==

If you are connecting locally, then your 'HOST' is 'localhost'. Your database name is the name you specified, but prefixed with your Plesk username and then an underscore (e.g. PLESK_USERNAME_DATABASE).

== Managing the database with phpMyAdmin ==

By using the phpMyAdmin button on Plesk's homepage, you can control and manage your databases and issue commands. More information about phpMyAdmin is available at the [https://www.phpmyadmin.net official site].

== Connecting Remotely ==

# Login at https://heliohost.org/login/
# Click continue to Plesk.
# Click databases in the left navigation panel.
# If you haven't already created a database see [https://wiki.helionet.org/MariaDB#Creating_the_Database Creating the Database] above, otherwise click the database you wish to connect to remotely.
# Click the database user near the bottom of the database tile. It will be your main account username followed by an underscore followed by whatever you picked when creating the database.
# Locate the access control section near the bottom of the page.
# By default databases are created with local connections only for increased security. If you want to allow any IP address to connect select the 'Allow remote connections from any host' option. If you want to allow only one or a few IP addresses to connect select the 'Allow remote connections from' option, and enter the IP address(es) into the box that appears.
# Click 'Ok' at the bottom of the page to save the changes.
# The host you use will be determined by which server you're on. Look at the URL of the Plesk page you're on currently, and if it says 'morty.heliohost.org/smb/database/list' that means you'll be using 'morty.heliohost.org' as your host value.
# The remote MariaDB port is 3306 for all of our plans.
# The full remote MariaDB config will look something like this:

<pre>
host=morty.heliohost.org
port=3306
username=username_user
database=username_db
</pre>
{{Caution|Make sure you update the above host based on which server you're actually on, make sure you update the username to match the actual username you created, and make sure you update the database name to match the actual database you created. This is just an example, and if you copy/paste it exactly as displayed without updating it to real values it won't work.}}

== Server Hosts ==

Use the host for your server:

* Morty: morty.heliohost.org
* Tommy: tommy.heliohost.org
* Johnny: johnny.heliohost.org

== Example Code Links ==

Official MariaDB docs:

[https://mariadb.com/developers/resources/language/php/ PHP Example]

[https://mariadb.com/resources/blog/how-to-connect-python-programs-to-mariadb/ Python MariaDB module example]

[https://mariadb.com/resources/blog/using-sqlalchemy-with-mariadb-connector-python-part-1/ Python SQLAlchemy module example]

Offical PHP and Python module docs:

[https://www.php.net/manual/en/book.mysqli.php PHP MySQLi Docs]

[https://mariadb-corporation.github.io/mariadb-connector-python/ Python MariaDB module docs]

[https://docs.sqlalchemy.org/en/20/ Python SQLAlchemy module docs]

You can find other language examples using your favorite search engine.

Flask

2026-02-08T00:36:38Z

Krydos: /* Request WSGI Control Access */ Flask uses flask.wsgi not dispatch.wsgi

== Flask ==

== About Flask ==

Flask is a Python web framework built with a small core and easy-to-extend philosophy. Read more at [https://www.fullstackpython.com/flask.html Full Stack Python].

== Morty server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a VPS. {{Template:VPSInfo}}}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Morty || 5.0.7 || 3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Tommy server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a VPS. {{Template:VPSInfo}}}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Tommy || 5.0.7 || 3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Johnny server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a VPS. {{Template:VPSInfo}}}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Johnny || 3.0.3 || 3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== How To Setup Flask on Plesk ==

== Create a directory on your main domain called 'flasktest'. ==

If you were transferred from the old cPanel, your main domain will be parked on the 'public_html' directory.

If you created a new account on Plesk, your directory will be 'httpdocs'.

== Create an '.htaccess' file inside the 'flasktest' directory with these contents: ==

<pre>
Options +ExecCGI
RewriteEngine On
RewriteBase /
RewriteRule ^(media/.*)$ - [L]
RewriteRule ^(admin_media/.*)$ - [L]
RewriteRule ^(flask\.wsgi/.*)$ - [L]
RewriteRule ^(.*)$ flasktest/flask.wsgi/$1 [QSA,PT,L]
</pre>

== Create a file named 'flask.wsgi' inside the 'flasktest' directory with these contents: ==

{{Caution|Update the code example, beneath where it says "edit your path below", and type in the path to your actual website address, instead of the placeholder 'domain.helioho.st' part.}}

<pre>
import os, sys

# edit your path below
sys.path.append("/home/domain.helioho.st/httpdocs/flasktest");

sys.path.insert(0, os.path.dirname(__file__))
from myapp import app as application

# set this to something harder to guess
application.secret_key = 'secret'
</pre>

== Create a file named 'myapp.py' inside the 'flasktest' directory with these contents: ==

<pre>
import sys

from flask import Flask, __version__
app = Flask(__name__)
application = app

@app.route("/")
def hello():
return """

Flask is working on HelioHost.<br><br>
<a href="/flasktest/python/version/">Python version</a><br>
<a href="/flasktest/flask/version/">Flask version</a>

"""

@app.route("/python/version/")
def p_version():
return "Python version %s<br><br><a href='/flasktest/'>back</a>" % sys.version

@app.route("/flask/version/")
def f_version():
return "Flask version %s<br><br><a href='/flasktest/'>back</a>" % __version__

if __name__ == "__main__":
app.run()
</pre>

== Make sure your directory structure and files look like this: ==

<pre>
flasktest/
├── flask.wsgi
├── .htaccess
└── myapp.py

0 directories, 3 files
</pre>

== If you did everything right it should look like the below: ==

Screenshot taken from [https://krydos.heliohost.org/flasktest https://krydos.heliohost.org/flasktest/]

[[File:flask_test.png]]

== WSGI Uses Caching ==

{{Caution|
Flask changes can take '''up to 2 hours''' to appear consistently on your site because [[:Flask#WSGI_Uses_Server_Side_Caching|WSGI uses server side caching]].

If you want site changes to take effect immediately, we offer [[#Options_to_Work_Around_Caching|a few options to work around caching]].
}}

== What Caching Does ==

Multiple Apache processes are running on the server, and each time you refresh your site you are randomly assigned to one of these processes. If that particular process has already displayed your site, it shows the cached version of your code; otherwise, it shows the new code changes. This means that during the first 2 hours after a site change, you may intermittently see old or new content, depending on which process you get assigned to. This situation will resolve when Apache is restarted, which happens every 2 hours.

== Options to Work Around Caching ==

== Request WSGI Control Access ==

A new feature currently available only on the [[:Morty]] plan is the ability for users to restart their Flask app themselves. Please note that this feature takes '''at a minimum''' 260 GB memory per day, which will result in a bill of '''$1.91 or more'''.

WSGI Control Access is no longer available on the [[:Tommy]] and [[:Johnny]] servers. Users who need WSGI Control Access can [[:Moving_Your_Account | move their account]] to Morty using our [https://heliohost.org/dashboard/move/ Dashboard page for account moves], or purchase a VPS. {{Template:VPSInfo}} The main advantage of the VPS over Morty is you get root SSH access, which makes Flask development even easier.

To try to keep the cost as low as possible, users on Morty also have the option to request that WSGI Control Access be temporarily enabled it to allow for debugging. Once they have completed troubleshooting, they can request for WSGI Control Access to be disabled.

Once you have created a Flask app that has a 'flask.wsgi' file, create a new post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'flask.wsgi' file.
# Confirmation that you understand that WSGI Control Access uses '''at a minimum''' 260 GB memory per day and your bill will probably be about '''$1.91 or more per month'''.
# The domain name(s) for which you want WSGI Control Access. '''Note:''' If you have 2 Flask apps on 2 different domains, you need to request WSGI Control Access for each domain.

Once you have confirmed your understanding of the charges involved, and been given WSGI Control Access on Morty, you can edit your 'flask.wsgi' to reload your Flask app so new code changes load immediately. The edits to the file can be as simple as adding or removing a space or a blank line. As long as the file's 'last modified date' changes it will discard the cache and reload your Flask app.

Please let us know if you experience unexpected results with this new feature.

== Account Resets Remove WSGI Control Access ==

{{Info|
If you [[:FAQ#How_do_I_reset_my_hosting_account_to_start_fresh|request an account reset]] you will need to re-request WSGI Control Access after the reset has been completed. By default, account resets will disable WSGI Control Access.
}}

== Use Local Development Environment ==

Another option to see code changes reflected immediately is to develop your Django app on your home computer and then host the production copy on the server. This is a useful approach for users on the [[:Tommy]] and [[:Johnny]] servers, where WSGI Control Access is no longer offered.

== VPS ==

You may prefer to upgrade to a VPS, depending on your requirements. {{Template:VPSInfo}} The main advantage of the VPS over Morty is you get root SSH access, which makes Flask development even easier.

== Troubleshooting ==

=== You don't have permission to access /flasktest/flask.wsgi/ on this server ===

If you receive an error of 'You don't have permission to access /flasktest/flask.wsgi/ on this server', you may need to add 'AddHandler cgi-script .py' on a new line in your '.htaccess' file.

=== ImportError: Interpreter change detected - this module can only be loaded into one interpreter per process ===

If you receive an error of 'ImportError: Interpreter change detected - this module can only be loaded into one interpreter per process', this happens because we use WSGI in embedded mode to reduce load on [[:Tommy | Tommy]] and [[:Johnny | Johnny.]]

On [[:Morty | Morty]] you have the option to use WSGI in daemon mode, but it uses 260 GB memory per day so you would get overage charges every day and pay about $1.91 per month.

You can also switch to a VPS to get rid of the error. {{Template:VPSInfo}}

To get rid of the error on Morty, Tommy, or Johnny, you could use Python CGI instead of Flask.

== Running Flask at the Webroot ==

The above example is for Flask in a subdirectory, so users can host different projects in different subdirectories rather than dedicating the whole domain to one Flask app.

If you prefer to run Flask at the webroot instead, this is possible with some slight changes to the '.htaccess', 'flask.wsgi', and 'myapp.py' files.

== References ==

This tutorial is adapted from the [https://helionet.org/index/topic/53856-how-to-use-flask-on-plesk/ How to Use Flask on Plesk] post on the HelioNet forum, answered by Krydos.

== Further Support ==

If this tutorial has not worked for you, please go back and check all of your steps again to make sure you didn't miss anything. If you can't figure out what is wrong, please check your account [[:View_Error_Logs | error logs]], since these will often provide information that can help you resolve the problem. If you're still stuck, please post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''' and any '''error message(s)''' received.

[[Category:Tutorials]]

Flask

2026-02-08T00:36:07Z

Krydos: /* Request WSGI Control Access */ Flask uses flask.wsgi not dispatch.wsgi

== Flask ==

== About Flask ==

Flask is a Python web framework built with a small core and easy-to-extend philosophy. Read more at [https://www.fullstackpython.com/flask.html Full Stack Python].

== Morty server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a VPS. {{Template:VPSInfo}}}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Morty || 5.0.7 || 3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Tommy server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a VPS. {{Template:VPSInfo}}}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Tommy || 5.0.7 || 3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Johnny server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a VPS. {{Template:VPSInfo}}}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Johnny || 3.0.3 || 3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== How To Setup Flask on Plesk ==

== Create a directory on your main domain called 'flasktest'. ==

If you were transferred from the old cPanel, your main domain will be parked on the 'public_html' directory.

If you created a new account on Plesk, your directory will be 'httpdocs'.

== Create an '.htaccess' file inside the 'flasktest' directory with these contents: ==

<pre>
Options +ExecCGI
RewriteEngine On
RewriteBase /
RewriteRule ^(media/.*)$ - [L]
RewriteRule ^(admin_media/.*)$ - [L]
RewriteRule ^(flask\.wsgi/.*)$ - [L]
RewriteRule ^(.*)$ flasktest/flask.wsgi/$1 [QSA,PT,L]
</pre>

== Create a file named 'flask.wsgi' inside the 'flasktest' directory with these contents: ==

{{Caution|Update the code example, beneath where it says "edit your path below", and type in the path to your actual website address, instead of the placeholder 'domain.helioho.st' part.}}

<pre>
import os, sys

# edit your path below
sys.path.append("/home/domain.helioho.st/httpdocs/flasktest");

sys.path.insert(0, os.path.dirname(__file__))
from myapp import app as application

# set this to something harder to guess
application.secret_key = 'secret'
</pre>

== Create a file named 'myapp.py' inside the 'flasktest' directory with these contents: ==

<pre>
import sys

from flask import Flask, __version__
app = Flask(__name__)
application = app

@app.route("/")
def hello():
return """

Flask is working on HelioHost.<br><br>
<a href="/flasktest/python/version/">Python version</a><br>
<a href="/flasktest/flask/version/">Flask version</a>

"""

@app.route("/python/version/")
def p_version():
return "Python version %s<br><br><a href='/flasktest/'>back</a>" % sys.version

@app.route("/flask/version/")
def f_version():
return "Flask version %s<br><br><a href='/flasktest/'>back</a>" % __version__

if __name__ == "__main__":
app.run()
</pre>

== Make sure your directory structure and files look like this: ==

<pre>
flasktest/
├── flask.wsgi
├── .htaccess
└── myapp.py

0 directories, 3 files
</pre>

== If you did everything right it should look like the below: ==

Screenshot taken from [https://krydos.heliohost.org/flasktest https://krydos.heliohost.org/flasktest/]

[[File:flask_test.png]]

== WSGI Uses Caching ==

{{Caution|
Flask changes can take '''up to 2 hours''' to appear consistently on your site because [[:Flask#WSGI_Uses_Server_Side_Caching|WSGI uses server side caching]].

If you want site changes to take effect immediately, we offer [[#Options_to_Work_Around_Caching|a few options to work around caching]].
}}

== What Caching Does ==

Multiple Apache processes are running on the server, and each time you refresh your site you are randomly assigned to one of these processes. If that particular process has already displayed your site, it shows the cached version of your code; otherwise, it shows the new code changes. This means that during the first 2 hours after a site change, you may intermittently see old or new content, depending on which process you get assigned to. This situation will resolve when Apache is restarted, which happens every 2 hours.

== Options to Work Around Caching ==

== Request WSGI Control Access ==

A new feature currently available only on the [[:Morty]] plan is the ability for users to restart their Flask app themselves. Please note that this feature takes '''at a minimum''' 260 GB memory per day, which will result in a bill of '''$1.91 or more'''.

WSGI Control Access is no longer available on the [[:Tommy]] and [[:Johnny]] servers. Users who need WSGI Control Access can [[:Moving_Your_Account | move their account]] to Morty using our [https://heliohost.org/dashboard/move/ Dashboard page for account moves], or purchase a VPS. {{Template:VPSInfo}} The main advantage of the VPS over Morty is you get root SSH access, which makes Flask development even easier.

To try to keep the cost as low as possible, users on Morty also have the option to request that WSGI Control Access be temporarily enabled it to allow for debugging. Once they have completed troubleshooting, they can request for WSGI Control Access to be disabled.

Once you have created a Flask app that has a 'dispatch.wsgi' file, create a new post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'flask.wsgi' file.
# Confirmation that you understand that WSGI Control Access uses '''at a minimum''' 260 GB memory per day and your bill will probably be about '''$1.91 or more per month'''.
# The domain name(s) for which you want WSGI Control Access. '''Note:''' If you have 2 Flask apps on 2 different domains, you need to request WSGI Control Access for each domain.

Once you have confirmed your understanding of the charges involved, and been given WSGI Control Access on Morty, you can edit your 'flask.wsgi' to reload your Flask app so new code changes load immediately. The edits to the file can be as simple as adding or removing a space or a blank line. As long as the file's 'last modified date' changes it will discard the cache and reload your Flask app.

Please let us know if you experience unexpected results with this new feature.

== Account Resets Remove WSGI Control Access ==

{{Info|
If you [[:FAQ#How_do_I_reset_my_hosting_account_to_start_fresh|request an account reset]] you will need to re-request WSGI Control Access after the reset has been completed. By default, account resets will disable WSGI Control Access.
}}

== Use Local Development Environment ==

Another option to see code changes reflected immediately is to develop your Django app on your home computer and then host the production copy on the server. This is a useful approach for users on the [[:Tommy]] and [[:Johnny]] servers, where WSGI Control Access is no longer offered.

== VPS ==

You may prefer to upgrade to a VPS, depending on your requirements. {{Template:VPSInfo}} The main advantage of the VPS over Morty is you get root SSH access, which makes Flask development even easier.

== Troubleshooting ==

=== You don't have permission to access /flasktest/flask.wsgi/ on this server ===

If you receive an error of 'You don't have permission to access /flasktest/flask.wsgi/ on this server', you may need to add 'AddHandler cgi-script .py' on a new line in your '.htaccess' file.

=== ImportError: Interpreter change detected - this module can only be loaded into one interpreter per process ===

If you receive an error of 'ImportError: Interpreter change detected - this module can only be loaded into one interpreter per process', this happens because we use WSGI in embedded mode to reduce load on [[:Tommy | Tommy]] and [[:Johnny | Johnny.]]

On [[:Morty | Morty]] you have the option to use WSGI in daemon mode, but it uses 260 GB memory per day so you would get overage charges every day and pay about $1.91 per month.

You can also switch to a VPS to get rid of the error. {{Template:VPSInfo}}

To get rid of the error on Morty, Tommy, or Johnny, you could use Python CGI instead of Flask.

== Running Flask at the Webroot ==

The above example is for Flask in a subdirectory, so users can host different projects in different subdirectories rather than dedicating the whole domain to one Flask app.

If you prefer to run Flask at the webroot instead, this is possible with some slight changes to the '.htaccess', 'flask.wsgi', and 'myapp.py' files.

== References ==

This tutorial is adapted from the [https://helionet.org/index/topic/53856-how-to-use-flask-on-plesk/ How to Use Flask on Plesk] post on the HelioNet forum, answered by Krydos.

== Further Support ==

If this tutorial has not worked for you, please go back and check all of your steps again to make sure you didn't miss anything. If you can't figure out what is wrong, please check your account [[:View_Error_Logs | error logs]], since these will often provide information that can help you resolve the problem. If you're still stuck, please post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''' and any '''error message(s)''' received.

[[Category:Tutorials]]

Addon Domains

2026-01-29T19:44:59Z

Krydos: /* Addon Domains */ Changed order to standardized best plan > lesser plan > lesser plan. Removed extra ) and extra space.

== Addon Domains ==

HelioHost accounts on the [[:Morty]] plan can have up to 15 domains total, but if you need more than 15 domains, you can create additional Morty accounts. Users on [[:Tommy]] can have up to 10 domains in total, and on [[:Johnny]] you can have up to 5 domains in total. This includes addon domains, [[:Subdomains|subdomains]], and [[:Parked_(Alias)_Domains|aliases (parked domains)]].

Users cannot yet manage domains on their account themselves. We plan to add this feature in the future, but [[:ETA|there is no ETA for when it may be implemented]].

In the meantime, HelioHost staff will be happy to help you manage your addon domains.

== What is an Addon Domain? ==

An addon domain is a domain which reflects the contents of a folder in your Plesk File Manager.

== How can I create an Addon Domain? ==

To create an addon domain, submit a request in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum] and provide the following information:
# Your hosting account '''username'''
# 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.)

== Where are the Addon Domain Files? ==

Addon domains don't use an httpdocs folder. Instead, each addon domain gets its own folder in your home directory with the same name as the addon domain. For example, if your addon domain is 'addondomain.helioho.st', visitors will see whatever files you upload to that folder.

[[File:addon_domain_files_folder.png]]

== Custom Addon Domains ==

== Nameservers ==

You will need to point your custom domain to the following nameservers:

* ns1.heliohost.org
* ns2.heliohost.org

== DNS Records ==

If you prefer to add A records (IPv4) or AAAA records (IPv6) to your custom domain registrar's dashboard instead of nameservers, look up the IP addresses for your server by using the steps below:

'''Login > Plesk > Websites & Domains > [domain name] > and check at the bottom of the page.'''

== What do I do now? ==

{{Info|Whether you are using one of HelioHost's domains or a custom domain, you will need to wait '''up to 2 hours''' for your addon domain to become fully active. If after an entire 2 hours, you still see a message saying 'HelioHost Account Queued', please [[:Clear_Your_Cache|clear your web browser cache]].}}

== Checking Custom Domain DNS ==

Full DNS propagation can take up to 24 - 48 hours globally in some cases. To check that your DNS is properly configured, go to [https://dnschecker.org/ dnschecker.org]. Select the type of record you want to check (NS record, A record, or AAAA record), and type in your custom domain.

== How can I delete an Addon Domain? ==

{{Danger|Deleting your addon domain will delete all the files associated with it, so we strongly recommend you [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|create an account backup]] before requesting to delete an addon domain.

As mentioned in our [[:Terms|Terms of Service]], it is not HelioHost's responsibility to keep backups of your data.}}

To request deletion of an addon domain, create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum] and provide the following information:
# Your hosting account '''username'''
# The '''addon domain''' you want deleted

Charlie

2025-12-30T05:52:23Z

Krydos: /* Charlie */ Update

== Charlie ==

Charlie is a physical server that was purchased in December 2010 and originally hosted [[:Cody|Cody]] and [[:Johnny|Johnny]]. In 2016 when [[:Eddie|Eddie]] was purchased [[:Cody|Cody]] was moved to [[:Eddie|Eddie]] so [[:Johnny|Johnny]] could have all of the resources of Charlie to himself. When [[:Sparkie|Sparkie]] was purchased in 2019 [[:Johnny|Johnny]] was moved off of Charlie as well. He is equipped with a Core 2 Quad Q9550 CPU, 8 GB of memory, and runs [https://en.wikipedia.org/wiki/VMware_ESXi VMware ESXi]. Charlie as been empty since December 2025, and is next in line to be retired.

WordPress

2025-12-11T01:35:38Z

Krydos: /* Abusive IPs */ Added another Digital Ocean range

== WordPress ==

WordPress is a popular content management system (CMS) that allows users to easily create and manage websites.

{{Caution|WordPress is known to require a lot of server resources, as it's not very well optimized. Also, the more pages or plugins a WordPress site has, the bigger the site load will be.

Exceeding the account load limits will cause your user account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Accounts on our [[:Morty|Morty]] server will not be suspended but will be charged for account load overages.

If you use WordPress, we recommend you [https://heliohost.org/dashboard/load/ monitor your site load here].

If at any point you become concerned about your account server usage load getting you suspended, you can add "deny from all" to the bottom of your '.htaccess' file to take the site offline. Once that's been done, the site should stop generating load practically instantly.}}

== But my WordPress Site is Brand New / Has No Plugins / Gets Hardly Any Visitor Traffic ==

WordPress causes 0 load with 0 traffic, but sites built with WordPress are prime targets for bot attacks. When bots discover your site URL address, they will keep trying to hack in, which causes load on the server resources.

Even if your WordPress install is brand new, with no plugins, and your site gets few visitors, there is still a risk of bots spamming your site. This could cause your account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Accounts on our [[:Morty|Morty]] server will not be suspended but will be charged for account load overages

Additionally, a lot of free themes and plugins can be backdoors for hackers, and installing them comes with risks. Once bots access your site, they will 'phone home' which then enables hackers to change your site files, set up phishing sites, send spam from your account, etc.

== How Much Server Load Could It Cause? ==

WordPress was one of the apps we load tested, with the benchmark testing results posted on our [[:Common_Software_Load|Common Software Load]] page.

Here are [https://helionet.org/index/topic/57357-solved-disconnect-addon-domain/?do=findComment&comment=252857 some comparison calculations] about how much demand on the server WordPress can cause.

== How Can I Keep My Server Load Low? ==

Our first recommendation is to switch to anything other than WordPress.

=== WordPress Alternatives ===
* Some of our users have switched from WordPress to '''Joomla''' and liked it.
* '''Drupal''' performed well in our recent benchmark load tests.
* Another popular alternative is '''Gatsby'''. You can check out a guide on migrating your site [https://www.gatsbyjs.com/blog/2019-03-21-migrating-from-wordpress-to-gatsby/ here] or follow our quick [[:Gatsby|Gatsby tutorial]] to set up a basic site from scratch.
* For static blog generators, '''Publii''' may be an option for you. Please note that as it's local, you will need to upload every time you post. It's not for Android or iOS, and it cannot be synced unless you use a cloud syncing service for the local files. You can check out a guide on how to import data from your WordPress site into Publii [https://getpublii.com/docs/import-wordpress-into-static-html-site.html here].
* '''Jekyll''' is a popular static site generator.
* '''Hugo''' is one of the most popular open-source static site generators.
* '''Grav''' is an open-source flat-file CMS (Content Management System).
* '''Eleventy''' (11ty) offers a simple 'zero-config' option to quickly get a site built. Since it runs on Node, which consumes a lot of memory, we recommend running the build process locally, and then deploying the static pages to your hosting account.
* '''Astro''' is a modern, fast, and flexible web framework. Our [[:Astro|Astro tutorial]] guides you through building and deploying a site with a dedicated blog section.

=== How To Reduce WordPress Server Load ===

If moving away from WordPress is not an option for you, here are other things to try:
* Update everything to the latest version.
* Disable uptime monitors.
* Disable logins.
* Disable unneeded plugins and themes.
* Use caching plugins to reduce the load (users have mentioned that '''WP Fastest Cache''' plugin can be useful).
* Use Cloudflare caching.
* Use Cloudflare and the '''Super Page Cache for Cloudflare''' WordPress plugin to [https://helionet.org/index/topic/57606-handling-cpu-load-spikes-or-high-load-using-cloudflare/ mitigate load spikes or other high load issues].
** If Super Page Cache for Cloudflare tells you to disable the options "Smart static files processing" and "Serve static files directly by Nginx" on the "Apache & Nginx Settings" page of your Plesk panel, you can change these settings yourself by navigating to: '''Login > Plesk > Websites & Domains > [domain] > Hosting & DNS > Apache & Nginx > Uncheck the 'smart static files processing box' and make sure the 'Serve static files directly by Nginx' box is also unchecked.'''
* Actively monitor your access logs and look for IPs with an unreasonably high number of hits/page views.
** Block any suspicious / abusive IPs by adding <code>Deny from x.x.x.x</code> to your '.htaccess' file, or block them with Cloudflare if you have a custom domain.
** To check site stats, navigate to: '''Plesk > Statistics > Web Statistics > your domain > [View].'''
* Convert to a static site.
** Users have mentioned '''WP2Static''' as being a useful plugin that converts WordPress sites to static sites.
** Explore [https://jamstack.org/generators/ this list of Open Source static site generators] to find alternatives.
* Upgrade to a VPS. {{Template:VPSInfo}}
** You can ask us to install Hestia, a free and popular control panel, on your [https://heliohost.org/vps/ VPS] for you. Hestia includes a one-click WordPress installation feature. Preview the setup steps in our [[:VPS_WordPress | Installing WordPress on a VPS running Hestia Control Panel tutorial]].

== Abusive IPs ==

HelioHost needed to block the below IP addresses and IP Ranges since some of our WordPress users were under attack from bots coming from these sources. If you use WordPress, we strongly recommend that you add the below to your own .htaccess file to proactively protect your site from IPs known to be abusive.

<pre>
# added by HelioHost - hacking attempt
Deny from 165.22.48.216
Deny from 52.169.95.1
Deny from 52.164.121.3
# these ranges are bots running at Digital Ocean who seems to have an abuse hosting problem
Deny from 68.183.176.0/20
Deny from 104.248.0.0/16
Deny from 104.131.0.0/16
Deny from 104.236.0.0/16
Deny from 165.232.0.0/16
Deny from 107.170.0.0/16
Deny from 128.199.0.0/16
Deny from 134.122.0.0/16
Deny from 134.199.128.0/17
Deny from 134.209.0.0/16
Deny from 137.184.0.0/16
Deny from 157.245.0.0/20
Deny from 152.42.191.0/24
Deny from 152.42.197.0/24
</pre>

If your site is under attack from other IPs or IP Ranges, you can [[:Contributing_to_the_Wiki | edit the Wiki]] to add more details.

Lily

2025-10-18T20:39:09Z

Krydos: /* .NET */ Added .NET 9

== Lily ==

Lily is a virtual server that runs Windows Server. She is mostly managed by [[:Wolstech|Wolstech]], a root admin.

== How to Request a Lily Account ==

To request an account on Lily, you must already have a Plesk account on Morty, Tommy, or Johnny. Then, please create a new post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] to request that we create an account for you on Lily.

Please note that there is no control panel on Lily, and access is done via FTP. The eventual plan is to rebuild Lily to run Plesk as our other servers do. However there is [[:ETA|no estimated timeframe]] as to when this functionality may be implemented, since there are many other higher-priority projects to be completed first.

== Features ==

== .NET ==

* .NET 1.1
* .NET 2.0
* .NET 3.0
* .NET 3.5
* .NET 4.0
* .NET 4.5
* .NET 4.6
* .NET 4.7
* .NET 5.0
* .NET 6.0
* .NET 8.0
* .NET 9.0
* .NET Core 3.1
* Classic ASP

== PHP ==

All versions of [[:PHP|PHP]] supported have 'exec()' enabled:
* PHP 5.3
* PHP 5.4
* PHP 5.5
* PHP 5.6
* PHP 7.0
* PHP 7.1
* PHP 7.2
* PHP 7.3
* PHP 7.4
* PHP 8.2

== Databases ==

* MariaDB
* MS SQL Server Express 2017

How You Can Help

2025-08-18T02:12:10Z

Krydos: /* Review Us on Trustpilot */ Make the capitalization consistent

== How You Can Help ==

HelioHost provides community-powered free hosting for everyone. There are several ways you can help support us.

== Make a Donation ==

=== Donate via PayPal or Crypto ===

The best way to help us keep providing free hosting is by donating at [https://heliohost.org/donate/ heliohost.org/donate]. You can donate via PayPal, Microsoft Points, Brave Creators, or the cryptocurrencies listed on the page.

In some countries, you can donate using a Debit or Credit Card, so PayPal will act as the card payment processor, but you will not need a PayPal account. If this option is available to you, after clicking on the yellow PayPal button, you should see the 'Donate with Debit or Credit Card' option.

[[File:donate-debit-credit-card.png]]

=== Corporate Donation Matching ===

A lot of employers will make a donation match to approved 501(c)(3) charities, which is what HelioHost is. So, if you donate $100 your job might match your donation and send another $100 to us. You can ask at work to see if your company has a donation matching program like this, and then search for us under 'Helio Networks' or 'HelioHost'.

=== Donate via Charityvest ===

You can [https://www.charityvest.org/charity/helio-networks-d5b1f0df-8759-41c4-91b3-e9e75099579d donate to Helio Networks via Charityvest] and it will be fee-free, since HelioHost is registered with the PayPal Giving Fund, which is the method Charityvest uses to [https://www.charityvest.org/blog/charityvest-implements-paypal-grant-payments-to-enable-electronic-payments-to-charities enable electronic payments to charities].

=== Donate via Facebook ===

In some countries, you can donate on the [https://www.facebook.com/HelioHost.org HelioHost Facebook page].

=== Donate via Brave browser ===

HelioHost is a Verified Creator in the Brave Creators program. This means that if you use the Brave web browser, you can now donate to us by clicking the triangle shape while viewing [https://heliohost.org/ heliohost.org] or [https://helionet.org/ helionet.org] or Plesk, and then clicking Send Contribution. If you have auto-contribute enabled, you can donate to us simply by using our website and forum as you normally would.

If you're not familiar with the Brave browser, check out [https://privacytests.org/ PrivacyTests.org]. Brave is based on Chromium just like Chrome and Edge, but has a built in ad-blocker and annoyance blocker that is better than most extensions you can install on any of the other browsers. You can even get paid to visit websites if you enable the option in the settings and set up a crypto wallet.


=== Donate via Edge browser ===

In some countries, you can donate using the Edge browser by visiting [https://heliohost.org/ heliohost.org] and clicking the 'Donate' button.

=== Donate Cash in Edge ===

You can choose to donate cash via Benevity.

[[File:edge-donate-cash.png]]

=== Donate Microsoft Rewards Points in Edge ===

You can choose to donate using Microsoft Rewards points via Benevity.

{{Danger|Please note that:
* Microsoft Rewards points cannot be used for Morty or Tommy accounts or for the purchase of paid services.
** Donations of Microsoft Rewards points [https://helionet.org/index/topic/63324-hh830443-donations-via-bing/#findComment-285484 cannot be traced back to the individual who made them]. Microsoft combines everything and sends it to us without including any information about the dates of individual donations or details about the people who made them.
** Donations of Microsoft Rewards points [https://helionet.org/index/topic/62006-hh561624-can-i-donate-via-microsoft-rewards/#findComment-280045 can take between at least 2 months] and [https://helionet.org/index/topic/63324-hh830443-donations-via-bing/#findComment-285484 sometimes even up to 6 months] to be received.}}


== Use Our Affiliate Links ==

HelioHost has an affiliate agreement with [https://heliohost.org/partners/namecheap Namecheap], so if you're in the market for a new domain we highly recommend purchasing it from them.

Using the affiliate banner below to sign up and register your domain will not cost you anything extra, but it helps HelioHost earn a bit of commission for the referral.

[[File:Namecheap.png|link=https://heliohost.org/partners/namecheap]]

{{Info|After checking if your preferred domain name is available, sometimes there will be a '''Promo Code''' to get a lower price for the first year.}}

After you've purchased a domain from Namecheap, set the nameservers to '''ns1.heliohost.org''' and '''ns2.heliohost.org''' and we can host the website on your brand new domain for you. For more details, visit our [[:Namecheap_DNS_Records|Namecheap DNS Record Management]] guide.

== Spread the Word ==

=== Refer Your Friends and Family ===

As a small non-profit funded by donations, we don't have a huge budget to afford paid advertising, and rely on word of mouth recommendations so we can find more users and continue to grow. If you know someone who is looking for an affordable VPS, inexpensive or free web hosting, please refer us! '''Note:''' If you share an internet connection or computer with the friend or family member that you refer to us, please [https://helionet.org/index/forum/45-customer-service/?do=add contact us] before they sign up to let us know. Users are only allowed 1 account on the Tommy and Johnny servers, and letting us know ahead of time of the referral enables us to adjust the Duplicate Account Detection System.

=== Put our Banner on your Site ===

You can find some user-contributed HelioHost banner graphics to use in [https://helionet.org/index/topic/28401-put-our-banner-on-your-site/ this HelioNet forum thread].

=== Put our Badge on your Site ===

Find a user-contributed configurable HelioHost badge to add to your site in [https://helionet.org/index/topic/31107-badge/ this HelioNet forum thread].

== Recommend Us ==

=== Recommend us on AlternativeTo ===

If you can think of a competitor to what we offer, find them on [https://alternativeto.net/ AlternativeTo.net] and make sure HelioHost is listed on their page as an alternative option.

To give HelioHost an upvote as an alternative to our competitors, use the links in [https://helionet.org/index/topic/28394-upvote-heliohost-on-alternativetonet/#comment-129850 this HelioNet forum thread].

=== Mention us on Quora ===

Answer a question with a description of HelioHost on [https://www.quora.com/search?q=Web%20Hosting%20Providers Quora.com]. (Must be logged in to your Quora account to view this link.)

== Review Us ==

Write a review about HelioHost at the sites below:

=== Review Us on Trustpilot ===

You may randomly receive an email with a link to review us on Trustpilot. If you receive one of these special links please click the link in the email, and write a 5 star verified review.

{{Danger|Trustpilot deletes most 5 star reviews that don't use the email link, but leaves up any 1 or 2 star reviews that are nonsense or even say in the review that they didn't use our service.}}

We recommend waiting for the email link to make sure your review doesn't get deleted. While you wait for your verified review link, please let us know how much you like HelioHost because we love to hear about it.

=== Review Us on Sitejabber===

* [https://www.sitejabber.com/reviews/heliohost.org Sitejabber]

=== Review Us on Free-Webhosts ===

The details about what HelioHost offers are a little out of date on this site, since a lot has changed since 2018. HelioHost has doubled the storage offered to new accounts, for example. However new users still find us from reviews, so feel free to share your thoughts!

* [http://www.free-webhosts.com/reviews/add-review.php?hostname=HelioHost Free-Webhosts.com]

=== Review Us on WHTop ===

The details about what HelioHost offers are a little out of date on this site, since a lot has changed since 2020. However new users still find us from reviews, so feel free to share your thoughts!

* [http://www.whtop.com/review/heliohost.org#reviews-open WHTop]

== Social Media ==

=== Post about us on Facebook ===

Let your Facebook friends know about us by posting on your timeline using [https://www.facebook.com/share.php?u=http://www.heliohost.org/ this link].

=== Mention us on X (formerly Twitter) ===

Let your followers know you're hosting your website with us by using '@HelioHost' in your tweet. You can use [https://twitter.com/intent/tweet?text=My%20website%20is%20on%20%40heliohost%20the%20community%20powered%20free%20web%20host%20for%20everyone.%20Get%20your%20own%20free%20website%20at%20http%3A%2F%2Fheliohost.org%2F this link].

=== Subscribe to our YouTube channel ===

We regularly post video guides on [https://www.youtube.com/@HelioHostYT YouTube] since some users find it much easier to follow a video guide than a written tutorial.

Subscribe to our channel and like our videos to help us continue to find more users and continue to grow. Please let us know if there is a specific topic that you think would be good for our next video.

== Join the Community ==

HelioHost is community powered. We are active on the platforms below, and welcoming to new users. Please ensure you follow our simple rules.

* [https://helionet.org/index/ HelioNet forum]
** Forum users must follow [[:Terms|these terms]]

* [https://discord.com/invite/y8QJfXg HelioHost Discord channel]
** Channel users must follow [https://discord.com/channels/398197622168616962/419629456794058752/1101198173386571816 these rules]

How You Can Help

2025-08-18T02:11:35Z

Krydos: /* Review Us on Trustpilot */ Removed link to TrustPilot page

== How You Can Help ==

HelioHost provides community-powered free hosting for everyone. There are several ways you can help support us.

== Make a Donation ==

=== Donate via PayPal or Crypto ===

The best way to help us keep providing free hosting is by donating at [https://heliohost.org/donate/ heliohost.org/donate]. You can donate via PayPal, Microsoft Points, Brave Creators, or the cryptocurrencies listed on the page.

In some countries, you can donate using a Debit or Credit Card, so PayPal will act as the card payment processor, but you will not need a PayPal account. If this option is available to you, after clicking on the yellow PayPal button, you should see the 'Donate with Debit or Credit Card' option.

[[File:donate-debit-credit-card.png]]

=== Corporate Donation Matching ===

A lot of employers will make a donation match to approved 501(c)(3) charities, which is what HelioHost is. So, if you donate $100 your job might match your donation and send another $100 to us. You can ask at work to see if your company has a donation matching program like this, and then search for us under 'Helio Networks' or 'HelioHost'.

=== Donate via Charityvest ===

You can [https://www.charityvest.org/charity/helio-networks-d5b1f0df-8759-41c4-91b3-e9e75099579d donate to Helio Networks via Charityvest] and it will be fee-free, since HelioHost is registered with the PayPal Giving Fund, which is the method Charityvest uses to [https://www.charityvest.org/blog/charityvest-implements-paypal-grant-payments-to-enable-electronic-payments-to-charities enable electronic payments to charities].

=== Donate via Facebook ===

In some countries, you can donate on the [https://www.facebook.com/HelioHost.org HelioHost Facebook page].

=== Donate via Brave browser ===

HelioHost is a Verified Creator in the Brave Creators program. This means that if you use the Brave web browser, you can now donate to us by clicking the triangle shape while viewing [https://heliohost.org/ heliohost.org] or [https://helionet.org/ helionet.org] or Plesk, and then clicking Send Contribution. If you have auto-contribute enabled, you can donate to us simply by using our website and forum as you normally would.

If you're not familiar with the Brave browser, check out [https://privacytests.org/ PrivacyTests.org]. Brave is based on Chromium just like Chrome and Edge, but has a built in ad-blocker and annoyance blocker that is better than most extensions you can install on any of the other browsers. You can even get paid to visit websites if you enable the option in the settings and set up a crypto wallet.


=== Donate via Edge browser ===

In some countries, you can donate using the Edge browser by visiting [https://heliohost.org/ heliohost.org] and clicking the 'Donate' button.

=== Donate Cash in Edge ===

You can choose to donate cash via Benevity.

[[File:edge-donate-cash.png]]

=== Donate Microsoft Rewards Points in Edge ===

You can choose to donate using Microsoft Rewards points via Benevity.

{{Danger|Please note that:
* Microsoft Rewards points cannot be used for Morty or Tommy accounts or for the purchase of paid services.
** Donations of Microsoft Rewards points [https://helionet.org/index/topic/63324-hh830443-donations-via-bing/#findComment-285484 cannot be traced back to the individual who made them]. Microsoft combines everything and sends it to us without including any information about the dates of individual donations or details about the people who made them.
** Donations of Microsoft Rewards points [https://helionet.org/index/topic/62006-hh561624-can-i-donate-via-microsoft-rewards/#findComment-280045 can take between at least 2 months] and [https://helionet.org/index/topic/63324-hh830443-donations-via-bing/#findComment-285484 sometimes even up to 6 months] to be received.}}


== Use Our Affiliate Links ==

HelioHost has an affiliate agreement with [https://heliohost.org/partners/namecheap Namecheap], so if you're in the market for a new domain we highly recommend purchasing it from them.

Using the affiliate banner below to sign up and register your domain will not cost you anything extra, but it helps HelioHost earn a bit of commission for the referral.

[[File:Namecheap.png|link=https://heliohost.org/partners/namecheap]]

{{Info|After checking if your preferred domain name is available, sometimes there will be a '''Promo Code''' to get a lower price for the first year.}}

After you've purchased a domain from Namecheap, set the nameservers to '''ns1.heliohost.org''' and '''ns2.heliohost.org''' and we can host the website on your brand new domain for you. For more details, visit our [[:Namecheap_DNS_Records|Namecheap DNS Record Management]] guide.

== Spread the Word ==

=== Refer Your Friends and Family ===

As a small non-profit funded by donations, we don't have a huge budget to afford paid advertising, and rely on word of mouth recommendations so we can find more users and continue to grow. If you know someone who is looking for an affordable VPS, inexpensive or free web hosting, please refer us! '''Note:''' If you share an internet connection or computer with the friend or family member that you refer to us, please [https://helionet.org/index/forum/45-customer-service/?do=add contact us] before they sign up to let us know. Users are only allowed 1 account on the Tommy and Johnny servers, and letting us know ahead of time of the referral enables us to adjust the Duplicate Account Detection System.

=== Put our Banner on your Site ===

You can find some user-contributed HelioHost banner graphics to use in [https://helionet.org/index/topic/28401-put-our-banner-on-your-site/ this HelioNet forum thread].

=== Put our Badge on your Site ===

Find a user-contributed configurable HelioHost badge to add to your site in [https://helionet.org/index/topic/31107-badge/ this HelioNet forum thread].

== Recommend Us ==

=== Recommend us on AlternativeTo ===

If you can think of a competitor to what we offer, find them on [https://alternativeto.net/ AlternativeTo.net] and make sure HelioHost is listed on their page as an alternative option.

To give HelioHost an upvote as an alternative to our competitors, use the links in [https://helionet.org/index/topic/28394-upvote-heliohost-on-alternativetonet/#comment-129850 this HelioNet forum thread].

=== Mention us on Quora ===

Answer a question with a description of HelioHost on [https://www.quora.com/search?q=Web%20Hosting%20Providers Quora.com]. (Must be logged in to your Quora account to view this link.)

== Review Us ==

Write a review about HelioHost at the sites below:

=== Review Us on Trustpilot ===

You may randomly receive an email with a link to review us on TrustPilot. If you receive one of these special links please click the link in the email, and write a 5 star verified review.

{{Danger|TrustPilot deletes most 5 star reviews that don't use the email link, but leaves up any 1 or 2 star reviews that are nonsense or even say in the review that they didn't use our service.}}

We recommend waiting for the email link to make sure your review doesn't get deleted. While you wait for your verified review link, please let us know how much you like HelioHost because we love to hear about it.

=== Review Us on Sitejabber===

* [https://www.sitejabber.com/reviews/heliohost.org Sitejabber]

=== Review Us on Free-Webhosts ===

The details about what HelioHost offers are a little out of date on this site, since a lot has changed since 2018. HelioHost has doubled the storage offered to new accounts, for example. However new users still find us from reviews, so feel free to share your thoughts!

* [http://www.free-webhosts.com/reviews/add-review.php?hostname=HelioHost Free-Webhosts.com]

=== Review Us on WHTop ===

The details about what HelioHost offers are a little out of date on this site, since a lot has changed since 2020. However new users still find us from reviews, so feel free to share your thoughts!

* [http://www.whtop.com/review/heliohost.org#reviews-open WHTop]

== Social Media ==

=== Post about us on Facebook ===

Let your Facebook friends know about us by posting on your timeline using [https://www.facebook.com/share.php?u=http://www.heliohost.org/ this link].

=== Mention us on X (formerly Twitter) ===

Let your followers know you're hosting your website with us by using '@HelioHost' in your tweet. You can use [https://twitter.com/intent/tweet?text=My%20website%20is%20on%20%40heliohost%20the%20community%20powered%20free%20web%20host%20for%20everyone.%20Get%20your%20own%20free%20website%20at%20http%3A%2F%2Fheliohost.org%2F this link].

=== Subscribe to our YouTube channel ===

We regularly post video guides on [https://www.youtube.com/@HelioHostYT YouTube] since some users find it much easier to follow a video guide than a written tutorial.

Subscribe to our channel and like our videos to help us continue to find more users and continue to grow. Please let us know if there is a specific topic that you think would be good for our next video.

== Join the Community ==

HelioHost is community powered. We are active on the platforms below, and welcoming to new users. Please ensure you follow our simple rules.

* [https://helionet.org/index/ HelioNet forum]
** Forum users must follow [[:Terms|these terms]]

* [https://discord.com/invite/y8QJfXg HelioHost Discord channel]
** Channel users must follow [https://discord.com/channels/398197622168616962/419629456794058752/1101198173386571816 these rules]

Configuring Environment

2025-07-28T22:55:05Z

Krydos: /* Python */ .htaccess was missing a c

__FORCETOC__
== Python ==
For Python, Flask, and Django, place your environment variables in a ".env" file located in your app's root directory. This is the same directory that contains your ".htaccess" file. The web server will restrict remote access to this file.

This file should be a list of key/value pairs similar to:
<pre>
DEV_ENV=development
SECRET_API_KEY=***my_secret_key***
</pre>

{{Info|You can add the following code to your ".htaccess" file as an extra explicit instruction for Apache to restrict access}}
<pre>
#hide .env files from http access
<FilesMatch "\.env">
Order allow,deny
Deny from all
</FilesMatch>
</pre>

=== Accessing the variables ===
==== Python and Flask ====
To access your environment variables from python you will nee to load them first using the <code>dotenv</code> package and the operating system environment with <code>os</code>.
<pre>
from dotenv import load_dotenv
from os import environ
</pre>

You will need to give load_dotenv the path to your ".env" file and then access the variables.
<pre>
#replace MY_USER_ID and MY_APP_DIR with your account root and app directory
load_dotenv("/home/MY_USER_ID.helioho.st/MY_APP_DIR/.env")

my_dev_environment = os.environ.get("DEV_ENV") # "development"
</pre>

502 Bad Gateway

2025-07-16T16:18:15Z

Krydos: /* How to Get Rid of 502 Errors */

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to [https://heliohost.org/dashboard/move/ upgrade your hosting plan].

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Minimum Restart !! Maximum Restart
|-
| Johnny || 7.08 minutes || 1.18 minutes || 13.67 minutes
|-
| Tommy || 3.64 minutes || 0.99 minutes || 6.65 minutes
|-
| Morty || 9.87 seconds || 4.45 seconds || 12.52 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

502 Bad Gateway

2025-07-16T16:18:03Z

Krydos: /* How to Get Rid of 502 Errors */

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to [https://heliohost.org/dashboard/move/ upgrade your hosting plan].

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Minimum Restart !! Max Restart
|-
| Johnny || 7.08 minutes || 1.18 minutes || 13.67 minutes
|-
| Tommy || 3.64 minutes || 0.99 minutes || 6.65 minutes
|-
| Morty || 9.87 seconds || 4.45 seconds || 12.52 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

502 Bad Gateway

2025-07-16T16:17:40Z

Krydos: /* How to Get Rid of 502 Errors */ Updated restart times

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to [https://heliohost.org/dashboard/move/ upgrade your hosting plan].

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Min Restart !! Max Restart
|-
| Johnny || 7.08 minutes || 1.18 minutes || 13.67 minutes
|-
| Tommy || 3.64 minutes || 0.99 minutes || 6.65 minutes
|-
| Morty || 9.87 seconds || 4.45 seconds || 12.52 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

Terms

2025-06-19T23:12:06Z

Krydos: /* Terms of Service */ Removed Syria

== Terms of Service ==

By signing up with HelioHost for any service, you agree to the following Terms of Service as well as the [[:#DISCLAIMER|DISCLAIMER]] presented below. If you do not agree to these Terms, you may not use HelioHost. Users who already have an account must [https://heliohost.org/dashboard/delete/ delete their account] if they no longer agree to the Terms.

By signing up with HelioHost for any service, you agree to the following:

* <strong style="color: #ff4d4d; font-size: 120%;">Each person is allowed to have a maximum of one account between Tommy and Johnny. You may not maintain someone else's account on their behalf. </strong><span style="font-size: 120%;">Exceptions to this policy can be requested by contacting support. Approval of such requests is not guaranteed. This policy does not apply to [https://heliohost.org/morty/ Morty] or [https://heliohost.org/vps/ VPS accounts].</span>
* You must be at least 13 years old to use HelioHost.
* Your site will contain no content illegal under US law.
* No phishing. Your site will not collect or attempt to collect personal information by deception.
* No cryptocurrency mining.
* Your website will not offer banking, investment, credit/loans, or similar financial services, as our data center does not meet PCI DSS compliance or ISO/IEC 27001 certification.
* Proxies are not permitted on Plesk plans. Users wishing to host a proxy are encouraged to [https://heliohost.org/vps/ purchase a VPS].
* You may not infringe on any copyrights through your site.
* No IPTV websites. You will not host a streaming video website that offers access to television or movie streams, regardless of the content on offer.
* Your site will not be of a pornographic nature and will refrain from providing pictures and/or photographs of nude men and women.
* Your site will not email, personal message, instant message, or communicate any kind of "spam," or unsolicited bulk advertising of any kind.
* Your site will not offer any form of social media "marketing" service, including but not limited to services that provide "Facebook Likes", "Instagram Followers", or "X Followers". Your account will not store or operate scripts required to provide such services (e.g. "like bots", "follower bots", "smm panels", "sosmed panels").
* Your site will not offer any service that purports to modify or add game content or credits to third-party online game accounts, or that is designed to interrupt, disable, cause a ban from, or otherwise prevent the normal operation of, a third party online game service or account.
* Everything displayed on your site will be your property. HelioHost assumes no responsibility for any content displayed by customers of our services.
* HelioHost is based in the USA. Federal Regulations prohibit us from accepting donations, providing free services, or providing paid services to anyone in Iran, Cuba, or North Korea.
* You will not register or maintain an account using a disposable email address.
* VPS customers only: Your VPS must respond to ICMP pings. This is required by our ISP.
* Refunds are provided pursuant to our [https://heliohost.org/refunds Refund Policy].
* You agree to not hold HelioHost liable for any loss of data, content, revenues, relationships, or traffic that occurs as a result of a systems failure or outage. You understand that HelioHost services are provided '''AS-IS and that HelioHost does not guarantee service availability'''. Services are provided in accordance with our [[#Disclaimer|Service Disclaimer]].
* We reserve the right to change the Terms of Service at any time. An announcement will be made to you via email and our normal [https://helionet.org/index/forum/1-news/ News channels] when we make such changes. If you disagree with the changes, you can decline them by [https://heliohost.org/dashboard/delete/ deleting your account].
* We reserve the right to delete, change, or edit your account or your content with or without prior notification, including, but not limited to cases arising from abuse of these Terms.

== DISCLAIMER ==

HelioHost hosting service is provided 'AS-IS' with NO WARRANTY of any kind, neither express nor implied, not even the implied warranties of merchantability, non-infringement, and fitness for a particular purpose. Furthermore, HelioHost makes no guarantees as to the proper operation of the service, availability of the service, or the safety or security of the service.

HelioHost is NOT LIABLE FOR DATA LOSS, equipment malfunction or failure, or other damages (physical, digital, monetary, or otherwise) caused by the use of this service, the improper operation of the service due to abuse, misuse, or malfunction of any kind, or the quality of the service's performance (or its failure to perform). Use the service at your own risk.

== HelioNet Terms ==

Users on [[:HelioNet|HelioNet]] must abide by the following rules:

* [https://www.helionet.org/index/topic/4-the-official-rules-guide/ Official Rules Guide]
* [https://www.helionet.org/index/topic/2-the-official-spam-guide/ Official Spam Guide]
* [https://www.helionet.org/index/topic/3-the-official-enforcement-guide/ Official Enforcement Guide]
* [https://www.helionet.org/index/topic/1544-the-official-etiquette-guide/ Official Etiquette Guide]

Failure to abide by these terms may result in suspension of ALL HelioNet affiliated accounts, including accounts related to HelioHost, to be determined at HelioNet's sole discretion.

WordPress

2025-06-19T17:13:02Z

Krydos: /* Abusive IPs */ Added another Digital Ocean range

== WordPress ==

WordPress is a popular content management system (CMS) that allows users to easily create and manage websites.

{{Caution|WordPress is known to require a lot of server resources, as it's not very well optimized. Also, the more pages or plugins a WordPress site has, the bigger the site load will be.

Exceeding the account load limits will cause your user account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Accounts on our [[:Morty|Morty]] server will not be suspended but will be charged for account load overages.

If you use WordPress, we recommend you [https://heliohost.org/dashboard/load/ monitor your site load here].

If at any point you become concerned about your account server usage load getting you suspended, you can add "deny from all" to the bottom of your '.htaccess' file to take the site offline. Once that's been done, the site should stop generating load practically instantly.}}

== But my WordPress Site is Brand New / Has No Plugins / Gets Hardly Any Visitor Traffic ==

WordPress causes 0 load with 0 traffic, but sites built with WordPress are prime targets for bot attacks. When bots discover your site URL address, they will keep trying to hack in, which causes load on the server resources.

Even if your WordPress install is brand new, with no plugins, and your site gets few visitors, there is still a risk of bots spamming your site. This could cause your account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Accounts on our [[:Morty|Morty]] server will not be suspended but will be charged for account load overages

Additionally, a lot of free themes and plugins can be backdoors for hackers, and installing them comes with risks. Once bots access your site, they will 'phone home' which then enables hackers to change your site files, set up phishing sites, send spam from your account, etc.

== How Much Server Load Could It Cause? ==

WordPress was one of the apps we load tested, with the benchmark testing results posted on our [[:Common_Software_Load|Common Software Load]] page.

Here are [https://helionet.org/index/topic/57357-solved-disconnect-addon-domain/?do=findComment&comment=252857 some comparison calculations] about how much demand on the server WordPress can cause.

== How Can I Keep My Server Load Low? ==

Our first recommendation is to switch to anything other than WordPress.

=== WordPress Alternatives ===
* Some of our users have switched from WordPress to '''Joomla''' and liked it.
* Another popular alternative is '''Gatsby'''. You can check out a guide on migrating your site [https://www.gatsbyjs.com/blog/2019-03-21-migrating-from-wordpress-to-gatsby/ here] or follow our quick [[:Gatsby|Gatsby tutorial]] to set up a basic site from scratch.
* For static blog generators, '''Publii''' may be an option for you. Please note that as it's local, you will need to upload every time you post. It's not for Android or iOS, and it cannot be synced unless you use a cloud syncing service for the local files. You can check out a guide on how to import data from your WordPress site into Publii [https://getpublii.com/docs/import-wordpress-into-static-html-site.html here].
* '''Jekyll''' is a popular static site generator.
* '''Hugo''' is one of the most popular open-source static site generators.
* '''Grav''' is an open-source flat-file CMS (Content Management System).
* '''Eleventy''' (11ty) offers a simple 'zero-config' option to quickly get a site built. Since it runs on Node, which consumes a lot of memory, we recommend running the build process locally, and then deploying the static pages to your hosting account.
* '''Astro''' is a modern, fast, and flexible web framework. Our [[:Astro|Astro tutorial]] guides you through building and deploying a site with a dedicated blog section.

=== How To Reduce WordPress Server Load ===

If moving away from WordPress is not an option for you, here are other things to try:
* Update everything to the latest version.
* Disable uptime monitors.
* Disable logins.
* Disable unneeded plugins and themes.
* Use caching plugins to reduce the load (users have mentioned that '''WP Fastest Cache''' plugin can be useful).
* Use Cloudflare caching.
* Use Cloudflare and the '''Super Page Cache for Cloudflare''' WordPress plugin to [https://helionet.org/index/topic/57606-handling-cpu-load-spikes-or-high-load-using-cloudflare/ mitigate load spikes or other high load issues].
** If Super Page Cache for Cloudflare tells you to disable the options "Smart static files processing" and "Serve static files directly by Nginx" on the "Apache & Nginx Settings" page of your Plesk panel, you can change these settings yourself by navigating to: Login > Plesk > Websites & Domains > [domain] > Hosting & DNS > Apache & Nginx > Uncheck the 'smart static files processing box' and make sure the 'Serve static files directly by Nginx' box is also unchecked.
* Actively monitor your access logs and look for IPs with an unreasonably high number of hits/page views.
** Block any suspicious / abusive IPs by adding <code>Deny from x.x.x.x</code> to your '.htaccess' file, or block them with Cloudflare if you have a custom domain.
** To check site stats, navigate to: Plesk > Statistics > Web Statistics > your domain > [View].
* Convert to a static site (users have mentioned '''WP2Static''' as being a useful plugin that converts WordPress sites to static sites).
* Upgrade to a [https://heliohost.org/vps/ VPS]. We offer a range of VPS plans, and a 10% discount when you pay for 6 months upfront.

== Abusive IPs ==

HelioHost needed to block the below IP addresses and IP Ranges since some of our WordPress users were under attack from bots coming from these sources. If you use WordPress, we strongly recommend that you add the below to your own .htaccess file to proactively protect your site from IPs known to be abusive.

<pre>
# added by HelioHost - hacking attempt
Deny from 165.22.48.216
Deny from 52.169.95.1
Deny from 52.164.121.3
# these ranges are bots running at Digital Ocean who seems to have an abuse hosting problem
Deny from 104.248.0.0/16
Deny from 104.131.0.0/16
Deny from 104.236.0.0/16
Deny from 165.232.0.0/16
Deny from 107.170.0.0/16
Deny from 128.199.0.0/16
Deny from 134.122.0.0/16
Deny from 134.199.128.0/17
Deny from 134.209.0.0/16
Deny from 137.184.0.0/16
Deny from 157.245.0.0/20
Deny from 152.42.191.0/24
Deny from 152.42.197.0/24
</pre>

If your site is under attack from other IPs or IP Ranges, you can [[:Contributing_to_the_Wiki | edit the Wiki]] to add more details.

Storage

2025-06-16T02:42:15Z

Krydos: /* Donations for Additional Storage */ Add link to self-service storage upgrade

== Account Storage ==

HelioHost offers 1000 MB of web space, with unlimited inodes, for hosting accounts on our [[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]] servers.

This figure combines your stored files (including [[:Account_Backups|account backups]], [[:View_Error_Logs|error logs]], and [[:Unlimited_Email_Accounts | emails]]), your databases, and items in your trash folder.

This should be more than enough to handle any forum, blog, or other script you might need to host. Sites that might encounter problems with this limit include photo galleries with high-megapixel images or online storage sites. In general, this limit should not be a problem to the great majority of hosting users.

== Viewing Your Storage Usage ==

To check how much disk space your account is using, follow the navigation steps below:

'''Login > Plesk > Statistics > Disk space'''

== Reducing Storage Usage ==

To reduce disk usage if you're nearing your account storage limit:
* [[:Account_Backups#Downloading_a_Local_Copy_of_Your_Backup | Download backups]] from inside Plesk and delete them off the server.
* Set a [[:Account_Backups#Limiting_the_Number_of_Backups_Stored_in_Plesk | limit on the number of backups]] stored inside Plesk.
* Change your [[:View_Error_Logs#Limiting_the_Storage_Space_Used_by_Error_Logs | Plesk logging settings]] to make smaller log files.
* Empty your trash folder on a regular basis.
* Delete [[:Unlimited_Email_Accounts | emails]] with large attachments.

== Plesk Storage Calculation ==

Plesk counts the entire contents of your home folder (which includes all addon domains) on your main domain's disk space. It will not display your file storage use distributed across your addon domains. The disk space usage reported for addon domains only consists of things such as log files and mail. This is the standard behavior in Plesk, and cannot be customized.

== Plesk File Storage Recalculation ==

Plesk takes '''up to 24 hours''' to reflect changes to disk space use after files are added or removed. Plesk storage usage recalculation is not done in real time.

== Storage Upgrade Options ==

Sometimes, users wish to increase their account capacity. We offer the following paid options:

== Donations for Additional Storage ==

For each one-time $5 USD donation, users can [[:Donations_for_Increased_Storage|add 1000 MB extra space]] to their account on [[:Morty|Morty]], [[:Tommy|Tommy]], or [[:Johnny|Johnny]], up to a maximum account size of 7000 MB. You can upgrade your storage at [https://heliohost.org/dashboard/storage/ heliohost.org/dashboard/storage]

The storage space, once increased, stays with your account forever. If you switch hosting plans, the storage transfers with your account. If you go inactive and your account is archived, the storage space will still be there years from now when you renew your account.

== Paid VPS Plans ==

For users who wish to pay for more memory, CPUs, or file space, we offer [https://heliohost.org/vps/ VPS plans] with storage options ranging from 50 GB to 300 GB, and a 10% discount when you pay for 6 months upfront.

502 Bad Gateway

2025-05-30T18:52:10Z

Krydos: /* How to Get Rid of 502 Errors */ Updated numbers

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to [https://heliohost.org/dashboard/move/ upgrade your hosting plan].

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Min Restart !! Max Restart
|-
| Johnny || 7.65 minutes || 1.59 minutes || 15.21 minutes
|-
| Tommy || 4.63 minutes || 0.87 minutes || 6.22 minutes
|-
| Morty || 9.37 seconds || 4.30 seconds || 11.62 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

Flask

2025-05-27T02:05:11Z

Krydos: /* Request WSGI Control Access */ Beta ended

== Flask ==

== About Flask ==

Flask is a Python web framework built with a small core and easy-to-extend philosophy. Read more at [https://www.fullstackpython.com/flask.html Full Stack Python].

== Morty server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a [https://heliohost.org/vps/ VPS]. You can get a 10% discount when you pay for 6 months upfront.}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Morty || 5.0.7 || 3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Tommy server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a [https://heliohost.org/vps/ VPS]. You can get a 10% discount when you pay for 6 months upfront.}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Tommy || 5.0.7 || 3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Johnny server ==

{{Info|If you need to run Flask on another version of Python, you'll need to get a [https://heliohost.org/vps/ VPS]. You can get a 10% discount when you pay for 6 months upfront.}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Flask Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Johnny || 3.0.3 || 3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== How To Setup Flask on Plesk ==

== Create a directory on your main domain called 'flasktest'. ==

If you were transferred from the old cPanel, your main domain will be parked on the 'public_html' directory.

If you created a new account on Plesk, your directory will be 'httpdocs'.

== Create an '.htaccess' file inside the 'flasktest' directory with these contents: ==

<pre>
Options +ExecCGI
RewriteEngine On
RewriteBase /
RewriteRule ^(media/.*)$ - [L]
RewriteRule ^(admin_media/.*)$ - [L]
RewriteRule ^(flask\.wsgi/.*)$ - [L]
RewriteRule ^(.*)$ flasktest/flask.wsgi/$1 [QSA,PT,L]
</pre>

== Create a file named 'flask.wsgi' inside the 'flasktest' directory with these contents: ==

{{Caution|Update the code example, beneath where it says "edit your path below", and type in the path to your actual website address, instead of the placeholder 'domain.helioho.st' part.}}

<pre>
import os, sys

# edit your path below
sys.path.append("/home/domain.helioho.st/httpdocs/flasktest");

sys.path.insert(0, os.path.dirname(__file__))
from myapp import app as application

# set this to something harder to guess
application.secret_key = 'secret'
</pre>

== Create a file named 'myapp.py' inside the 'flasktest' directory with these contents: ==

<pre>
import sys

from flask import Flask, __version__
app = Flask(__name__)
application = app

@app.route("/")
def hello():
return """

Flask is working on HelioHost.<br><br>
<a href="/flasktest/python/version/">Python version</a><br>
<a href="/flasktest/flask/version/">Flask version</a>

"""

@app.route("/python/version/")
def p_version():
return "Python version %s<br><br><a href='/flasktest/'>back</a>" % sys.version

@app.route("/flask/version/")
def f_version():
return "Flask version %s<br><br><a href='/flasktest/'>back</a>" % __version__

if __name__ == "__main__":
app.run()
</pre>

== Make sure your directory structure and files look like this: ==

<pre>
flasktest/
├── flask.wsgi
├── .htaccess
└── myapp.py

0 directories, 3 files
</pre>

== If you did everything right it should look like the below: ==

Screenshot taken from [https://krydos.heliohost.org/flasktest https://krydos.heliohost.org/flasktest/]

[[File:flask_test.png]]

== WSGI Uses Caching ==

{{Caution|
Flask changes can take '''up to 2 hours''' to appear consistently on your site because [[:Flask#WSGI_Uses_Server_Side_Caching|WSGI uses server side caching]].

If you want site changes to take effect immediately, we offer [[#Options_to_Work_Around_Caching|a few options to work around caching]].
}}

== What Caching Does ==

Multiple Apache processes are running on the server, and each time you refresh your site you are randomly assigned to one of these processes. If that particular process has already displayed your site, it shows the cached version of your code; otherwise, it shows the new code changes. This means that during the first 2 hours after a site change, you may intermittently see old or new content, depending on which process you get assigned to. This situation will resolve when Apache is restarted, which happens every 2 hours.

== Options to Work Around Caching ==

== Request WSGI Control Access ==

A new feature currently available only on the [[:Morty]] plan is the ability for users to restart their Flask app themselves. Please note that this feature takes '''at a minimum''' 260 GB memory per day, which will result in a bill of '''$1.91 or more'''.

To try to keep the cost as low as possible, users on Morty also have the option to request that WSGI Control Access be temporarily enabled it to allow for debugging. Once they have completed troubleshooting, they can request for WSGI Control Access to be disabled.

WSGI Control Access is no longer available on the [[:Tommy]] and [[:Johnny]] servers.

Once you have created a Flask app that has a 'dispatch.wsgi' file, create a new post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# The domain name(s) for which you want WSGI Control Access. '''Note:''' If you have 2 Flask apps on 2 different domains, you need to request WSGI Control Access for each domain.

Once you have been given WSGI Control Access on Morty, you can edit your 'flask.wsgi' to reload your Flask app so new code changes load immediately. The edits to the file can be as simple as adding or removing a space or a blank line. As long as the file's 'last modified date' changes it will discard the cache and reload your Flask app.

Please let us know if you experience unexpected results with this new feature.

== Account Resets Remove WSGI Control Access ==

{{Info|
If you [[:FAQ#How_do_I_reset_my_hosting_account_to_start_fresh|request an account reset]] you will need to re-request WSGI Control Access after the reset has been completed. By default, account resets will disable WSGI Control Access.
}}

== Use Local Development Environment ==

Another option to see code changes reflected immediately is to develop your Django app on your home computer and then host the production copy on the server. This is a useful approach for users on the [[:Tommy]] and [[:Johnny]] servers, where WSGI Control Access is no longer offered.

== VPS ==

You may prefer to explore one of our paid [https://heliohost.org/vps/ VPS plans], depending on your requirements. You can get a 10% discount when you pay for 6 months upfront.

== Troubleshooting ==

If you receive an error of 'You don't have permission to access /flasktest/flask.wsgi/ on this server', you may need to add 'AddHandler cgi-script .py' on a new line in your '.htaccess' file.

== Running Flask at the Webroot ==

The above example is for Flask in a subdirectory, so users can host different projects in different subdirectories rather than dedicating the whole domain to one Flask app.

If you prefer to run Flask at the webroot instead, this is possible with some slight changes to the '.htaccess', 'flask.wsgi', and 'myapp.py' files.

== References ==

This tutorial is adapted from the [https://helionet.org/index/topic/53856-how-to-use-flask-on-plesk/ How to Use Flask on Plesk] post on the HelioNet forum, answered by Krydos.

== Further Support ==

If this tutorial has not worked for you, please go back and check all of your steps again to make sure you didn't miss anything. If you can't figure out what is wrong, please check your account [[:View_Error_Logs | error logs]], since these will often provide information that can help you resolve the problem. If you're still stuck, please post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''' and any '''error message(s)''' received.

[[Category:Tutorials]]

502 Bad Gateway

2025-05-24T17:39:09Z

Krydos: /* How to Get Rid of 502 Errors */ Add another link

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to [https://heliohost.org/dashboard/move/ upgrade your hosting plan].

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Min Restart !! Max Restart
|-
| Johnny || 7.44 minutes || 1.58 minutes || 16.76 minutes
|-
| Tommy || 4.63 minutes || 1.04 minutes || 6.22 minutes
|-
| Morty || 8.72 seconds || 5.83 seconds || 11.62 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

502 Bad Gateway

2025-05-13T18:03:46Z

Krydos: /* How to Get Rid of 502 Errors */ Updated Apache restart times

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to upgrade your hosting plan.

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Min Restart !! Max Restart
|-
| Johnny || 7.44 minutes || 1.58 minutes || 16.76 minutes
|-
| Tommy || 4.63 minutes || 1.04 minutes || 6.22 minutes
|-
| Morty || 8.72 seconds || 5.83 seconds || 11.62 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

Johnny

2025-04-28T19:31:07Z

Krydos: /* Uptime Goal */ Missecd changing 1 Tommy to Johnny in the copy/pasta

== Johnny ==

Johnny is our free server, offering great stability, speed, and uptime.

Because of Johnny's popularity, [https://heliohost.org/signup/ new account signups] are available on a limited basis twice a day, at noon and midnight UTC. Please see our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny|list of helpful tips for getting a free account on Johnny]].

To keep your account on Johnny active, make sure you [[:Suspension_Policy#Inactivity_Policy|log in at least once a month]].

== Uptime Goal ==

Our goal for the Johnny server is to keep the uptime at or above 97.00%. This is not a Service Level Agreement (SLA), and we make no guarantees about our service or uptime. If the uptime is at or above 97.00% we consider this to be an acceptable level and there is no problem. If the uptime is below 97.00% we consider this a problem, and we are working to improve the situation. You can read more about why we don't provide [[:ETA#ETA_for_New_Features,_Version_Upgrades,_and_Server_Repairs|SLAs or ETAs]]. If you are dissatisfied with performance of the Johnny server you can take a look at how to [[:Moving_Your_Account|move your account to a better server]]. You can see the historical uptime and performance data for Johnny on our [https://status.heliohost.org/history/johnny Johnny status page].

== Features ==

* [[:Plesk_Features|Plesk]]
* [[:Golang|Golang]]
* [[:MySQL|MySQL]]
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

Johnny

2025-04-28T19:30:25Z

Krydos: Added uptime goal

== Johnny ==

Johnny is our free server, offering great stability, speed, and uptime.

Because of Johnny's popularity, [https://heliohost.org/signup/ new account signups] are available on a limited basis twice a day, at noon and midnight UTC. Please see our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny|list of helpful tips for getting a free account on Johnny]].

To keep your account on Johnny active, make sure you [[:Suspension_Policy#Inactivity_Policy|log in at least once a month]].

== Uptime Goal ==

Our goal for the Johnny server is to keep the uptime at or above 97.00%. This is not a Service Level Agreement (SLA), and we make no guarantees about our service or uptime. If the uptime is at or above 97.00% we consider this to be an acceptable level and there is no problem. If the uptime is below 97.00% we consider this a problem, and we are working to improve the situation. You can read more about why we don't provide [[:ETA#ETA_for_New_Features,_Version_Upgrades,_and_Server_Repairs|SLAs or ETAs]]. If you are dissatisfied with performance of the Tommy server you can take a look at how to [[:Moving_Your_Account|move your account to a better server]]. You can see the historical uptime and performance data for Johnny on our [https://status.heliohost.org/history/johnny Johnny status page].

== Features ==

* [[:Plesk_Features|Plesk]]
* [[:Golang|Golang]]
* [[:MySQL|MySQL]]
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

Morty

2025-04-28T19:28:05Z

Krydos: /* Uptime Goal */ Mentioned moving to VPS if Morty isn't good enough

== Morty ==

Morty is our flagship production server, available only to paid subscribers. Morty is the fastest server we have ever built, running on the fastest processor we have ever purchased, using the fastest SSD raid array we have ever had, and the fastest memory our processor supports. Thanks to 82 amazing donors during our 2023 fundraiser, we were able to raise enough money to purchase our newest server which is home to Morty, among other things.

In November 2024, donors from our last fundraiser were transferred over to Morty and they spent a few weeks beta testing. The few issues found were fixed, and Morty was opened to account transfers from existing users in December 2024.

The [[:Moving_Your_Account|account move]] page in the dashboard is 100% automated, so if you decide to move to Morty you can do so without any help from an admin, and without even talking to anyone if you don't want to. That said, we would love to hear what you have to say about our new server if you decide to try it out, or if you have any feedback about the transfer process.

== No Login Requirement ==

Unlike our other shared hosting servers, Morty has no requirement to log in to your account every 30 days to keep it active. As long as there is a positive balance on your account, it will remain active.

== Pricing ==

There will eventually be two ways to pay for Morty, the monthly subscription and the prepay option. Right now only the prepay option is available, but you can get $6 of Morty balance for only $5, which could keep your website online for 6 months. There is also the option to buy $12 balance and $24 balance for discounted rates.

== Adding Funds to Morty Account ==

To add funds to your Morty account, go to [https://heliohost.org/donate/ heliohost.org/donate] and type in the amount you want to add. Once the transaction is complete, create a new topic in the [http://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and provide:
# Your account '''username'''
# The '''Transaction ID'''

Once an admin confirms the transaction, the funds will be added to your Morty account balance.

The ability to add funds to your Morty account will eventually be built into the account dashboard, but there is [[:ETA | no ETA]] for when this will be completed. Once this feature is available, it will be announced in the HelioNet [https://helionet.org/index/forum/1-news/ News] section, as well as elsewhere on our site and our social media.

=== Providing PayPal Transaction ID ===

Some users are hesitant to provide their PayPal transaction ID. Please refer to this post by a PayPal employee explaining that [https://www.paypal-community.com/t5/Refunds-and-cancellations/OK-TO-RELEASE-PAYPAL-TRANSACTION-ID-NUMBER/td-p/719651 providing your transaction ID to your seller is perfectly safe].

== Account Load Overage Charges ==

Keep in mind if your account uses more than {{Template:MemoryLimit}} memory or 10k CPU in a day we will charge you an extra $0.0005 per 1 GB memory and $0.005 per 1k CPU rather than suspending you. So if you have a lot of overages the $6 balance won't last you a full 6 months, but we will email you when the balance gets low.

For up to date information on Morty, check out the HelioNet Forum [https://helionet.org/index/forum/1-news/ News section].

== Uptime Goal ==

Our goal for the Morty server is to keep the uptime at or above 99.99%. This is not a Service Level Agreement (SLA), and we make no guarantees about our service or uptime. You can read more about why we don't provide [[:ETA#ETA_for_New_Features,_Version_Upgrades,_and_Server_Repairs|SLAs or ETAs]]. If you are dissatisfied with performance of the Morty server you can [https://heliohost.org/vps/ move your domain(s) to a VPS] or read our [[:Refunds|refund policy]]. You can see the historical uptime and performance data since Morty was created on our [https://status.heliohost.org/history/morty Morty status page].

== Features ==

* [[:Plesk_Features|Plesk]]
* [[:Golang|Golang]]
* [[:MySQL|MySQL]]
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

Tommy

2025-04-28T19:26:28Z

Krydos: Added uptime goal section and disclaimers about no SLA

== Tommy ==

Tommy is our exclusive donor server offering stability and speed suitable for production sites.

We offer various [https://heliohost.org/tommy/ Donor Plans], and for a one-time donation of as little as $1 USD, you can open an account any time of day.

To keep your account on Tommy active, make sure you [[:Suspension_Policy#Inactivity_Policy|log in at least once a month]].

== Uptime Goal ==

Our goal for the Tommy server is to keep the uptime at or above 99.50%. This is not a Service Level Agreement (SLA), and we make no guarantees about our service or uptime. If the uptime is at or above 99.50% we consider this to be an acceptable level and there is no problem. If the uptime is below 99.50% we consider this a problem, and we are working to improve the situation. You can read more about why we don't provide [[:ETA#ETA_for_New_Features,_Version_Upgrades,_and_Server_Repairs|SLAs or ETAs]]. If you are dissatisfied with performance of the Tommy server you can take a look at how to [[:Moving_Your_Account|move your account to a better server]] or read our [[:Refunds|refund policy]]. You can see the historical uptime and performance data for Tommy on our [https://status.heliohost.org/history/tommy Tommy status page].

== Features ==

* [[:Plesk_Features|Plesk]]
* [[:Golang|Golang]]
* [[:MySQL|MySQL]]
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

Morty

2025-04-28T19:18:45Z

Krydos: Added uptime goal section and disclaimer about no guarantees

== Morty ==

Morty is our flagship production server, available only to paid subscribers. Morty is the fastest server we have ever built, running on the fastest processor we have ever purchased, using the fastest SSD raid array we have ever had, and the fastest memory our processor supports. Thanks to 82 amazing donors during our 2023 fundraiser, we were able to raise enough money to purchase our newest server which is home to Morty, among other things.

In November 2024, donors from our last fundraiser were transferred over to Morty and they spent a few weeks beta testing. The few issues found were fixed, and Morty was opened to account transfers from existing users in December 2024.

The [[:Moving_Your_Account|account move]] page in the dashboard is 100% automated, so if you decide to move to Morty you can do so without any help from an admin, and without even talking to anyone if you don't want to. That said, we would love to hear what you have to say about our new server if you decide to try it out, or if you have any feedback about the transfer process.

== No Login Requirement ==

Unlike our other shared hosting servers, Morty has no requirement to log in to your account every 30 days to keep it active. As long as there is a positive balance on your account, it will remain active.

== Pricing ==

There will eventually be two ways to pay for Morty, the monthly subscription and the prepay option. Right now only the prepay option is available, but you can get $6 of Morty balance for only $5, which could keep your website online for 6 months. There is also the option to buy $12 balance and $24 balance for discounted rates.

== Adding Funds to Morty Account ==

To add funds to your Morty account, go to [https://heliohost.org/donate/ heliohost.org/donate] and type in the amount you want to add. Once the transaction is complete, create a new topic in the [http://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and provide:
# Your account '''username'''
# The '''Transaction ID'''

Once an admin confirms the transaction, the funds will be added to your Morty account balance.

The ability to add funds to your Morty account will eventually be built into the account dashboard, but there is [[:ETA | no ETA]] for when this will be completed. Once this feature is available, it will be announced in the HelioNet [https://helionet.org/index/forum/1-news/ News] section, as well as elsewhere on our site and our social media.

=== Providing PayPal Transaction ID ===

Some users are hesitant to provide their PayPal transaction ID. Please refer to this post by a PayPal employee explaining that [https://www.paypal-community.com/t5/Refunds-and-cancellations/OK-TO-RELEASE-PAYPAL-TRANSACTION-ID-NUMBER/td-p/719651 providing your transaction ID to your seller is perfectly safe].

== Account Load Overage Charges ==

Keep in mind if your account uses more than {{Template:MemoryLimit}} memory or 10k CPU in a day we will charge you an extra $0.0005 per 1 GB memory and $0.005 per 1k CPU rather than suspending you. So if you have a lot of overages the $6 balance won't last you a full 6 months, but we will email you when the balance gets low.

For up to date information on Morty, check out the HelioNet Forum [https://helionet.org/index/forum/1-news/ News section].

== Uptime Goal ==

Our goal for the Morty server is to keep the uptime at or above 99.99%. This is not a Service Level Agreement (SLA), and we make no guarantees about our service or uptime. You can read more about why we don't provide [[:ETA#ETA_for_New_Features,_Version_Upgrades,_and_Server_Repairs|SLAs or ETAs]]. If you are dissatisfied with performance of the Morty server you can read our [[:Refunds|refund policy]]. You can see the historical uptime and performance data since Morty was created on our [https://status.heliohost.org/history/morty Morty status page].

== Features ==

* [[:Plesk_Features|Plesk]]
* [[:Golang|Golang]]
* [[:MySQL|MySQL]]
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

502 Bad Gateway

2025-04-21T20:44:14Z

Krydos: /* How to Get Rid of 502 Errors */ added comma

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime, is to upgrade your hosting plan.

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Min Restart !! Max Restart
|-
| Johnny || 5.33 minutes || 1.55 minutes || 15.39 minutes
|-
| Tommy || 5.08 minutes || 1.05 minutes || 11.11 minutes
|-
| Morty || 6.26 seconds || 4.82 seconds || 9.80 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

502 Bad Gateway

2025-04-21T20:43:33Z

Krydos: Added information about how to get rid of 502 errors

== 502 Bad Gateway ==

== Apache Restarts ==

Apache restarts happen every 2 hours on the shared hosting servers. During the restarts on the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, your site may display a 502 error to visitors. On the [[:Morty|Morty]] server, a [[:504_Gateway_Timeout|504 error]] may display. These errors typically last no longer than a couple of minutes and are resolved once Apache has finished restarting.

The difference in error messages (502 vs. 504) is because of different restart methods used. A hard restart interrupts Apache abruptly, leading to a 502 (Bad Gateway), and a graceful restart will give the 504 (Gateway Timeout). The restart approach on Tommy and Johnny is different in order to minimize downtime and address user concerns about longer wait times for their sites to come back up after server restarts. Because the wait time for restarts on Morty was already minimal, the graceful approach is preferred for this server.

To check the status of our servers, please visit the visit the [https://status.heliohost.org/ HelioHost Services Status Page]. The status page provides a real-time overview of your server’s status and includes a history of past incidents.

== How to Get Rid of 502 Errors ==

If you see frequent 502 errors on your website, the best way to fix the issue and get better uptime is to upgrade your hosting plan.

{| class="wikitable" style="margin:auto"
|-
! Plan !! Average Restart !! Min Restart !! Max Restart
|-
| Johnny || 5.33 minutes || 1.55 minutes || 15.39 minutes
|-
| Tommy || 5.08 minutes || 1.05 minutes || 11.11 minutes
|-
| Morty || 6.26 seconds || 4.82 seconds || 9.80 seconds
|}

If the Apache restarts take less than 30 seconds no error messages are displayed, and it counts as 100% uptime. Tommy is a little better than Johnny, but we recommend switching to Morty if you want to get rid of the 502 errors entirely. You can upgrade your existing account to the Morty plan at [https://heliohost.org/dashboard/move/ heliohost.org/dashboard/move].

You can also upgrade to a [https://heliohost.org/vps/ VPS Plan] to fix the 502 errors. On a [https://heliohost.org/vps/ VPS Plan] there are no other users sharing the server with you, so Apache only restarts when you restart it yourself. You can leave it running without a restart for months if you want to. We offer a range of [https://heliohost.org/vps/ VPS Plans], and a 10% discount when you pay for 6 months upfront.

Converting an Existing Django App

2025-04-06T18:07:53Z

Krydos: /* Create a new project called 'djangotest' */ Removed word 'text'

== Converting an Existing Django App to work on HelioHost ==

== About Django ==

Django is a web development framework designed specifically for Python. As Ruby on Rails does for Ruby, Django aims to provide an MVC (Model-View-Controller) architecture for web application development as well as a large set of prebuilt libraries to simplify the development of common web app features. Django's modularity also allows easy scalability and enables the reuse of various code blocks, aligning to the DRY ("Don't Repeat Yourself") software development principle.

== Django Versions Available ==

{{Info|If you need to run Django on another version of Python, you'll need to get a [https://heliohost.org/vps/ VPS]. We offer a range of VPS plans, and a 10% discount when you pay for 6 months upfront.}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Django Version !! Python Version !! Python Modules Installed !! Python Path !! Loader
|-
| Morty || 5.0.7 || 3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|-
| Tommy || 5.0.7 || 3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|-
| Johnny || 5.0.7 || 3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View] || /usr/bin/python3.12 || WSGI
|}

== Enabled ==

== WSGI ==

Using the WSGI loader for a shared hosting environment is ideal because it conserves memory and enhances security.

{{Caution|
Django changes can take '''up to 2 hours''' to appear consistently on your site because [[:Converting_an_Existing_Django_App#WSGI_Uses_Server_Side_Caching|WSGI uses server side caching]].

If you want site changes to take effect immediately, we offer [[:Converting_an_Existing_Django_App#Options_to_Work_Around_Caching|a few options to work around caching]].
}}

== Complete Django ==

We offer the complete, unadulterated Django package, including extensions to interface with [[:MySQL|MySQL]], [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Info|Before requesting additional modules, make sure you check the list of modules already installed. Please do not request modules that are already installed.}}

{| class="wikitable" style="margin:auto"
|-
! Server !! Python Modules Installed
|-
| Morty || [https://krydos3.heliohost.org/pyinfo/info3.12.py View]
|-
| Tommy || [https://krydos1.heliohost.org/pyinfo/info3.12.py View]
|-
| Johnny || [https://krydos2.heliohost.org/pyinfo/info3.12.py View]
|}

After checking the list of modules that are already installed, if you need to request additional libraries, please raise a request in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', your '''server''', and '''the libraries you need''' including any relevant '''version numbers''' for them.

== Disabled ==

== Shell Access ==

We don't offer shell (command line) access to our users. Many Django tutorials and installation instructions assume that users have command line access, which may make working with Python & Django more difficult. Most people tend to develop on their home computer and then upload to their web server, which almost negates the need for this feature. Furthermore, most configuration done through the command line can be done through other methods, such as FTP and manual file editing.

== WSGI Daemon Mode ==

There are two ways to configure Django to work with the mod_wsgi loader in Apache. You can either create a separate daemon for each Django process (daemon mode) or embed Django into the Apache daemon (embedded mode). While daemon mode tends to be the standard among Django admins because of the increased control it offers, we use embedded mode because it can be set up on a per-user basis without very much root-level configuration. Embedded mode is slightly harder to get working (see directions below), and might break compatibility with some Django tutorials. In most cases, it should not be a problem.

== Converting an Existing Django App to work on HelioHost ==

This tutorial will guide you through using the command line on your development system to convert an existing Django app for hosting on HelioHost.

If you prefer not to use the command line, our brief [[:Django_on_HelioHost|Django on HelioHost]] tutorial may better suit your needs.

We recommend referring to the [https://docs.djangoproject.com/ official Django documentation] and following the introduction tutorial relevant to the Django version you are using. We also suggest using 'virtualenv' to differentiate each Django installation for each project. The below tutorial has been designed for Linux users, but Windows users should work it out easily.

'''Conventions:''' The following commands don't need root access to be executed. Shell commands are preceded by a '$' (dollar sign) to differentiate them from the output.
The Python executable name used on the local computer is 'python3', but this can vary depending on the distribution used, so change it as needed to match your system requirements.

== Create a new project called 'djangotest' ==

On your local computer, open a terminal, create a new project and perform the minimal configuration:

<pre>
$ django-admin startproject djangotest
$ cd djangotest/ && python3 manage.py migrate
</pre>

== Verify Project Structure ==

The below directory structure, with a 'djangotest' folder nested inside another 'djangotest' folder, is standard for a Django project. Please note that you cannot name the project folder 'django', it will not work. This is why the name 'djangotest' has been used for this tutorial.

Make sure that your directory structure and files look like this:

<pre>
$ tree ../djangotest/

../djangotest/
├── db.sqlite3
├── djangotest
│ ├── __init__.py
│ ├── __pycache__/
│ │ ├── ...
│ ├── asgi.py
│ ├── settings.py
│ ├── urls.py
│ └── wsgi.py
└── manage.py

2 directories, 10 files
</pre>

== Run the Test Server ==

Inside the first (outer) 'djangotest' folder, start the testing server.

<pre>
$ python3 manage.py runserver 0.0.0.0:8000

Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
May 31, 2024 - 18:12:55
Django version 4.1, using settings 'djangotest.settings'
Starting development server at http://0.0.0.0:8000/
Quit the server with CONTROL-C.
</pre>

== Open Test Server in Browser ==

By using the test server, you can develop the app on your local computer and changes you make will take effect immediately.

Point your web browser to [http://127.0.0.1:8000/ http://127.0.0.1:8000] and you should see a message confirming the installation worked successfully:

[[File:django-install-success.png]]

== Configuring the Project for Deployment ==

{{Caution|
Django changes can take '''up to 2 hours''' to appear consistently on your site because [[:Converting_an_Existing_Django_App#WSGI_Uses_Server_Side_Caching|WSGI uses server side caching]].

If you want site changes to take effect immediately, we offer [[:Converting_an_Existing_Django_App#Options_to_Work_Around_Caching|a few options to work around caching]].
}}

== Rename the 'wsgi.py' file to 'dispatch.wsgi' ==

To prepare the project for deployment, rename the 'wsgi.py' file to 'dispatch.wsgi'. Both files are inside the second (inner) 'djangotest' folder.

<pre>
$ mv djangotest/wsgi.py djangotest/dispatch.wsgi
</pre>

== Create an '.htaccess' file ==

Inside the first (outer) 'djangotest' folder, create an '.htaccess' file with these contents:

<pre>
Options +ExecCGI
RewriteEngine On
RewriteBase /
RewriteRule ^(media/.*)$ - [L]
RewriteRule ^(admin_media/.*)$ - [L]
RewriteRule ^(djangotest/dispatch\.wsgi/.*)$ - [L]
RewriteRule ^(.*)$ djangotest/djangotest/dispatch.wsgi/$1 [QSA,PT,L]
</pre>

This instructs Apache to redirect all the requests (except those requesting something from 'media/' or 'admin_media/') to the dispatcher file.

== Edit the 'dispatch.wsgi' file ==

Inside the second (inner) 'djangotest' folder, edit the dispatcher file 'dispatch.wsgi' to instruct it how to load your Django settings. Change it from:

<pre>
import os

from django.core.wsgi import get_wsgi_application

os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'djangotest.settings')

application = get_wsgi_application()
</pre>

To the below:

<pre>
import os, sys

# edit your path below
sys.path.append("/home/domain.helioho.st/httpdocs/djangotest")

from django.core.wsgi import get_wsgi_application
os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'djangotest.settings')
application = get_wsgi_application()
</pre>

{{Caution|Update the code example, beneath where it says "edit your path below", and type in the path to your actual website address, instead of the placeholder 'domain.helioho.st' part.

On Plesk, your path is "/home/domain.helioho.st/httpdocs/djangotest"

If you were transferred from cPanel, your path is "/home/domain.helioho.st/public_html/djangotest"}}

== Edit the 'urls.py' file ==

Inside the second (inner) 'djangotest' folder, edit the 'urls.py' file. Change it from:

<pre>
from django.contrib import admin
from django.urls import path

urlpatterns = [
path('admin/', admin.site.urls),
]
</pre>

To the below:

<pre>
from django.contrib import admin
from django.urls import path

urlpatterns = [
# path('admin/', admin.site.urls),
]
</pre>

Commenting out the path to the admin interface is done for security reasons, to prevent unauthorized access to the admin panel in a production environment.

== Edit the 'settings.py' file ==

Inside the second (inner) 'djangotest' folder, edit the 'settings.py' file.

Adding the web server address to the app settings will allow the web server to serve your Django app. Change it from:

<pre>
ALLOWED_HOSTS = []
</pre>

To the below:

<pre>
ALLOWED_HOSTS = ["*"]
</pre>

This will ensure that your website (such as 'domain.heliohost.us') can serve your application from any custom domains you have (such as 'domain.com') as well as every subdomain (such as 'www').

== Upload Your Project to HelioHost ==

Upload the entire first (outer) 'djangotest' folder to your main domain. Make sure that your directory structure and files look like this:

<pre>
home/
└── domain/
└── httpdocs/
├── .htaccess
├── db.sqlite3
├── manage.py
└── djangotest/
└── djangotest/
├── __init__.py
├── asgi.py
├── dispatch.wsgi
├── settings.py
├── urls.py
└── __pycache__/
├── ...
</pre>

== Visit Your Deployed Site ==

{{Caution|
Django changes can take '''up to 2 hours''' to appear consistently on your site because WSGI uses server side caching.

If you want site changes to take effect immediately, we offer a few options to work around caching.
}}

In your web browser, navigate to 'domain.helioho.st/djangotest'

If you did everything right it should look like this:

[[File:django-install-success.png]]

== WSGI Uses Server Side Caching ==

== What WSGI Server Side Caching Does ==

Multiple Apache processes are running on the server, and each time you refresh your site you are randomly assigned to one of these processes. If that particular process has already displayed your site, it shows the cached version of your code; otherwise, it shows the new code changes. This means that during the first 2 hours after a site change, you may intermittently see old or new content, depending on which process you get assigned to. This situation will resolve when Apache is restarted, which happens every 2 hours.

== Options to Work Around Caching ==

== Request WSGI Control Access ==

A new feature currently in beta is the ability for users to restart their Django app themselves.

Once you have created a Django app that has a 'dispatch.wsgi file', create a new post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and provide your '''username''', '''server name''', and the '''domain name(s)''' for which you want WSGI Control Access. (If you have 2 Django apps on 2 different domains, you need to request WSGI Control Access for each domain.)

Once you have been given WSGI Control Access, you can edit your 'dispatch.wsgi' to reload your Django app so new code changes load immediately. The edits to the file can be as simple as adding or removing a space or a blank line. As long as the file's 'last modified date' changes, it will discard the cache and reload your Django app.

Please let us know if you experience unexpected results with this new feature.

== Account Resets Remove WSGI Control Access ==

{{Info|
If you [[:FAQ#How_do_I_reset_my_hosting_account_to_start_fresh|request an account reset]] you will need to re-request WSGI Control Access after the reset has been completed. By default, account resets will disable WSGI Control Access.
}}

== Use Local Development Environment ==

Another option to see code changes reflected immediately is to develop your Django app on your home computer and then host the production copy on the server.

== VPS ==

You may prefer to explore one of our paid [https://heliohost.org/vps/ VPS Plan] options, depending on your requirements. We offer a range of VPS plans, and a 10% discount when you pay for 6 months upfront.

== References ==

* This tutorial is adapted from [https://www.helionet.org/index/topic/27585-django-on-tommy/?p=126077 this post] on the HelioNet forum.
* A ready-made template using an older Django version (1.11) is available at [https://github.com/rahul-gj/cookiecutter-helio https://github.com/rahul-gj/cookiecutter-helio].

Signing Up

2025-04-02T21:38:35Z

Krydos: /* Helpful Tips for Getting a Free Account on Johnny */ Added images for people who can't read

== Signing Up ==

== Before Signup ==

== Why should I choose Morty? ==

[[:Morty]] is our flagship production server, available only to paid subscribers. Morty is the fastest server we have ever built, running on the fastest processor we have ever purchased, using the fastest SSD raid array we have ever had, and the fastest memory our processor supports.

== Why should I choose Tommy? ==

[[:Tommy|Tommy]] is our exclusive donor server offering stability and speed suitable for production sites.

Tommy is closed for free signups, but [https://heliohost.org/tommy/ Donor Signups] are always available.

== Why should I choose Johnny? ==

[[:Johnny|Johnny]] is our free server, offering great stability, speed, and uptime.

== During Signup ==

== Usernames are not private ==

{{Caution|
When creating your account username, please note that if you need support, you will be asked to provide this username for account identification, where it may be visible to other users.

Please avoid using any private information in your username.
}}

[[File:Username-is-not-private.png]]

== "That plan is already full for the day" message ==

To prevent the free Johnny server from getting overloaded with masses of new accounts, we put a limit on the number of people who can sign up. This limit resets [https://helionet.org/index/topic/59660-midnight-and-noon/ every 12 hours], at midnight UTC and noon UTC.

To find out when to sign up, check the 'Opens in' text field, shown on the very bottom of the Johnny tile.

You can also see how long the free signups slot was open for last time by checking the 'Last signup open' text in the last bullet point on the tile.

[[File:johnny-signup-tile.png]]

== Helpful Tips for Getting a Free Account on Johnny ==

1. Make sure your computer's or phone's time and time zone is set correctly, and synced up with a time server. The website [https://time.is/ time.is] is a great way to check if your device time is correct. For instance, if you see something like this you would know you need to sync your clock.

[[File:Johnny-tips time-is.png]]

If the [https://time.is/ time.is] website says your time isn't exact, you'll need to update it in the OS. If you're using Windows 11 you would open settings and go to '''Time & Language > Date & Time''', and then click 'Sync now'. The way to sync the time on other phones or operating systems may vary slightly.

[[File:Johnny-tips sync-time.png]]

Once your OS time is synced up try the [https://time.is time.is] website and you should see this.

[[File:Johnny-tips exact-time.png]]

2. Make sure Javascript works in your browser. The bottom of the Johnny tile should count down as you get closer to noon and midnight UTC.

[[File:Johnny-tips countdown.png]]

3. When the time gets down to 30 seconds or less, you can begin clicking as fast as you can on the Johnny tile:
* If signups aren't open yet it will just give the red 'That plan is already full for the day' message.
* If signups are open it will take you to a page to enter your email address.

4. Once it asks you for your email address you have a spot reserved for at least an hour and you don't need to rush through the rest of the signup process.

Free signups fill up fast, sometimes in even less than a second. If you miss the free signups timeslot, be ready to try again next time if needed.

{{Info|
There are no exceptions to the free signup timeframes. If you cannot sign up during the 2 daily timeslots when Johnny is open for free signups, we offer various [https://heliohost.org/tommy/ Donor Plans], so for a one-time donation of as little as $1 USD, you can open an account on Tommy any time of day without needing to wait.
}}

== What is HelioNet? ==

HelioNet is located at [http://helionet.org helionet.org] and is a discussion board where users like yourself can request support. The friendly staff and the community will attempt to answer your questions as best as they can.

{{Info|When you create your hosting account, a HelioNet forum account with the same username and password is created for you.}}

If you need assistance, you can post on the HelioNet [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum] and the administrators can easily identify you by username.

Learn more about [[:HelioNet|the history of HelioNet]].

== After Signup ==

== Up to 2 hours for activation ==

{{Info|It can take '''up to 2 hours''' for your account to be fully active.}}

The HelioHost Dashboard will display a message advising you that your account has been created and you can login to Plesk. However, it may take '''up to 2 hours''' for your domain to begin working.

In the meantime, your website may not load or display correctly, and file changes you make may not take effect. Please be patient and wait for '''the full 2 hours''' before assuming anything is broken.

[[File:Dashboard-up-to-2-hours.png]]

== Check account activation status ==

To check the status of your account and see an approximation of the activation completion time, go to [https://heliohost.org/status/ heliohost.org/status].

If after '''a full 2 hours''', you still see a message saying 'HelioHost Account Queued' or are still seeing the Plesk default page, please [[:Clear_Your_Cache|clear your cache]].

== Using a non-HelioHost domain ==

{{Info|
The more domains there are on the server the longer it takes to restart Apache.

In order to keep server uptime reasonably high, our automated process will disable domains that aren't hosted by us.
}}

=== HelioHost Nameservers ===

You will need to add the following nameservers to your domain via your domain registrar's website:

* ns1.heliohost.org
* ns2.heliohost.org

=== DNS Records ===

If you prefer to add A records (IPv4) or AAAA records (IPv6) to your custom domain registrar's dashboard instead of nameservers, look up the IP addresses for your server by using the steps below:

'''Login > Plesk > Websites & Domains > [domain name] > and check at the bottom of the page.'''

=== Checking Custom Domain DNS ===

Full DNS propagation can take up to 24 - 48 hours globally in some cases. To check that your DNS is properly configured, go to [https://dnschecker.org/ dnschecker.org]. Select the type of record you want to check (NS record, A record, or AAAA record), and type in your custom domain.

== "Account failed to be created" email message ==

Please create a new topic in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum] and make sure you provide your hosting account '''username''' so we can investigate this for you.

File:Johnny-tips countdown.png

2025-04-02T21:36:19Z

Krydos:

File:Johnny-tips exact-time.png

2025-04-02T21:32:40Z

Krydos:

File:Johnny-tips sync-time.png

2025-04-02T21:25:51Z

Krydos:

File:Johnny-tips time-is.png

2025-04-02T21:21:03Z

Krydos:

Refunds

2025-03-24T20:12:20Z

Krydos: /* Refund Policy */ add, some, commas,

== Refund Policy ==

At HelioHost we strive to provide the highest quality hosting service for all your website needs. We understand that not everyone will know exactly which plan they need upfront and also may not know how long they will need it. Our goal is 100% customer satisfaction, so we can offer exchanges and pro-rated partial refunds for most services or upgrades. However, since we are a small non-profit organization powered by donations, we can't afford to lose money on fees so every donation and payment has a non-refundable transaction fee.

* '''Exchanges''' - If you're dissatisfied with your plan or you realize you need a different type of plan, exchanges can be done with no transaction fees and the full value of the payment or the pro-rated remainder of the payment. For example, if you paid $19 for a Morty account, and then later realized you needed a VPS instead, we can put the pro-rated remainder toward the price of the VPS. Likewise, if you donate $5 to increase the storage space on your Johnny account, and then realize you'd rather move to Morty that can be done as well.
* '''Tommy donations''' - Requests to return the tax-deductible gift you gave to us must be received within 14 days from the date of the donation. We acknowledge that some people have difficulty grasping the difference between a donation and a payment so we honor refunds on donations, even though it is considered bad manners to ask for a gift to be returned. Tommy donations have a non-refundable transaction fee of $0.50. For example, if you donated $1, and then less than 14 days later decide you no longer want to support our mission as a non-profit, we can delete your account for you, and provide a refund of $0.50.
* '''Morty prepay payments''' - Refunds for Morty prepay payments will be given for the unused portion minus the initial discount and minus a non-refundable transaction fee of $0.50. For example, if you pay $5 for a Morty prepay balance of $6, and then decide to ask for a refund after using $1 worth of credit you will be refunded $3.50.
* '''VPS subscriptions''' - Refunds for VPS subscriptions will be given for the unused portion of the subscription, minus the initial discount, and minus a non-refundable transaction fee of $0.50. For example, if you pay $21.60 for a 6-month subscription of a Mercury VPS, and then decide to cancel it after the first month you will be refunded $17.10.

Refunds will not be issued for accounts that are banned for abuse. The prices listed in all of the examples above are in USD. Subscriptions cannot be scheduled for cancellation in the future. All provided services will be terminated immediately if refunded.

Discord Bot

2025-03-23T17:08:29Z

Krydos: Added section on automatically restarting the bot after a crash

== Preface ==

This guide will work on any of the HelioHost servers.

Python is an interpreted, object-oriented, high-level programming language with dynamic semantics. Its high-level built in data structures, combined with dynamic typing and dynamic binding, make it very attractive for Rapid Application Development, as well as for use as a scripting or glue language to connect existing components together. Python's simple, easy to learn syntax emphasizes readability and therefore reduces the cost of program maintenance. Python supports modules and packages, which encourages program modularity and code reuse.

The Discord app works with desktop and mobile platforms, combining the features of a chat lobby, a message board and a VoIP chatting system into one app that's not going to hog resources on your phone or PC. Discord's popularity has only multiplied in recent years, with the app now reaching over 90 million registered users.

Bots and apps are the lifeblood of the Discord development community. They come in all shapes and sizes, from small hobby projects for your server with friends, to huge projects that live in hundreds of thousands of servers. We love seeing the unique, fun, and sometimes downright strange (in a good way) creations that come from our community.

== How to get Started with a Discord Bot ==

First you'll need to have a Discord account, and a Discord channel that you'll add the bot to later. Here's a [https://www.howtogeek.com/364075/how-to-create-set-up-and-manage-your-discord-server/ good guide] to get started.

== Create the Bot ==

Once you have your Discord server all set up it's time to create the bot through Discord's site. Go to [https://discordapp.com/developers/applications discordapp.com/developers/applications] and make sure you're logged in. Then click 'New Application' in the top right.

[[File:New_application.png]]

Type a name and hit create. I decided to name my bot 'HelioBot'.

== Add the Bot to your Discord Server ==

Click 'OAuth2' on the left navigation.

[[File:oauth2.png]]

Then check the bot box under 'SCOPES', and scroll down and select 'Administrator' under 'BOT PERMISSIONS'. You could select the exact permissions that your bot needs one by one, but for this simple example it's easier to just allow the bot permission to do everything.

[[File:bot_admin.png]]

Click copy next to the URL that is generated and open that URL in a new tab. Then, select your Discord server from the dropdown menu.

[[File:add_to_server.png]]

Click 'Authorize' and complete the reCAPTCHA to add the bot to the Discord server. If you go to your Discord now you can see the bot on the offline user list.

[[File:offline_bot.png]]

== Write the Bot Script in Python ==

[https://heliohost.org/login Log in] and continue to Plesk. Then load up the file manager.

[[File:file_manager.png]]

In the top left corner click the '+' plus sign, and select 'Create File'.

[[File:plus_file.png]]

Then type the name of your new file: 'heliobot.py'.

[[File:create_heliobot.png]]

You want to create this bot in your home directory so random hackers and bots on the internet can't access it directly. Make sure it says 'Add a file to: /' not 'Add a file to: /httpdocs' or any other folder.

Scroll down in the file manager and click on the new 'heliobot.py' file to edit it. Then copy/paste this code in:

<pre>
#!/usr/bin/python3.12

import os
import discord
from dotenv import load_dotenv

load_dotenv()
token = os.getenv('DISCORD_TOKEN')

import certifi
os.environ["SSL_CERT_FILE"] = certifi.where()

client = discord.Client(intents=discord.Intents.default())

class MyClient(discord.Client):
async def on_ready(self):
print(f'Logged in as {self.user} (ID: {self.user.id})')
print('------')

async def on_message(self, message):
# we do not want the bot to reply to itself
if message.author.id == self.user.id:
return

if message.content.startswith('!hello'):
await message.reply('Hello!', mention_author=True)

intents = discord.Intents.default()
intents.message_content = True

client = MyClient(intents=intents)
client.run(token)
</pre>

The first line is called the shebang, and it tells the system which version of Python you want to use. Morty, Tommy, and Johnny also have Python 3.9, but we recommend using Python 3.12 like in the example.

Once you have your code copy/pasted in click save in the bottom left corner. Now we need the bot to be executable so in the file manager click the 'rw- r-- r--' on the heliobot.py line.

[[File:change_permissions.png]]

Check all three of the 'Execute/Search' boxes so it looks like this and then click save in the bottom left corner.

[[File:755_permissions.png]]

Now we need to provide our Discord token to the bot so click the '+' plus sign, and select 'Create File' again and this time name the file '.env'.

[[File:dot_env.png]]

'''Make sure you start the filename with a period.''' It's easy to miss that in the screenshot. This file needs to be in the '''same''' directory as your Python script.

Go back to the Discord bot page and click bot on the left navigation again.

[[File:select_bot.png]]

The first thing we need to do on this page is enable 'Presence Intent', 'Server Members Intent', and 'Message Content Intent'. If you're sure your bot doesn't need all three of these enable just what you need, but for simplicity of this guide we're going to enable all three, and then save the changes.

[[File:discord_intents.png]]

On the same page click the 'Reset Token' button, and then copy/paste the token.

[[File:copy_token.png]]

If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to come back to this page and reset it. Anyone who has your token can do whatever permissions you granted your bot to your server. Now you need to paste this token into your '.env' file that you created. So go back to the Plesk file manager and click the '.env' file to edit it. Paste the token into the file like this:

[[File:paste_the_token.png]]

Make sure the line starts with 'DISCORD_TOKEN=' like that. Then click 'Save Changes' and close the tab. Saving your token separate from your Python code is good practice because this way you can share the code on GitHub or something like that without worrying about people getting access to your bot.

== Starting and Stopping Your Bot ==

You have a functional bot now, but you need a way to start and stop it.

{{Info|
Side note: Previous versions of this guide used Python scripts to start and stop the Discord bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.
}}

We'll use Bash CGI to do that so you can control your bot through your web page. With the file manager, navigate to '/httpdocs' and create a new directory called 'bot_control'.

[[File:bot_control.png]]

Now create a new file named '.htaccess' in the '/httpdocs/bot_control' directory.

[[File:create_htaccess.png]]

Paste this code into the new '.htaccess' file.

<pre>
Options +ExecCGI
AddHandler cgi-script .sh
DirectoryIndex index.sh
</pre>

Next create a new file named 'index.sh' in the '/httpdocs/bot_control' directory.

[[File:create_indexsh.png]]

Paste the code below into the new file. Remember to use either 'helio'''ho.st'''' or 'helioho'''st.us'''' at the end of your domain, unless you're one of the very few users who still have a legacy heliohost.org domain:

<pre>
#!/bin/bash

# edit this to match your bot filename
bot_name="heliobot.py"

###################################################################

printf 'Content-Type: text/html\n\n'
username=`whoami`
pwd=`printenv|grep '^PWD'|cut -f2 -d'='`
main_domain=`echo "$pwd"|cut -f3 -d'/'`
control=`echo "$pwd"|cut -f5 -d'/'`
temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command|grep -v grep|grep "^$username "`
running=`echo "$temp"|grep -c "$bot_name"`
file_base=`echo $bot_name|tr -cd "a-zA-Z0-9"`
log_name="$file_base.txt"
if [ "$QUERY_STRING" == "" ]; then
if [ $running -ne 0 ]; then
mem_kb=`echo "$temp"|grep "$bot_name"|awk '{print $6}'`
mem_mb=$( echo "scale=2;$mem_kb/1024"|bc )
mem_24=$( echo "scale=2;$mem_kb*1440/1048576"|bc )
echo "$bot_name is running. <a href='?action=stop'>Stop</a><br>Current memory usage: $mem_mb MB<br>Estimated 24 hour usage: $mem_24 GB - "
else
echo "$bot_name is not running. <a href='?action=start'>Start</a> - "
fi
echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/$control/$log_name'>Full Logs</a><pre>"
tail -30 $pwd/$log_name
echo "</pre><script>reloading = setTimeout('window.location.reload();', 10000);</script>"
fi
ts=`date +"%Y-%m-%d %H:%M:%S"`
if [ "$QUERY_STRING" == "action=stop" ]; then
echo "[$ts] Stopping $bot_name." >> $pwd/$log_name
pid=`echo "$temp"|grep "$bot_name"|tail -1|awk '{print $2}'`
if [ ${#pid} -ne 0 ]; then
kill $pid
fi
echo "Stopping $bot_name...<script>setInterval(\"window.location.replace('/$control/');\", 2000);</script>"
fi
if [ "$QUERY_STRING" == "action=start" ]; then
if [ $running -ne 0 ]; then
echo "$bot_name is already running..."
else
echo "[$ts] Starting $bot_name." >> $pwd/$log_name
/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> $pwd/$log_name 2>&1 &
echo "Starting $bot_name...<script>window.location.replace('/$control/');</script>"
fi
fi
if [ "$QUERY_STRING" == "action=clear" ]; then
cat /dev/null > $pwd/$log_name
echo "Clearing logs...<script>window.location.replace('/$control/');</script>"
fi
exit 0
</pre>

Be sure to edit the variable at the top of the file to match your bot filename.

Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliobot.py file earlier.

[[File:755_permissions.png]]

== Test It Out ==

Now everything should be ready to be tested. Open your browser and go to 'yourdomain.helioho.st/bot_control/' and when you click Start it should start the bot. You can check if the bot is running by going to Discord and seeing if HelioBot is showing up as online now. If it is, test it out by typing the command:

<pre>
!hello
</pre>

It should respond to you.

[[File:testing_discord_bot.png]]

If it doesn't work go back and check all the steps again to make sure you did everything correctly. You can also check out the logs in the bot_control dashboard to see if there is any errors listed. For example, if you try to import a modules that isn't already installed it will give an error like this:

[[File:bot_error.png]]

If you can't figure out what is wrong let us know by opening [https://helionet.org/index/forum/45-customer-service/?do=add a customer service ticket].

== Watch Your Account Load ==

{{Caution|Bots use a lot of system resources so we recommend [https://heliohost.org/dashboard/load/ keeping an eye on your account load].}}

We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.
* On the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, if you exceed these limits, your account will be suspended.
* On the [[:Morty|Morty]] server, if you exceed these limits, we will charge you for overages.

On the bot_control dashboard it shows the current memory usage, and the estimated usage over the next 24 hours if your bot continues using the same amount of memory.

[[File:bot_dashboard.png]]

If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].

If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

== Automatically Restarting the Bot ==

We've had a lot of people ask us if we intentionally stop their bots after 60 minutes or so. The answer is no. The only time we kill processes automatically is if your account got suspended for high load. In our testing the bots can run for weeks or longer without needing to be restarted. Our servers are stable enough to run for months or years without a reboot as well. The issue is undoubtedly that people write bad code that crashes, but rather than admitting that their code is buggy, it's easier to just blame us.

If your bot keeps stopping on its own, the best solution is to check the logs and fix the issue. If there is nothing shown in the logs that means you need to add more logging to your code to figure out why it's crashing. If you still can't figure it out you could enable auto-restart, but it's really just a crutch for buggy code rather than a real fix. If your bot code really is stable enough to run for weeks or months without crashing, auto-restart can also benefit you in the rare case of us rebooting the whole server, your bot will automatically start up as soon as the reboot is finished.

{{Caution|
Enabling auto-restart could increase your chance of getting suspended. If you don't currently need your bot online we recommend shutting it down entirely rather than leaving it restarting over and over.
}}

To set up auto-restart login to Plesk and navigate to:

'''Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks'''

[[File:plesk-scheduled-tasks.png]]

Next, click 'Add Task' and select the 'Fetch a URL' option.

[[File:Plesk-schedule-a-task.png]]

In the URL box put the start link from your bot_control page if you would click 'Start'. The easiest way to get this value is to stop your bot, and then right click on the 'Start' link, and 'Copy link address'.

[[File:Telegram-start-link.png]]

If you followed this guide without changing too much it should be something like 'yourdomain.helioho.st/bot_control/?action=start'.

[[File:Telegram-cron-job.png]]

For those of you who want to minimize the downtime, and maximize your suspension chance you can set the schedule task up to run every minute like this with Cron Style and '* * * * *'. If everything is working correctly it will check if the bot is up every minute. Then if the bot is stopped it will restart it, and if the bot is already running it won't do anything.

{{Danger|
Running a scheduled task every minute increases your load by quite a bit even if your bot never needs to be restarted. Simply checking if it has crashed causes some load. Worst case scenario: this scheduled tasks starts a new bot process every minute even though you already have a copy of the bot running, and you get suspended on [[:Tommy|Tommy]] or [[:Johnny|Johnny]] in record time, or reach the maximum billing on [[:Morty|Morty]] faster than anyone has ever dreamed possible.
}}

[[Category:Tutorials]]

Discord Bot

2025-03-23T17:02:47Z

Krydos: /* Starting and Stopping Your Bot */ Updated the bot_control script

Mail Delivery Problems

2025-03-17T17:41:48Z

Krydos: /* Send a Test Email */ .top is abused TLD as well

== Mail Delivery Problems ==

HelioHost offers [[:Unlimited_Email_Accounts|unlimited email accounts]] to our users. Below is a troubleshooting guide to help resolve issues with email delivery.

== Emails Not Delivered ==

If you get a mail delivery report that says your email could not be delivered, the report should explain why.

If the report says: 'Your email has been blocked because the sender is unauthenticated. [Email provider] requires all senders to authenticate with either SPF or DKIM', we can help you set up these records.

== Emails Going to Spam Folder ==

If your email recipients say that your emails are going to their spam folder, setting up SPF, DKIM, and DMARC records will help improve email delivery.

== SPF, DKIM, and DMARC Records ==

== Set Up SPF, DKIM, and DMARC Records ==

To help improve the delivery of your emails, you can request that SPF, DKIM, and DMARC records be added to your account. Please create a new topic in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum] and include your hosting account '''username''' and '''domain name''' so we can set this up for you.

== Send a Test Email ==

After the SPF, DKIM, and DMARC records are set up, we recommend sending a test email to [https://www.mail-tester.com/ mail-tester.com] to check that everything is set up correctly. Your test email should be a regular email, such as your typical newsletter or a standard message (avoid using just "test" as the email content). If your score is below 10/10, please create a new topic in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and include '''the full mail-tester report link''', your hosting account '''username''', and your '''domain name''' so we can help you fix any remaining issues.

{{Info|For sites with the '''.xyz''' or '''.top''' TLD (Top-Level Domain), it is impossible to get a 10/10 mail-tester result. Since the domain is primarily associated with spam and abuse, most providers have added it to blocklists. The only solution is to purchase a domain with a more reputable TLD, such as .com or .net.}}

== Further Support ==

If you get a different error in the mail delivery report, or if your emails are not delivered and you don't know why, please make a new post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', and details about the problem, including '''the full mail-tester report link''' and any '''error message(s)''' received.

Discord Bot

2025-03-16T02:41:12Z

Krydos: /* Starting and Stopping Your Bot */ Changed caution box into info box

== Preface ==

This guide will work on any of the HelioHost servers.

Python is an interpreted, object-oriented, high-level programming language with dynamic semantics. Its high-level built in data structures, combined with dynamic typing and dynamic binding, make it very attractive for Rapid Application Development, as well as for use as a scripting or glue language to connect existing components together. Python's simple, easy to learn syntax emphasizes readability and therefore reduces the cost of program maintenance. Python supports modules and packages, which encourages program modularity and code reuse.

The Discord app works with desktop and mobile platforms, combining the features of a chat lobby, a message board and a VoIP chatting system into one app that's not going to hog resources on your phone or PC. Discord's popularity has only multiplied in recent years, with the app now reaching over 90 million registered users.

Bots and apps are the lifeblood of the Discord development community. They come in all shapes and sizes, from small hobby projects for your server with friends, to huge projects that live in hundreds of thousands of servers. We love seeing the unique, fun, and sometimes downright strange (in a good way) creations that come from our community.

== How to get Started with a Discord Bot ==

First you'll need to have a Discord account, and a Discord channel that you'll add the bot to later. Here's a [https://www.howtogeek.com/364075/how-to-create-set-up-and-manage-your-discord-server/ good guide] to get started.

== Create the Bot ==

Once you have your Discord server all set up it's time to create the bot through Discord's site. Go to [https://discordapp.com/developers/applications discordapp.com/developers/applications] and make sure you're logged in. Then click 'New Application' in the top right.

[[File:New_application.png]]

Type a name and hit create. I decided to name my bot 'HelioBot'.

== Add the Bot to your Discord Server ==

Click 'OAuth2' on the left navigation.

[[File:oauth2.png]]

Then check the bot box under 'SCOPES', and scroll down and select 'Administrator' under 'BOT PERMISSIONS'. You could select the exact permissions that your bot needs one by one, but for this simple example it's easier to just allow the bot permission to do everything.

[[File:bot_admin.png]]

Click copy next to the URL that is generated and open that URL in a new tab. Then, select your Discord server from the dropdown menu.

[[File:add_to_server.png]]

Click 'Authorize' and complete the reCAPTCHA to add the bot to the Discord server. If you go to your Discord now you can see the bot on the offline user list.

[[File:offline_bot.png]]

== Write the Bot Script in Python ==

[https://heliohost.org/login Log in] and continue to Plesk. Then load up the file manager.

[[File:file_manager.png]]

In the top left corner click the '+' plus sign, and select 'Create File'.

[[File:plus_file.png]]

Then type the name of your new file: 'heliobot.py'.

[[File:create_heliobot.png]]

You want to create this bot in your home directory so random hackers and bots on the internet can't access it directly. Make sure it says 'Add a file to: /' not 'Add a file to: /httpdocs' or any other folder.

Scroll down in the file manager and click on the new 'heliobot.py' file to edit it. Then copy/paste this code in:

<pre>
#!/usr/bin/python3.12

import os
import discord
from dotenv import load_dotenv

load_dotenv()
token = os.getenv('DISCORD_TOKEN')

import certifi
os.environ["SSL_CERT_FILE"] = certifi.where()

client = discord.Client(intents=discord.Intents.default())

class MyClient(discord.Client):
async def on_ready(self):
print(f'Logged in as {self.user} (ID: {self.user.id})')
print('------')

async def on_message(self, message):
# we do not want the bot to reply to itself
if message.author.id == self.user.id:
return

if message.content.startswith('!hello'):
await message.reply('Hello!', mention_author=True)

intents = discord.Intents.default()
intents.message_content = True

client = MyClient(intents=intents)
client.run(token)
</pre>

The first line is called the shebang, and it tells the system which version of Python you want to use. Morty, Tommy, and Johnny also have Python 3.9, but we recommend using Python 3.12 like in the example.

Once you have your code copy/pasted in click save in the bottom left corner. Now we need the bot to be executable so in the file manager click the 'rw- r-- r--' on the heliobot.py line.

[[File:change_permissions.png]]

Check all three of the 'Execute/Search' boxes so it looks like this and then click save in the bottom left corner.

[[File:755_permissions.png]]

Now we need to provide our Discord token to the bot so click the '+' plus sign, and select 'Create File' again and this time name the file '.env'.

[[File:dot_env.png]]

'''Make sure you start the filename with a period.''' It's easy to miss that in the screenshot. This file needs to be in the '''same''' directory as your Python script.

Go back to the Discord bot page and click bot on the left navigation again.

[[File:select_bot.png]]

The first thing we need to do on this page is enable 'Presence Intent', 'Server Members Intent', and 'Message Content Intent'. If you're sure your bot doesn't need all three of these enable just what you need, but for simplicity of this guide we're going to enable all three, and then save the changes.

[[File:discord_intents.png]]

On the same page click the 'Reset Token' button, and then copy/paste the token.

[[File:copy_token.png]]

If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to come back to this page and reset it. Anyone who has your token can do whatever permissions you granted your bot to your server. Now you need to paste this token into your '.env' file that you created. So go back to the Plesk file manager and click the '.env' file to edit it. Paste the token into the file like this:

[[File:paste_the_token.png]]

Make sure the line starts with 'DISCORD_TOKEN=' like that. Then click 'Save Changes' and close the tab. Saving your token separate from your Python code is good practice because this way you can share the code on GitHub or something like that without worrying about people getting access to your bot.

== Starting and Stopping Your Bot ==

You have a functional bot now, but you need a way to start and stop it.

{{Info|
Side note: Previous versions of this guide used Python scripts to start and stop the Discord bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.
}}

We'll use Bash CGI to do that so you can control your bot through your web page. With the file manager, navigate to '/httpdocs' and create a new directory called 'bot_control'.

[[File:bot_control.png]]

Now create a new file named '.htaccess' in the '/httpdocs/bot_control' directory.

[[File:create_htaccess.png]]

Paste this code into the new '.htaccess' file.

<pre>
Options +ExecCGI
AddHandler cgi-script .sh
DirectoryIndex index.sh
</pre>

Next create a new file named 'index.sh' in the '/httpdocs/bot_control' directory.

[[File:create_indexsh.png]]

Paste the code below into the new file. Remember to use either 'helio'''ho.st'''' or 'helioho'''st.us'''' at the end of your domain, unless you're one of the very few users who still have a legacy heliohost.org domain:

<pre>
#!/bin/bash

# edit these to match your username, main domain, and bot filename
username="krydos"
main_domain="krydos.heliohost.org"
bot_name="heliobot.py"

###################################################################

printf 'Content-Type: text/html\n\n'
temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command|grep -v grep|grep "^$username"`
running=`echo "$temp"|grep -c "$bot_name"`
file_base=`echo $bot_name|tr -cd "a-zA-Z0-9"`
log_name="$file_base.txt"
if [ "$QUERY_STRING" == "" ]; then
if [ $running -ne 0 ]; then
mem_kb=`echo "$temp"|grep "$bot_name"|awk '{print $6}'`
mem_mb=$( echo "scale=2;$mem_kb/1024"|bc )
mem_24=$( echo "scale=2;$mem_kb*1440/1048576"|bc )
echo "$bot_name is running. <a href='?action=stop'>Stop</a><br>Current memory usage: $mem_mb MB<br>Estimated 24 hour usage: $mem_24 GB - "
else
echo "$bot_name is not running. <a href='?action=start'>Start</a> - "
fi
echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/bot_control/$log_name'>Full Logs</a><pre>"
tail -30 /home/$main_domain/httpdocs/bot_control/$log_name
echo "</pre><script>reloading = setTimeout('window.location.reload();', 10000);</script>"
fi
ts=`date +"%Y-%m-%d %H:%M:%S"`
if [ "$QUERY_STRING" == "action=stop" ]; then
echo "[$ts] Stopping $bot_name." >> /home/$main_domain/httpdocs/bot_control/$log_name
pid=`echo "$temp"|grep "$bot_name"|tail -1|awk '{print $2}'`
if [ ${#pid} -ne 0 ]; then
kill $pid
fi
echo "Stopping $bot_name...<script>window.location.replace('/bot_control/');</script>"
fi
if [ "$QUERY_STRING" == "action=start" ]; then
if [ $running -ne 0 ]; then
echo "$bot_name is already running..."
else
echo "[$ts] Starting $bot_name." >> /home/$main_domain/httpdocs/bot_control/$log_name
/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> /home/$main_domain/httpdocs/bot_control/$log_name 2>&1 &
echo "Starting $bot_name...<script>window.location.replace('/bot_control/');</script>"
fi
fi
if [ "$QUERY_STRING" == "action=clear" ]; then
cat /dev/null > /home/$main_domain/httpdocs/bot_control/$log_name
echo "Clearing logs...<script>window.location.replace('/bot_control/');</script>"
fi
exit 0
</pre>

Be sure to edit the three variables at the top of the file to match your username, main domain, and bot filename.

Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliobot.py file earlier.

[[File:755_permissions.png]]

== Test It Out ==

Now everything should be ready to be tested. Open your browser and go to 'yourdomain.helioho.st/bot_control/' and when you click Start it should start the bot. You can check if the bot is running by going to Discord and seeing if HelioBot is showing up as online now. If it is, test it out by typing the command:

<pre>
!hello
</pre>

It should respond to you.

[[File:testing_discord_bot.png]]

If it doesn't work go back and check all the steps again to make sure you did everything correctly. You can also check out the logs in the bot_control dashboard to see if there is any errors listed. For example, if you try to import a modules that isn't already installed it will give an error like this:

[[File:bot_error.png]]

If you can't figure out what is wrong let us know by opening [https://helionet.org/index/forum/45-customer-service/?do=add a customer service ticket].

== Watch Your Account Load ==

{{Caution|Bots use a lot of system resources so we recommend [https://heliohost.org/dashboard/load/ keeping an eye on your account load].}}

We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.
* On the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, if you exceed these limits, your account will be suspended.
* On the [[:Morty|Morty]] server, if you exceed these limits, we will charge you for overages.

On the bot_control dashboard it shows the current memory usage, and the estimated usage over the next 24 hours if your bot continues using the same amount of memory.

[[File:bot_dashboard.png]]

If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].

If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

[[Category:Tutorials]]

Telegram Bot

2025-03-16T02:40:27Z

Krydos: /* Starting and Stopping Your Bot */ Changed caution box to info

== Preface ==

This guide will work on any of the HelioHost servers.

Python is an interpreted, object-oriented, high-level programming language with dynamic semantics. Its high-level built in data structures, combined with dynamic typing and dynamic binding, make it very attractive for Rapid Application Development, as well as for use as a scripting or glue language to connect existing components together. Python's simple, easy to learn syntax emphasizes readability and therefore reduces the cost of program maintenance. Python supports modules and packages, which encourages program modularity and code reuse.

Telegram, also known as Telegram Messenger, is a cloud-based, cross-platform, social media and instant messaging (IM) service. It was originally launched for iOS on 14 August 2013 and Android on 20 October 2013. It allows users to exchange messages, share media and files, and hold private and group voice or video calls as well as public livestreams. It is available for Android, iOS, Windows, macOS, Linux, and web browsers. Telegram offers end-to-end encryption in voice and video calls, and in optional private chats, which Telegram calls Secret Chats.

In June 2015, Telegram launched a platform for third-party developers to create bots. Bots are Telegram accounts operated by programs. They can respond to messages or mentions directly or can be invited into groups, and are able to perform tasks, integrate with other programs and host mini apps.

== How to get Started with a Telegram Bot ==

The first step is to download the Telegram app and create an account, if you haven't done so already. Once you have an account you can search Telegram for the @BotFather. There are many people pretending to be the BotFather, likely to scam you, but make sure you click the one that actually says @BotFather.

[[File:Telegram-bot-father.png]]

His profile page also has some useful links such as [https://core.telegram.org/bots core.telegram.org/bots] and [https://core.telegram.org/bots/api core.telegram.org/bots/api]. Next click the start button at the bottom of the page.

[[File:Telegram-click-start.png]]

A whole bunch of slash commands come up, but they're all useless until we run the first command he listed: /newbot

[[File:Telegram-new-bot.png]]

He'll ask you for a name for your bot. I picked HelioBot.

[[File:Telegram-bot-name.png]]

He'll also ask you for a username for your bot, and then give you the API token. Be sure to keep your token safe, and don't do anything dumb like uploading it to a wiki because then anyone who reads the wiki will have full control over your bot.

[[File:Telegram-bot-api-token.png]]

== Write the Bot Script in Python ==

Great! You have a bot now, and you have an API token, but it doesn't do anything without some code to run it. Let's fix that! [https://heliohost.org/login/ Login to your HelioHost account], continue to Plesk, and load up the file manager.

[[File:File_manager.png]]

In the top left corner click the '+' plus sign, and select 'Create File'.

[[File:Plus_file.png]]

Then type the name of your new file: 'heliotelebot.py'.

[[File:Telegram-heliotelebot.png]]

You want to create this bot in your home directory so random hackers and bots on the internet can't access it directly. Make sure it says 'Add a file to: /' not 'Add a file to: /httpdocs' or any other folder.

Scroll down in the file manager and click on the new 'heliotelebot.py' file to edit it. Then copy/paste this code in:

<pre>
#!/usr/bin/python3.12

import os
from datetime import datetime, UTC
from dotenv import load_dotenv
load_dotenv()
TOKEN = os.getenv('TELEGRAM_TOKEN')

from telegram import Update
from telegram.ext import ApplicationBuilder, CommandHandler, ContextTypes

async def hello(update: Update, context: ContextTypes.DEFAULT_TYPE) -> None:
ts = datetime.now(UTC).strftime('%Y-%m-%d %H:%M:%S')
print(f"[{ts}] Saying hello to {update.effective_user.first_name}.")
await update.message.reply_text(f"Hello {update.effective_user.first_name}, you have created a Telegram bot on HelioHost!")

app = ApplicationBuilder().token(TOKEN).build()
app.add_handler(CommandHandler("hello", hello))
app.run_polling()
</pre>

The first line is called the shebang, and it tells the system which version of Python you want to use. Morty, Tommy, and Johnny also have Python 3.9, but we recommend using Python 3.12 like in the example.

Once you have your code copy/pasted in click save in the bottom left corner. Now we need the bot to be executable so in the file manager click the 'rw- r-- r--' on the heliotelebot.py line.

[[File:Telegram-644-permissions.png]]

Check all three of the 'Execute/Search' boxes so it looks like this and then click save in the bottom left corner.

[[File:755_permissions.png]]

Now we need to provide our Telegram token to the bot so click the '+' plus sign, and select 'Create File' again and this time name the file '.env'.

[[File:Dot_env.png]]

'''Make sure you start the filename with a period.''' It's easy to miss that in the screenshot. This file needs to be in the '''same''' directory as your Python script.

If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to talk to the BotFather and use the /token command to reset it. Anyone who has your token has full access to control your bot. Now you need to paste this token into your '.env' file that you created. So go back to the Plesk file manager and click the '.env' file to edit it. Paste the token into the file like this:

[[File:Telegram-telegram-token.png]]

Make sure the line starts with 'TELEGRAM_TOKEN=' as shown. Then click 'Save Changes' and close the tab. Saving your token separate from your Python code is good practice because this way you can share the code on GitHub or something like that without worrying about people getting access to your bot.

== Starting and Stopping Your Bot ==

You have a functional bot now, but you need a way to start and stop it.

{{Info|
Side note: Previous versions of this guide used Python scripts to start and stop the Telegram bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.
}}

We'll use Bash CGI to do that so you can control your bot through your web page. With the file manager, navigate to '/httpdocs' and create a new directory called 'bot_control'.

[[File:Bot_control.png]]

Now create a new file named '.htaccess' in the '/httpdocs/bot_control' directory.

[[File:Create_htaccess.png]]

Paste this code into the new '.htaccess' file.

<pre>
Options +ExecCGI
AddHandler cgi-script .sh
DirectoryIndex index.sh
</pre>

Next create a new file named 'index.sh' in the '/httpdocs/bot_control' directory.

[[File:Create_indexsh.png]]

Paste the code below into the new index.sh file. Remember to update the bot filename if you're not using heliotelebot.py like this guide says:

<pre>
#!/bin/bash

# edit this to match your bot filename
bot_name="heliotelebot.py"

###################################################################

printf 'Content-Type: text/html\n\n'
username=`whoami`
pwd=`printenv|grep '^PWD'|cut -f2 -d'='`
main_domain=`echo "$pwd"|cut -f3 -d'/'`
control=`echo "$pwd"|cut -f5 -d'/'`
temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command|grep -v grep|grep "^$username "`
running=`echo "$temp"|grep -c "$bot_name"`
file_base=`echo $bot_name|tr -cd "a-zA-Z0-9"`
log_name="$file_base.txt"
if [ "$QUERY_STRING" == "" ]; then
if [ $running -ne 0 ]; then
mem_kb=`echo "$temp"|grep "$bot_name"|awk '{print $6}'`
mem_mb=$( echo "scale=2;$mem_kb/1024"|bc )
mem_24=$( echo "scale=2;$mem_kb*1440/1048576"|bc )
echo "$bot_name is running. <a href='?action=stop'>Stop</a><br>Current memory usage: $mem_mb MB<br>Estimated 24 hour usage: $mem_24 GB - "
else
echo "$bot_name is not running. <a href='?action=start'>Start</a> - "
fi
echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/$control/$log_name'>Full Logs</a><pre>"
tail -30 $pwd/$log_name
echo "</pre><script>reloading = setTimeout('window.location.reload();', 10000);</script>"
fi
ts=`date +"%Y-%m-%d %H:%M:%S"`
if [ "$QUERY_STRING" == "action=stop" ]; then
echo "[$ts] Stopping $bot_name." >> $pwd/$log_name
pid=`echo "$temp"|grep "$bot_name"|tail -1|awk '{print $2}'`
if [ ${#pid} -ne 0 ]; then
kill $pid
fi
echo "Stopping $bot_name...<script>setInterval(\"window.location.replace('/$control/');\", 2000);</script>"
fi
if [ "$QUERY_STRING" == "action=start" ]; then
if [ $running -ne 0 ]; then
echo "$bot_name is already running..."
else
echo "[$ts] Starting $bot_name." >> $pwd/$log_name
/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> $pwd/$log_name 2>&1 &
echo "Starting $bot_name...<script>window.location.replace('/$control/');</script>"
fi
fi
if [ "$QUERY_STRING" == "action=clear" ]; then
cat /dev/null > $pwd/$log_name
echo "Clearing logs...<script>window.location.replace('/$control/');</script>"
fi
exit 0
</pre>

Be sure to edit the variable at the top of the file to match your bot filename.

Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliotelebot.py file earlier.

[[File:755_permissions.png]]

== Test It Out ==

Now everything should be ready to be tested. Open your browser and go to yourdomain.helioho.st/bot_control/ and when you click Start it should start the bot. You can check if the bot is running by going to t.me/YourBotName on Telegram. If everything is working you should be able to type /hello and it will reply to you.

[[File:Telegram-hello.png]]

If it doesn't work go back and check all the steps again to make sure you did everything correctly. You can also check out the logs in the bot_control dashboard to see if there is any errors listed. For example, if you try to import a modules that isn't already installed it will give an error like this:

[[File:Bot_error.png]]

If you can't figure out what is wrong let us know by opening [https://helionet.org/index/forum/45-customer-service/?do=add a customer service ticket].

== Watch Your Account Load ==

{{Caution|Bots use a lot of system resources so we recommend [https://heliohost.org/dashboard/load/ keeping an eye on your account load].}}

We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.
* On the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, if you exceed these limits, your account will be suspended.
* On the [[:Morty|Morty]] server, if you exceed these limits, we will charge you for overages.

On the bot_control dashboard it shows the current memory usage, and the estimated usage over the next 24 hours if your bot continues using the same amount of memory.

[[File:Telegram-bot-dashboard.png]]

If you followed the guide exactly your bot will use about 60 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].

If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

== Automatically Restarting the Bot ==

We've had a lot of people ask us if we intentionally stop their bots after 60 minutes or so. The answer is no. The only time we kill processes automatically is if your account got suspended for high load. In our testing the bots can run for weeks or longer without needing to be restarted. Our servers are stable enough to run for months or years without a reboot as well. The issue is undoubtedly that people write bad code that crashes, but rather than admitting that their code is buggy, it's easier to just blame us.

If your bot keeps stopping on its own, the best solution is to check the logs and fix the issue. If there is nothing shown in the logs that means you need to add more logging to your code to figure out why it's crashing. If you still can't figure it out you could enable auto-restart, but it's really just a crutch for buggy code rather than a real fix. If your bot code really is stable enough to run for weeks or months without crashing, auto-restart can also benefit you in the rare case of us rebooting the whole server, your bot will automatically start up as soon as the reboot is finished.

{{Caution|
Enabling auto-restart could increase your chance of getting suspended. If you don't currently need your bot online we recommend shutting it down entirely rather than leaving it restarting over and over.
}}

To set up auto-restart login to Plesk and navigate to:

'''Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks'''

[[File:plesk-scheduled-tasks.png]]

Next, click 'Add Task' and select the 'Fetch a URL' option.

[[File:Plesk-schedule-a-task.png]]

In the URL box put the start link from your bot_control page if you would click 'Start'. The easiest way to get this value is to stop your bot, and then right click on the 'Start' link, and 'Copy link address'.

[[File:Telegram-start-link.png]]

If you followed this guide without changing too much it should be something like 'yourdomain.helioho.st/bot_control/?action=start'.

[[File:Telegram-cron-job.png]]

For those of you who want to minimize the downtime, and maximize your suspension chance you can set the schedule task up to run every minute like this with Cron Style and '* * * * *'. If everything is working correctly it will check if the bot is up every minute. Then if the bot is stopped it will restart it, and if the bot is already running it won't do anything.

{{Danger|
Running a scheduled task every minute increases your load by quite a bit even if your bot never needs to be restarted. Simply checking if it has crashed causes some load. Worst case scenario: this scheduled tasks starts a new bot process every minute even though you already have a copy of the bot running, and you get suspended on [[:Tommy|Tommy]] or [[:Johnny|Johnny]] in record time, or reach the maximum billing on [[:Morty|Morty]] faster than anyone has ever dreamed possible.
}}

[[Category:Tutorials]]

Telegram Bot

2025-03-16T02:39:23Z

Krydos: Initial publication

== Preface ==

This guide will work on any of the HelioHost servers.

Python is an interpreted, object-oriented, high-level programming language with dynamic semantics. Its high-level built in data structures, combined with dynamic typing and dynamic binding, make it very attractive for Rapid Application Development, as well as for use as a scripting or glue language to connect existing components together. Python's simple, easy to learn syntax emphasizes readability and therefore reduces the cost of program maintenance. Python supports modules and packages, which encourages program modularity and code reuse.

Telegram, also known as Telegram Messenger, is a cloud-based, cross-platform, social media and instant messaging (IM) service. It was originally launched for iOS on 14 August 2013 and Android on 20 October 2013. It allows users to exchange messages, share media and files, and hold private and group voice or video calls as well as public livestreams. It is available for Android, iOS, Windows, macOS, Linux, and web browsers. Telegram offers end-to-end encryption in voice and video calls, and in optional private chats, which Telegram calls Secret Chats.

In June 2015, Telegram launched a platform for third-party developers to create bots. Bots are Telegram accounts operated by programs. They can respond to messages or mentions directly or can be invited into groups, and are able to perform tasks, integrate with other programs and host mini apps.

== How to get Started with a Telegram Bot ==

The first step is to download the Telegram app and create an account, if you haven't done so already. Once you have an account you can search Telegram for the @BotFather. There are many people pretending to be the BotFather, likely to scam you, but make sure you click the one that actually says @BotFather.

[[File:Telegram-bot-father.png]]

His profile page also has some useful links such as [https://core.telegram.org/bots core.telegram.org/bots] and [https://core.telegram.org/bots/api core.telegram.org/bots/api]. Next click the start button at the bottom of the page.

[[File:Telegram-click-start.png]]

A whole bunch of slash commands come up, but they're all useless until we run the first command he listed: /newbot

[[File:Telegram-new-bot.png]]

He'll ask you for a name for your bot. I picked HelioBot.

[[File:Telegram-bot-name.png]]

He'll also ask you for a username for your bot, and then give you the API token. Be sure to keep your token safe, and don't do anything dumb like uploading it to a wiki because then anyone who reads the wiki will have full control over your bot.

[[File:Telegram-bot-api-token.png]]

== Write the Bot Script in Python ==

Great! You have a bot now, and you have an API token, but it doesn't do anything without some code to run it. Let's fix that! [https://heliohost.org/login/ Login to your HelioHost account], continue to Plesk, and load up the file manager.

[[File:File_manager.png]]

In the top left corner click the '+' plus sign, and select 'Create File'.

[[File:Plus_file.png]]

Then type the name of your new file: 'heliotelebot.py'.

[[File:Telegram-heliotelebot.png]]

You want to create this bot in your home directory so random hackers and bots on the internet can't access it directly. Make sure it says 'Add a file to: /' not 'Add a file to: /httpdocs' or any other folder.

Scroll down in the file manager and click on the new 'heliotelebot.py' file to edit it. Then copy/paste this code in:

<pre>
#!/usr/bin/python3.12

import os
from datetime import datetime, UTC
from dotenv import load_dotenv
load_dotenv()
TOKEN = os.getenv('TELEGRAM_TOKEN')

from telegram import Update
from telegram.ext import ApplicationBuilder, CommandHandler, ContextTypes

async def hello(update: Update, context: ContextTypes.DEFAULT_TYPE) -> None:
ts = datetime.now(UTC).strftime('%Y-%m-%d %H:%M:%S')
print(f"[{ts}] Saying hello to {update.effective_user.first_name}.")
await update.message.reply_text(f"Hello {update.effective_user.first_name}, you have created a Telegram bot on HelioHost!")

app = ApplicationBuilder().token(TOKEN).build()
app.add_handler(CommandHandler("hello", hello))
app.run_polling()
</pre>

The first line is called the shebang, and it tells the system which version of Python you want to use. Morty, Tommy, and Johnny also have Python 3.9, but we recommend using Python 3.12 like in the example.

Once you have your code copy/pasted in click save in the bottom left corner. Now we need the bot to be executable so in the file manager click the 'rw- r-- r--' on the heliotelebot.py line.

[[File:Telegram-644-permissions.png]]

Check all three of the 'Execute/Search' boxes so it looks like this and then click save in the bottom left corner.

[[File:755_permissions.png]]

Now we need to provide our Telegram token to the bot so click the '+' plus sign, and select 'Create File' again and this time name the file '.env'.

[[File:Dot_env.png]]

'''Make sure you start the filename with a period.''' It's easy to miss that in the screenshot. This file needs to be in the '''same''' directory as your Python script.

If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to talk to the BotFather and use the /token command to reset it. Anyone who has your token has full access to control your bot. Now you need to paste this token into your '.env' file that you created. So go back to the Plesk file manager and click the '.env' file to edit it. Paste the token into the file like this:

[[File:Telegram-telegram-token.png]]

Make sure the line starts with 'TELEGRAM_TOKEN=' as shown. Then click 'Save Changes' and close the tab. Saving your token separate from your Python code is good practice because this way you can share the code on GitHub or something like that without worrying about people getting access to your bot.

== Starting and Stopping Your Bot ==

You have a functional bot now, but you need a way to start and stop it.

{{Caution|
Side note: Previous versions of this guide used Python scripts to start and stop the Telegram bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.
}}

We'll use Bash CGI to do that so you can control your bot through your web page. With the file manager, navigate to '/httpdocs' and create a new directory called 'bot_control'.

[[File:Bot_control.png]]

Now create a new file named '.htaccess' in the '/httpdocs/bot_control' directory.

[[File:Create_htaccess.png]]

Paste this code into the new '.htaccess' file.

<pre>
Options +ExecCGI
AddHandler cgi-script .sh
DirectoryIndex index.sh
</pre>

Next create a new file named 'index.sh' in the '/httpdocs/bot_control' directory.

[[File:Create_indexsh.png]]

Paste the code below into the new index.sh file. Remember to update the bot filename if you're not using heliotelebot.py like this guide says:

<pre>
#!/bin/bash

# edit this to match your bot filename
bot_name="heliotelebot.py"

###################################################################

printf 'Content-Type: text/html\n\n'
username=`whoami`
pwd=`printenv|grep '^PWD'|cut -f2 -d'='`
main_domain=`echo "$pwd"|cut -f3 -d'/'`
control=`echo "$pwd"|cut -f5 -d'/'`
temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command|grep -v grep|grep "^$username "`
running=`echo "$temp"|grep -c "$bot_name"`
file_base=`echo $bot_name|tr -cd "a-zA-Z0-9"`
log_name="$file_base.txt"
if [ "$QUERY_STRING" == "" ]; then
if [ $running -ne 0 ]; then
mem_kb=`echo "$temp"|grep "$bot_name"|awk '{print $6}'`
mem_mb=$( echo "scale=2;$mem_kb/1024"|bc )
mem_24=$( echo "scale=2;$mem_kb*1440/1048576"|bc )
echo "$bot_name is running. <a href='?action=stop'>Stop</a><br>Current memory usage: $mem_mb MB<br>Estimated 24 hour usage: $mem_24 GB - "
else
echo "$bot_name is not running. <a href='?action=start'>Start</a> - "
fi
echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/$control/$log_name'>Full Logs</a><pre>"
tail -30 $pwd/$log_name
echo "</pre><script>reloading = setTimeout('window.location.reload();', 10000);</script>"
fi
ts=`date +"%Y-%m-%d %H:%M:%S"`
if [ "$QUERY_STRING" == "action=stop" ]; then
echo "[$ts] Stopping $bot_name." >> $pwd/$log_name
pid=`echo "$temp"|grep "$bot_name"|tail -1|awk '{print $2}'`
if [ ${#pid} -ne 0 ]; then
kill $pid
fi
echo "Stopping $bot_name...<script>setInterval(\"window.location.replace('/$control/');\", 2000);</script>"
fi
if [ "$QUERY_STRING" == "action=start" ]; then
if [ $running -ne 0 ]; then
echo "$bot_name is already running..."
else
echo "[$ts] Starting $bot_name." >> $pwd/$log_name
/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> $pwd/$log_name 2>&1 &
echo "Starting $bot_name...<script>window.location.replace('/$control/');</script>"
fi
fi
if [ "$QUERY_STRING" == "action=clear" ]; then
cat /dev/null > $pwd/$log_name
echo "Clearing logs...<script>window.location.replace('/$control/');</script>"
fi
exit 0
</pre>

Be sure to edit the variable at the top of the file to match your bot filename.

Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliotelebot.py file earlier.

[[File:755_permissions.png]]

== Test It Out ==

Now everything should be ready to be tested. Open your browser and go to yourdomain.helioho.st/bot_control/ and when you click Start it should start the bot. You can check if the bot is running by going to t.me/YourBotName on Telegram. If everything is working you should be able to type /hello and it will reply to you.

[[File:Telegram-hello.png]]

If it doesn't work go back and check all the steps again to make sure you did everything correctly. You can also check out the logs in the bot_control dashboard to see if there is any errors listed. For example, if you try to import a modules that isn't already installed it will give an error like this:

[[File:Bot_error.png]]

If you can't figure out what is wrong let us know by opening [https://helionet.org/index/forum/45-customer-service/?do=add a customer service ticket].

== Watch Your Account Load ==

{{Caution|Bots use a lot of system resources so we recommend [https://heliohost.org/dashboard/load/ keeping an eye on your account load].}}

We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.
* On the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, if you exceed these limits, your account will be suspended.
* On the [[:Morty|Morty]] server, if you exceed these limits, we will charge you for overages.

On the bot_control dashboard it shows the current memory usage, and the estimated usage over the next 24 hours if your bot continues using the same amount of memory.

[[File:Telegram-bot-dashboard.png]]

If you followed the guide exactly your bot will use about 60 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].

If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

== Automatically Restarting the Bot ==

We've had a lot of people ask us if we intentionally stop their bots after 60 minutes or so. The answer is no. The only time we kill processes automatically is if your account got suspended for high load. In our testing the bots can run for weeks or longer without needing to be restarted. Our servers are stable enough to run for months or years without a reboot as well. The issue is undoubtedly that people write bad code that crashes, but rather than admitting that their code is buggy, it's easier to just blame us.

If your bot keeps stopping on its own, the best solution is to check the logs and fix the issue. If there is nothing shown in the logs that means you need to add more logging to your code to figure out why it's crashing. If you still can't figure it out you could enable auto-restart, but it's really just a crutch for buggy code rather than a real fix. If your bot code really is stable enough to run for weeks or months without crashing, auto-restart can also benefit you in the rare case of us rebooting the whole server, your bot will automatically start up as soon as the reboot is finished.

{{Caution|
Enabling auto-restart could increase your chance of getting suspended. If you don't currently need your bot online we recommend shutting it down entirely rather than leaving it restarting over and over.
}}

To set up auto-restart login to Plesk and navigate to:

'''Login > Plesk > Websites & Domains > [ domain ] > Scheduled Tasks'''

[[File:plesk-scheduled-tasks.png]]

Next, click 'Add Task' and select the 'Fetch a URL' option.

[[File:Plesk-schedule-a-task.png]]

In the URL box put the start link from your bot_control page if you would click 'Start'. The easiest way to get this value is to stop your bot, and then right click on the 'Start' link, and 'Copy link address'.

[[File:Telegram-start-link.png]]

If you followed this guide without changing too much it should be something like 'yourdomain.helioho.st/bot_control/?action=start'.

[[File:Telegram-cron-job.png]]

For those of you who want to minimize the downtime, and maximize your suspension chance you can set the schedule task up to run every minute like this with Cron Style and '* * * * *'. If everything is working correctly it will check if the bot is up every minute. Then if the bot is stopped it will restart it, and if the bot is already running it won't do anything.

{{Danger|
Running a scheduled task every minute increases your load by quite a bit even if your bot never needs to be restarted. Simply checking if it has crashed causes some load. Worst case scenario: this scheduled tasks starts a new bot process every minute even though you already have a copy of the bot running, and you get suspended on [[:Tommy|Tommy]] or [[:Johnny|Johnny]] in record time, or reach the maximum billing on [[:Morty|Morty]] faster than anyone has ever dreamed possible.
}}

[[Category:Tutorials]]

File:Telegram-cron-job.png

2025-03-16T02:32:07Z

Krydos:

File:Telegram-start-link.png

2025-03-16T02:25:20Z

Krydos:

Discord Bot

2025-03-15T21:50:22Z

Krydos: /* Starting and Stopping Your Bot */ Updated index.sh code to help prevent multiple bots running at the same time

== Preface ==

This guide will work on any of the HelioHost servers.

Python is an interpreted, object-oriented, high-level programming language with dynamic semantics. Its high-level built in data structures, combined with dynamic typing and dynamic binding, make it very attractive for Rapid Application Development, as well as for use as a scripting or glue language to connect existing components together. Python's simple, easy to learn syntax emphasizes readability and therefore reduces the cost of program maintenance. Python supports modules and packages, which encourages program modularity and code reuse.

The Discord app works with desktop and mobile platforms, combining the features of a chat lobby, a message board and a VoIP chatting system into one app that's not going to hog resources on your phone or PC. Discord's popularity has only multiplied in recent years, with the app now reaching over 90 million registered users.

Bots and apps are the lifeblood of the Discord development community. They come in all shapes and sizes, from small hobby projects for your server with friends, to huge projects that live in hundreds of thousands of servers. We love seeing the unique, fun, and sometimes downright strange (in a good way) creations that come from our community.

== How to get Started with a Discord Bot ==

First you'll need to have a Discord account, and a Discord channel that you'll add the bot to later. Here's a [https://www.howtogeek.com/364075/how-to-create-set-up-and-manage-your-discord-server/ good guide] to get started.

== Create the Bot ==

Once you have your Discord server all set up it's time to create the bot through Discord's site. Go to [https://discordapp.com/developers/applications discordapp.com/developers/applications] and make sure you're logged in. Then click 'New Application' in the top right.

[[File:New_application.png]]

Type a name and hit create. I decided to name my bot 'HelioBot'.

== Add the Bot to your Discord Server ==

Click 'OAuth2' on the left navigation.

[[File:oauth2.png]]

Then check the bot box under 'SCOPES', and scroll down and select 'Administrator' under 'BOT PERMISSIONS'. You could select the exact permissions that your bot needs one by one, but for this simple example it's easier to just allow the bot permission to do everything.

[[File:bot_admin.png]]

Click copy next to the URL that is generated and open that URL in a new tab. Then, select your Discord server from the dropdown menu.

[[File:add_to_server.png]]

Click 'Authorize' and complete the reCAPTCHA to add the bot to the Discord server. If you go to your Discord now you can see the bot on the offline user list.

[[File:offline_bot.png]]

== Write the Bot Script in Python ==

[https://heliohost.org/login Log in] and continue to Plesk. Then load up the file manager.

[[File:file_manager.png]]

In the top left corner click the '+' plus sign, and select 'Create File'.

[[File:plus_file.png]]

Then type the name of your new file: 'heliobot.py'.

[[File:create_heliobot.png]]

You want to create this bot in your home directory so random hackers and bots on the internet can't access it directly. Make sure it says 'Add a file to: /' not 'Add a file to: /httpdocs' or any other folder.

Scroll down in the file manager and click on the new 'heliobot.py' file to edit it. Then copy/paste this code in:

<pre>
#!/usr/bin/python3.12

import os
import discord
from dotenv import load_dotenv

load_dotenv()
token = os.getenv('DISCORD_TOKEN')

import certifi
os.environ["SSL_CERT_FILE"] = certifi.where()

client = discord.Client(intents=discord.Intents.default())

class MyClient(discord.Client):
async def on_ready(self):
print(f'Logged in as {self.user} (ID: {self.user.id})')
print('------')

async def on_message(self, message):
# we do not want the bot to reply to itself
if message.author.id == self.user.id:
return

if message.content.startswith('!hello'):
await message.reply('Hello!', mention_author=True)

intents = discord.Intents.default()
intents.message_content = True

client = MyClient(intents=intents)
client.run(token)
</pre>

The first line is called the shebang, and it tells the system which version of Python you want to use. Morty, Tommy, and Johnny also have Python 3.9, but we recommend using Python 3.12 like in the example.

Once you have your code copy/pasted in click save in the bottom left corner. Now we need the bot to be executable so in the file manager click the 'rw- r-- r--' on the heliobot.py line.

[[File:change_permissions.png]]

Check all three of the 'Execute/Search' boxes so it looks like this and then click save in the bottom left corner.

[[File:755_permissions.png]]

Now we need to provide our Discord token to the bot so click the '+' plus sign, and select 'Create File' again and this time name the file '.env'.

[[File:dot_env.png]]

'''Make sure you start the filename with a period.''' It's easy to miss that in the screenshot. This file needs to be in the '''same''' directory as your Python script.

Go back to the Discord bot page and click bot on the left navigation again.

[[File:select_bot.png]]

The first thing we need to do on this page is enable 'Presence Intent', 'Server Members Intent', and 'Message Content Intent'. If you're sure your bot doesn't need all three of these enable just what you need, but for simplicity of this guide we're going to enable all three, and then save the changes.

[[File:discord_intents.png]]

On the same page click the 'Reset Token' button, and then copy/paste the token.

[[File:copy_token.png]]

If you ever think someone has gotten your token, for instance if you posted it on a public wiki like I just did, be sure to come back to this page and reset it. Anyone who has your token can do whatever permissions you granted your bot to your server. Now you need to paste this token into your '.env' file that you created. So go back to the Plesk file manager and click the '.env' file to edit it. Paste the token into the file like this:

[[File:paste_the_token.png]]

Make sure the line starts with 'DISCORD_TOKEN=' like that. Then click 'Save Changes' and close the tab. Saving your token separate from your Python code is good practice because this way you can share the code on GitHub or something like that without worrying about people getting access to your bot.

== Starting and Stopping Your Bot ==

You have a functional bot now, but you need a way to start and stop it.

{{Caution|
Side note: Previous versions of this guide used Python scripts to start and stop the Discord bot. Unfortunately, the people who wanted to write their bot in Node.js always complained that they didn't want to use Python for anything. Likewise, if we used Node.js to start and stop the bot, the Python people would inevitably complain about not wanting to use Node.js for anything. Therefore, we wrote the start and stop scripts in Bash CGI to make absolutely sure that no one is happy.
}}

We'll use Bash CGI to do that so you can control your bot through your web page. With the file manager, navigate to '/httpdocs' and create a new directory called 'bot_control'.

[[File:bot_control.png]]

Now create a new file named '.htaccess' in the '/httpdocs/bot_control' directory.

[[File:create_htaccess.png]]

Paste this code into the new '.htaccess' file.

<pre>
Options +ExecCGI
AddHandler cgi-script .sh
DirectoryIndex index.sh
</pre>

Next create a new file named 'index.sh' in the '/httpdocs/bot_control' directory.

[[File:create_indexsh.png]]

Paste the code below into the new file. Remember to use either 'helio'''ho.st'''' or 'helioho'''st.us'''' at the end of your domain, unless you're one of the very few users who still have a legacy heliohost.org domain:

<pre>
#!/bin/bash

# edit these to match your username, main domain, and bot filename
username="krydos"
main_domain="krydos.heliohost.org"
bot_name="heliobot.py"

###################################################################

printf 'Content-Type: text/html\n\n'
temp=`ps axo user:16,pid,pcpu,pmem,vsz,rss,tty,stat,start,time,command|grep -v grep|grep "^$username"`
running=`echo "$temp"|grep -c "$bot_name"`
file_base=`echo $bot_name|tr -cd "a-zA-Z0-9"`
log_name="$file_base.txt"
if [ "$QUERY_STRING" == "" ]; then
if [ $running -ne 0 ]; then
mem_kb=`echo "$temp"|grep "$bot_name"|awk '{print $6}'`
mem_mb=$( echo "scale=2;$mem_kb/1024"|bc )
mem_24=$( echo "scale=2;$mem_kb*1440/1048576"|bc )
echo "$bot_name is running. <a href='?action=stop'>Stop</a><br>Current memory usage: $mem_mb MB<br>Estimated 24 hour usage: $mem_24 GB - "
else
echo "$bot_name is not running. <a href='?action=start'>Start</a> - "
fi
echo "<a href='https://heliohost.org/dashboard/load/' target='_blank'>Check Load</a><br><br>Logs: <a href='?action=clear'>Clear Logs</a> - <a href='/bot_control/$log_name'>Full Logs</a><pre>"
tail -30 /home/$main_domain/httpdocs/bot_control/$log_name
echo "</pre><script>reloading = setTimeout('window.location.reload();', 10000);</script>"
fi
ts=`date +"%Y-%m-%d %H:%M:%S"`
if [ "$QUERY_STRING" == "action=stop" ]; then
echo "[$ts] Stopping $bot_name." >> /home/$main_domain/httpdocs/bot_control/$log_name
pid=`echo "$temp"|grep "$bot_name"|tail -1|awk '{print $2}'`
if [ ${#pid} -ne 0 ]; then
kill $pid
fi
echo "Stopping $bot_name...<script>window.location.replace('/bot_control/');</script>"
fi
if [ "$QUERY_STRING" == "action=start" ]; then
if [ $running -ne 0 ]; then
echo "$bot_name is already running..."
else
echo "[$ts] Starting $bot_name." >> /home/$main_domain/httpdocs/bot_control/$log_name
/usr/bin/python3.12 -u /home/$main_domain/$bot_name >> /home/$main_domain/httpdocs/bot_control/$log_name 2>&1 &
echo "Starting $bot_name...<script>window.location.replace('/bot_control/');</script>"
fi
fi
if [ "$QUERY_STRING" == "action=clear" ]; then
cat /dev/null > /home/$main_domain/httpdocs/bot_control/$log_name
echo "Clearing logs...<script>window.location.replace('/bot_control/');</script>"
fi
exit 0
</pre>

Be sure to edit the three variables at the top of the file to match your username, main domain, and bot filename.

Now, we need to set the permissions of this 'index.sh' file to be executable. On the file manager click the 'rw- r-- r--' and check all the 'Execute/Search' boxes just like we did the heliobot.py file earlier.

[[File:755_permissions.png]]

== Test It Out ==

Now everything should be ready to be tested. Open your browser and go to 'yourdomain.helioho.st/bot_control/' and when you click Start it should start the bot. You can check if the bot is running by going to Discord and seeing if HelioBot is showing up as online now. If it is, test it out by typing the command:

<pre>
!hello
</pre>

It should respond to you.

[[File:testing_discord_bot.png]]

If it doesn't work go back and check all the steps again to make sure you did everything correctly. You can also check out the logs in the bot_control dashboard to see if there is any errors listed. For example, if you try to import a modules that isn't already installed it will give an error like this:

[[File:bot_error.png]]

If you can't figure out what is wrong let us know by opening [https://helionet.org/index/forum/45-customer-service/?do=add a customer service ticket].

== Watch Your Account Load ==

{{Caution|Bots use a lot of system resources so we recommend [https://heliohost.org/dashboard/load/ keeping an eye on your account load].}}

We enforce a memory limit of no more than {{Template:MemoryLimit}} per day and a limit of {{Template:CPULimit}} usage per day on our shared hosting servers.
* On the [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, if you exceed these limits, your account will be suspended.
* On the [[:Morty|Morty]] server, if you exceed these limits, we will charge you for overages.

On the bot_control dashboard it shows the current memory usage, and the estimated usage over the next 24 hours if your bot continues using the same amount of memory.

[[File:bot_dashboard.png]]

If you followed the guide exactly your bot will use about 50 GB of memory per day, which is 1/4 of your allowed amount. If you edit your bot code, make your bot more complicated, and import more modules it will increase the memory usage though. Obviously if you have some sort of memory leak it could easily allow your bot to continue consuming more and more memory until you get [[:Suspension_Policy#High_Server_Usage|suspended]] on [[:Tommy]] and [[:Johnny]], or charged for overages on [[:Morty|Morty]].

If everything is working you can shut your bot down by clicking the Stop button on the bot_control dashboard. It's a good idea to keep your bot offline if you don't need it so you don't cause too much load. If you're having trouble staying under the limits you could also consider [https://heliohost.org/dashboard/move/?move=morty-prepay moving to the Morty plan] where there is no load limit, or [https://heliohost.org/vps/ moving to a VPS] where you have root SSH access, dedicated memory, dedicated CPU, and no load limits. You can get a 10% discount when you pay for 6 months upfront.

[[Category:Tutorials]]