HelioHost Wiki - User contributions [en]

PHP

2026-04-05T15:57:24Z

KazVee: Add new 'PHP Configuration Limits' section

== PHP ==

PHP is the most popular scripting language on the Internet for a reason. It's easy to learn and easy to implement, yet is powerful enough to suit almost every task. Unlike some other languages, PHP is not explicitly linked with any programming paradigms, allowing for more flexible development. HelioHost offers the latest versions of PHP on all its hosting accounts. We are unique in that we offer PHP without safe mode, which is the more secure but less functional alternative that you'll find on most free hosts.

== PHP Versions Supported ==

The PHP versions supported on each server are listed below. To see the PHP packages installed for each version, click on the 'phpinfo()' link. To check if a specific package is installed, press <code>Ctrl + F</code> and type in the package name to search the page.

== Morty server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Morty server'''
|-
! PHP Version !! Packages Installed
|-
| PHP 5.6 || [https://php56.krydos3.heliohost.org phpinfo()]
|-
| PHP 7.0 || [https://php70.krydos3.heliohost.org phpinfo()]
|-
| PHP 7.4 || [https://php74.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.0 || [https://php80.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.1 || [https://php81.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.2 || [https://php82.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.3 || [https://php83.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.4 || [https://php84.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.5 || [https://php85.krydos3.heliohost.org phpinfo()]
|}

== Tommy server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Tommy server'''
|-
! PHP Version !! Packages Installed
|-
| PHP 5.6 || [https://php56.krydos1.heliohost.org phpinfo()]
|-
| PHP 7.0 || [https://php70.krydos1.heliohost.org phpinfo()]
|-
| PHP 7.4 || [https://php74.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.0 || [https://php80.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.1 || [https://php81.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.2 || [https://php82.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.3 || [https://php83.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.4 || [https://php84.krydos1.heliohost.org phpinfo()]
|}

== Johnny server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Johnny server'''
|-
! PHP Version !! Packages Installed
|-
| PHP 5.6 || [https://php56.krydos2.heliohost.org phpinfo()]
|-
| PHP 7.0 || [https://php70.krydos2.heliohost.org phpinfo()]
|-
| PHP 7.4 || [https://php74.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.0 || [https://php80.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.1 || [https://php81.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.2 || [https://php82.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.3 || [https://php83.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.4 || [https://php84.krydos2.heliohost.org phpinfo()]
|}

== Lily server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Lily server'''
|-
! PHP Version
|-
| 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
|-
| PHP 8.4
|-
| PHP 8.5
|}

== PHP Packages Installed ==

=== Inside Plesk ===

Follow the navigation steps below to view which PHP packages are installed:

'''Login > Plesk > Websites & Domains > [domain] > Dashboard tab > Dev Tools > PHP button > click on the ' View the phpinfo() page' link'''

To check if a specific package is installed, press <code>Ctrl + F</code> and type in the package name to search the page. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

[[File:View-phpinfo.png]]

=== View phpinfo() page ===

If you don't have a HelioHost account to access information within Plesk, you can view the installed PHP packages for the available PHP versions on our servers by checking [[#PHP_Versions_Supported|the relevant phpinfo() page links here]].

== Request Additional PHP Packages ==

{{Caution|
Before requesting additional modules, make sure you check the [[:PHP#PHP_Packages_Installed|list of packages already installed]] on your server.

When viewing the [[:PHP#PHP_Packages_Installed|list of packages already installed]], press '''Ctrl + F''' to search the page for a package name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request packages that are already installed.}}

'''After you have checked''' the [[:PHP#PHP_Packages_Installed|list of packages already installed]], if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:PHP#PHP_Packages_Installed|list of packages already installed]] on your server for the version of PHP you're using.
# Your account username.
# Your server.
# The version of PHP you're using.
# The package(s) you need, including any specific version numbers.

== PHP Configuration Limits ==

On the [[:Morty]], [[:Tommy]], and [[:Johnny]] shared hosting accounts, the '''memory_limit''' and '''max_execution_time''' are intentionally limited to prevent excessive load to all users on the server. If you need these values increased, it's likely you will need a VPS. {{Template:VPSInfo}}

If you are installing something that requires larger uploads, you can request a temporary increase to the '''post_max_size''' and '''upload_max_filesize''' values. Approval is not guaranteed, and any changes will be reverted after installation.

To request a temporary increase of the upload and post sizes, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Your account username.
# Your server.
# The version of PHP you're using.
# What you're trying to install.
# What values your installer is requesting for the '''post_max_size''' and '''upload_max_filesize''' values.

== Using proc_open(), exec(), popen(), etc. ==

These functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

== Learning PHP ==

'<?php' is the opening braces and '?>' is the closing braces for PHP.

Here is a sample hello world file.

<pre>
<?php
echo "Hello World!";
?>
</pre>

A good tutorial can be found here: [https://blog.udemy.com/php-tutorial/ https://blog.udemy.com/php-tutorial].

== Change PHP Version ==

Follow the navigation steps below to change your PHP version inside Plesk:

'''Login > Plesk > Websites & Domains > [domain] > Dashboard tab > Dev Tools > PHP button > select PHP version from the dropdown menu'''

[[File:plesk-change-php-version.png]]

After the PHP version is changed, you will see a confirmation message that contains the timeframe for the change to take effect:

[[File:plesk-php-change-120-min.png]]

== PHP Version Changes Take Up To 2 Hours ==

{{Info|PHP version changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

PHP

2026-04-05T15:40:32Z

KazVee: Add new 'Request Additional PHP Packages' section

== PHP ==

PHP is the most popular scripting language on the Internet for a reason. It's easy to learn and easy to implement, yet is powerful enough to suit almost every task. Unlike some other languages, PHP is not explicitly linked with any programming paradigms, allowing for more flexible development. HelioHost offers the latest versions of PHP on all its hosting accounts. We are unique in that we offer PHP without safe mode, which is the more secure but less functional alternative that you'll find on most free hosts.

== PHP Versions Supported ==

The PHP versions supported on each server are listed below. To see the PHP packages installed for each version, click on the 'phpinfo()' link. To check if a specific package is installed, press <code>Ctrl + F</code> and type in the package name to search the page.

== Morty server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Morty server'''
|-
! PHP Version !! Packages Installed
|-
| PHP 5.6 || [https://php56.krydos3.heliohost.org phpinfo()]
|-
| PHP 7.0 || [https://php70.krydos3.heliohost.org phpinfo()]
|-
| PHP 7.4 || [https://php74.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.0 || [https://php80.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.1 || [https://php81.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.2 || [https://php82.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.3 || [https://php83.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.4 || [https://php84.krydos3.heliohost.org phpinfo()]
|-
| PHP 8.5 || [https://php85.krydos3.heliohost.org phpinfo()]
|}

== Tommy server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Tommy server'''
|-
! PHP Version !! Packages Installed
|-
| PHP 5.6 || [https://php56.krydos1.heliohost.org phpinfo()]
|-
| PHP 7.0 || [https://php70.krydos1.heliohost.org phpinfo()]
|-
| PHP 7.4 || [https://php74.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.0 || [https://php80.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.1 || [https://php81.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.2 || [https://php82.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.3 || [https://php83.krydos1.heliohost.org phpinfo()]
|-
| PHP 8.4 || [https://php84.krydos1.heliohost.org phpinfo()]
|}

== Johnny server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Johnny server'''
|-
! PHP Version !! Packages Installed
|-
| PHP 5.6 || [https://php56.krydos2.heliohost.org phpinfo()]
|-
| PHP 7.0 || [https://php70.krydos2.heliohost.org phpinfo()]
|-
| PHP 7.4 || [https://php74.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.0 || [https://php80.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.1 || [https://php81.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.2 || [https://php82.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.3 || [https://php83.krydos2.heliohost.org phpinfo()]
|-
| PHP 8.4 || [https://php84.krydos2.heliohost.org phpinfo()]
|}

== Lily server ==

{| class="wikitable"
|+ style="caption-side:top; |'''Lily server'''
|-
! PHP Version
|-
| 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
|-
| PHP 8.4
|-
| PHP 8.5
|}

== PHP Packages Installed ==

=== Inside Plesk ===

Follow the navigation steps below to view which PHP packages are installed:

'''Login > Plesk > Websites & Domains > [domain] > Dashboard tab > Dev Tools > PHP button > click on the ' View the phpinfo() page' link'''

To check if a specific package is installed, press <code>Ctrl + F</code> and type in the package name to search the page. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

[[File:View-phpinfo.png]]

=== View phpinfo() page ===

If you don't have a HelioHost account to access information within Plesk, you can view the installed PHP packages for the available PHP versions on our servers by checking [[#PHP_Versions_Supported|the relevant phpinfo() page links here]].

== Request Additional PHP Packages ==

{{Caution|
Before requesting additional modules, make sure you check the [[:PHP#PHP_Packages_Installed|list of packages already installed]] on your server.

When viewing the [[:PHP#PHP_Packages_Installed|list of packages already installed]], press '''Ctrl + F''' to search the page for a package name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request packages that are already installed.}}

'''After you have checked''' the [[:PHP#PHP_Packages_Installed|list of packages already installed]], if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:PHP#PHP_Packages_Installed|list of packages already installed]] on your server for the version of PHP you're using.
# Your account username.
# Your server.
# The version of PHP you're using.
# The package(s) you need, including any specific version numbers.

== Using proc_open(), exec(), popen(), etc. ==

These functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

== Learning PHP ==

'<?php' is the opening braces and '?>' is the closing braces for PHP.

Here is a sample hello world file.

<pre>
<?php
echo "Hello World!";
?>
</pre>

A good tutorial can be found here: [https://blog.udemy.com/php-tutorial/ https://blog.udemy.com/php-tutorial].

== Change PHP Version ==

Follow the navigation steps below to change your PHP version inside Plesk:

'''Login > Plesk > Websites & Domains > [domain] > Dashboard tab > Dev Tools > PHP button > select PHP version from the dropdown menu'''

[[File:plesk-change-php-version.png]]

After the PHP version is changed, you will see a confirmation message that contains the timeframe for the change to take effect:

[[File:plesk-php-change-120-min.png]]

== PHP Version Changes Take Up To 2 Hours ==

{{Info|PHP version changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

Django on HelioHost

2026-04-04T17:38:07Z

KazVee: Add note that modules already installed on the server can be used right away

== Django 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.

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[:Django_on_HelioHost#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]].
}}

== Complete Django ==

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

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of Python modules already installed]] on your server.

When viewing the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of modules already installed]], press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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.

== Getting started with Django on HelioHost ==

This brief tutorial will guide you through setting up a Django test app without using the command line on your development system.

If you already have an existing Django app or prefer to use the command line, our tutorial on [[:Converting_an_Existing_Django_App|Converting an Existing Django App]] may better suit your needs.

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

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 'djangotest' directory 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>

== Create another 'djangotest' directory within the first 'djangotest' directory ==

This directory structure 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' is being used in this example.

== Create a 'dispatch.wsgi' file inside the second 'djangotest' 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.

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"}}

<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>

== Create a '__init__.py' file inside the second 'djangotest' directory ==

This file should remain empty.

== Create a 'urls.py' file inside the second 'djangotest' directory with these contents: ==

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

== Create a 'settings.py' file inside the second 'djangotest' directory with these contents: ==

<pre>
from pathlib import Path
# Build paths inside the project like this: BASE_DIR / 'subdir'.
BASE_DIR = Path(__file__).resolve().parent.parent
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/4.1/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'django-makeyoursecretbetterthanthis'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = ['*']
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'djangotest.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'djangotest.wsgi.application'
# Database
# https://docs.djangoproject.com/en/4.1/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
# Password validation
# https://docs.djangoproject.com/en/4.1/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/4.1/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.1/howto/static-files/
STATIC_URL = 'static/'
# Default primary key field type
# https://docs.djangoproject.com/en/4.1/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
</pre>

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

<pre>
djangotest/
├── djangotest
│ ├── dispatch.wsgi
│ ├── __init__.py
│ ├── settings.py
│ └── urls.py
└── .htaccess
1 directory, 5 files
</pre>

== Visit Your Site ==

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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 Django 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 '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 ==

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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== References ==

This tutorial is adapted from [https://helionet.org/index/topic/53855-how-to-use-django-on-plesk/ this post].

[[Category:Tutorials]]

Flask

2026-04-04T17:28:52Z

KazVee: Add internal link so users can find how to check the list of modules already installed

== 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].

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, find use the '''View''' link for the server, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

== 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
|}

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.

When viewing the [[:Flask#Viewing_Installed_Python_Modules|list of Python modules already installed]], press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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. 
<a href="/flasktest/python/version/">Python version</a> 
<a href="/flasktest/flask/version/">Flask version</a>

"""

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

@app.route("/flask/version/")
def f_version():
return "Flask version %s <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 Flask 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]]

Converting an Existing Django App

2026-04-04T17:28:12Z

KazVee: Add internal links so users can find how to check the list of modules already installed

== 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.

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[#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 [[:MariaDB|MariaDB]], MySQL, [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.

When viewing the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of Python modules already installed]], press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 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. 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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== 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].

[[Category:Tutorials]]

Python Tutorial

2026-04-04T17:27:06Z

KazVee: Add internal links so users can find how to check the list of modules already installed

== Python ==

The easiest way to get started with Python on a server is with CGI. The only real difference between CGI and running the script on your home computer is that CGI needs to output a 'Content-Type' header.

{{Info|We also have tutorials for building with [[:Flask|Flask]], [[:Django_on_HelioHost|creating a new Django project]], and [[:Converting_an_Existing_Django_App|converting an existing Django app to work on HelioHost]].}}

== Python Versions Available ==

Below are details of the Python versions available on each server, and links to view the Python modules already installed.

=== Viewing Installed Python Modules ===

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

=== Morty Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos3.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View]
|}

=== Tommy Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos1.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View]
|}

=== Johnny Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos2.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View]
|}

== Steps ==

* Open the File Manager in Plesk
* Open the 'httpdocs' webroot directory. (If you were transferred from the old cPanel, the directory will be called 'public_html'.)
* Open the 'cgi-bin' directory
* In the top left click the '+' button and select 'Create File'
* Type 'test.py' as your filename
* Click 'OK' to create the file
* Highlight the 'test.py' file and select 'Change Permissions'
* Add a checkmark to the 'Execute / Search' column for all three rows (Owner / Group / Others)
* Click the 'Save' button
* Make sure 'rwx r-x r-x' ('755') is displayed under the Permissions column
* Highlight 'test.py' and select 'Edit in Text Editor'
* Leave 'UTF-8' as the encoding, set 'Line break type' to 'Convert to Unix style' and copy/paste the below into the large text field:

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

print("Content-Type: text/html\n\n")

print("Heliohost rules!")
</pre>

* Click the 'Save' button
* Highlight the 'test.py' file and select 'Open in Browser' (Or manually navigate to: '<your subdomain>.helioho.st/cgi-bin/test.py')

If everything worked, you should see 'HelioHost rules!' displayed in your browser.

== Code Explanation ==

In the code pasted in, the first line is called the 'shebang'. It tells the server which version of Python to use.

The second line of code is the 'Content-Type' header. This is important so the server knows what to do with the output that follows. If you forget it, your script will give you an error. The 'Content-Type' header always has to have the two end lines immediately after it. That's what the two '\n' are.

== Troubleshooting ==

If you don't see the module you need, your script will probably give you an error when you try to import the missing module. You can [[View_Error_Logs|view your account error logs]] for details on which module is missing and causing the error.

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server.

When viewing the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]], press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== Running Python scripts outside cgi-bin folder ==

Executing a CGI script outside the 'cgi-bin' folder is possible with some modifications.

== Steps ==

* Go to '/home/<your username>/httpdocs'. (If you were transferred from the old cPanel, the folder will be called 'public_html')
* Create a file named '.htaccess' and copy/paste the below in:

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

The first two lines make '.py' files executable outside 'cgi-bin', and the last line makes the filename 'index.py' show up if someone goes to your domain without having to type out the filename like 'domain.helioho.st/index.py'. This also supports other CGI file extensions.

== 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.

Converting an Existing Django App

2026-04-04T17:25:04Z

KazVee: Add internal links so users know how to check the list of modules already installed

== 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.

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[#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 [[:MariaDB|MariaDB]], MySQL, [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Converting_an_Existing_Django_App#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 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. 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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== 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].

[[Category:Tutorials]]

Django on HelioHost

2026-04-04T17:22:33Z

KazVee: Add internal links so users can find the list of modules already installed

== Django 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.

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[:Django_on_HelioHost#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]].
}}

== Complete Django ==

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

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of Python modules already installed]] on your server.

When viewing the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of modules already installed]], press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Django_on_HelioHost#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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.

== Getting started with Django on HelioHost ==

This brief tutorial will guide you through setting up a Django test app without using the command line on your development system.

If you already have an existing Django app or prefer to use the command line, our tutorial on [[:Converting_an_Existing_Django_App|Converting an Existing Django App]] may better suit your needs.

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

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 'djangotest' directory 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>

== Create another 'djangotest' directory within the first 'djangotest' directory ==

This directory structure 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' is being used in this example.

== Create a 'dispatch.wsgi' file inside the second 'djangotest' 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.

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"}}

<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>

== Create a '__init__.py' file inside the second 'djangotest' directory ==

This file should remain empty.

== Create a 'urls.py' file inside the second 'djangotest' directory with these contents: ==

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

== Create a 'settings.py' file inside the second 'djangotest' directory with these contents: ==

<pre>
from pathlib import Path
# Build paths inside the project like this: BASE_DIR / 'subdir'.
BASE_DIR = Path(__file__).resolve().parent.parent
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/4.1/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'django-makeyoursecretbetterthanthis'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = ['*']
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'djangotest.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'djangotest.wsgi.application'
# Database
# https://docs.djangoproject.com/en/4.1/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
# Password validation
# https://docs.djangoproject.com/en/4.1/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/4.1/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.1/howto/static-files/
STATIC_URL = 'static/'
# Default primary key field type
# https://docs.djangoproject.com/en/4.1/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
</pre>

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

<pre>
djangotest/
├── djangotest
│ ├── dispatch.wsgi
│ ├── __init__.py
│ ├── settings.py
│ └── urls.py
└── .htaccess
1 directory, 5 files
</pre>

== Visit Your Site ==

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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 Django 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 '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 ==

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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== References ==

This tutorial is adapted from [https://helionet.org/index/topic/53855-how-to-use-django-on-plesk/ this post].

[[Category:Tutorials]]

Django on HelioHost

2026-04-04T17:18:17Z

KazVee: Add note that installed modules can be used right away, change header to 'Viewing Installed Python Modules' from 'Django Versions Available' for clarity

== Django 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.

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[:Django_on_HelioHost#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]].
}}

== Complete Django ==

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

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the list of modules already installed on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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.

== Getting started with Django on HelioHost ==

This brief tutorial will guide you through setting up a Django test app without using the command line on your development system.

If you already have an existing Django app or prefer to use the command line, our tutorial on [[:Converting_an_Existing_Django_App|Converting an Existing Django App]] may better suit your needs.

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

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 'djangotest' directory 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>

== Create another 'djangotest' directory within the first 'djangotest' directory ==

This directory structure 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' is being used in this example.

== Create a 'dispatch.wsgi' file inside the second 'djangotest' 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.

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"}}

<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>

== Create a '__init__.py' file inside the second 'djangotest' directory ==

This file should remain empty.

== Create a 'urls.py' file inside the second 'djangotest' directory with these contents: ==

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

== Create a 'settings.py' file inside the second 'djangotest' directory with these contents: ==

<pre>
from pathlib import Path
# Build paths inside the project like this: BASE_DIR / 'subdir'.
BASE_DIR = Path(__file__).resolve().parent.parent
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/4.1/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'django-makeyoursecretbetterthanthis'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = ['*']
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'djangotest.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'djangotest.wsgi.application'
# Database
# https://docs.djangoproject.com/en/4.1/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
# Password validation
# https://docs.djangoproject.com/en/4.1/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/4.1/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.1/howto/static-files/
STATIC_URL = 'static/'
# Default primary key field type
# https://docs.djangoproject.com/en/4.1/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
</pre>

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

<pre>
djangotest/
├── djangotest
│ ├── dispatch.wsgi
│ ├── __init__.py
│ ├── settings.py
│ └── urls.py
└── .htaccess
1 directory, 5 files
</pre>

== Visit Your Site ==

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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 Django 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 '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 ==

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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== References ==

This tutorial is adapted from [https://helionet.org/index/topic/53855-how-to-use-django-on-plesk/ this post].

[[Category:Tutorials]]

Converting an Existing Django App

2026-04-04T17:15:51Z

KazVee: Add note that installed modules can be used right away, change header to 'Viewing Installed Python Modules' from 'Django Versions Available' for clarity

== 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.

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[#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 [[:MariaDB|MariaDB]], MySQL, [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the list of modules already installed on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 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. 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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== 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].

[[Category:Tutorials]]

Flask

2026-04-04T17:12:27Z

KazVee: Add another internal link so users can find the list of modules already installed

== 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].

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, find use the '''View''' link for the server, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

== 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
|}

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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. 
<a href="/flasktest/python/version/">Python version</a> 
<a href="/flasktest/flask/version/">Flask version</a>

"""

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

@app.route("/flask/version/")
def f_version():
return "Flask version %s <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 Flask 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-04-04T16:54:21Z

KazVee: Move 'Request Additional Python Modules' section to below the servers list, add internal links

== 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].

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, find use the '''View''' link for the server, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

== 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
|}

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Flask#Viewing_Installed_Python_Modules|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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. 
<a href="/flasktest/python/version/">Python version</a> 
<a href="/flasktest/flask/version/">Flask version</a>

"""

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

@app.route("/flask/version/")
def f_version():
return "Flask version %s <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 Flask 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]]

Python Tutorial

2026-04-04T16:42:40Z

KazVee: Additional clarity that installed modules can be used right away

== Python ==

The easiest way to get started with Python on a server is with CGI. The only real difference between CGI and running the script on your home computer is that CGI needs to output a 'Content-Type' header.

{{Info|We also have tutorials for building with [[:Flask|Flask]], [[:Django_on_HelioHost|creating a new Django project]], and [[:Converting_an_Existing_Django_App|converting an existing Django app to work on HelioHost]].}}

== Python Versions Available ==

Below are details of the Python versions available on each server, and links to view the Python modules already installed.

=== Viewing Installed Python Modules ===

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

=== Morty Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos3.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View]
|}

=== Tommy Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos1.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View]
|}

=== Johnny Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos2.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View]
|}

== Steps ==

* Open the File Manager in Plesk
* Open the 'httpdocs' webroot directory. (If you were transferred from the old cPanel, the directory will be called 'public_html'.)
* Open the 'cgi-bin' directory
* In the top left click the '+' button and select 'Create File'
* Type 'test.py' as your filename
* Click 'OK' to create the file
* Highlight the 'test.py' file and select 'Change Permissions'
* Add a checkmark to the 'Execute / Search' column for all three rows (Owner / Group / Others)
* Click the 'Save' button
* Make sure 'rwx r-x r-x' ('755') is displayed under the Permissions column
* Highlight 'test.py' and select 'Edit in Text Editor'
* Leave 'UTF-8' as the encoding, set 'Line break type' to 'Convert to Unix style' and copy/paste the below into the large text field:

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

print("Content-Type: text/html\n\n")

print("Heliohost rules!")
</pre>

* Click the 'Save' button
* Highlight the 'test.py' file and select 'Open in Browser' (Or manually navigate to: '<your subdomain>.helioho.st/cgi-bin/test.py')

If everything worked, you should see 'HelioHost rules!' displayed in your browser.

== Code Explanation ==

In the code pasted in, the first line is called the 'shebang'. It tells the server which version of Python to use.

The second line of code is the 'Content-Type' header. This is important so the server knows what to do with the output that follows. If you forget it, your script will give you an error. The 'Content-Type' header always has to have the two end lines immediately after it. That's what the two '\n' are.

== Troubleshooting ==

If you don't see the module you need, your script will probably give you an error when you try to import the missing module. You can [[View_Error_Logs|view your account error logs]] for details on which module is missing and causing the error.

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== Running Python scripts outside cgi-bin folder ==

Executing a CGI script outside the 'cgi-bin' folder is possible with some modifications.

== Steps ==

* Go to '/home/<your username>/httpdocs'. (If you were transferred from the old cPanel, the folder will be called 'public_html')
* Create a file named '.htaccess' and copy/paste the below in:

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

The first two lines make '.py' files executable outside 'cgi-bin', and the last line makes the filename 'index.py' show up if someone goes to your domain without having to type out the filename like 'domain.helioho.st/index.py'. This also supports other CGI file extensions.

== 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.

Converting an Existing Django App

2026-04-04T16:42:12Z

KazVee: Additional clarity that installed modules can be used right away

== 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|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[#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 [[:MariaDB|MariaDB]], MySQL, [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the list of modules already installed on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 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. 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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== 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].

[[Category:Tutorials]]

Django on HelioHost

2026-04-04T16:40:40Z

KazVee: Additional clarity that installed modules can be used right away

== Django 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|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[:Django_on_HelioHost#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]].
}}

== Complete Django ==

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

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

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 you have checked''' the list of modules already installed on your server, 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]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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.

== Getting started with Django on HelioHost ==

This brief tutorial will guide you through setting up a Django test app without using the command line on your development system.

If you already have an existing Django app or prefer to use the command line, our tutorial on [[:Converting_an_Existing_Django_App|Converting an Existing Django App]] may better suit your needs.

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

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 'djangotest' directory 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>

== Create another 'djangotest' directory within the first 'djangotest' directory ==

This directory structure 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' is being used in this example.

== Create a 'dispatch.wsgi' file inside the second 'djangotest' 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.

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"}}

<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>

== Create a '__init__.py' file inside the second 'djangotest' directory ==

This file should remain empty.

== Create a 'urls.py' file inside the second 'djangotest' directory with these contents: ==

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

== Create a 'settings.py' file inside the second 'djangotest' directory with these contents: ==

<pre>
from pathlib import Path
# Build paths inside the project like this: BASE_DIR / 'subdir'.
BASE_DIR = Path(__file__).resolve().parent.parent
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/4.1/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'django-makeyoursecretbetterthanthis'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = ['*']
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'djangotest.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'djangotest.wsgi.application'
# Database
# https://docs.djangoproject.com/en/4.1/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
# Password validation
# https://docs.djangoproject.com/en/4.1/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/4.1/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.1/howto/static-files/
STATIC_URL = 'static/'
# Default primary key field type
# https://docs.djangoproject.com/en/4.1/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
</pre>

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

<pre>
djangotest/
├── djangotest
│ ├── dispatch.wsgi
│ ├── __init__.py
│ ├── settings.py
│ └── urls.py
└── .htaccess
1 directory, 5 files
</pre>

== Visit Your Site ==

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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 Django 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 '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 ==

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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== References ==

This tutorial is adapted from [https://helionet.org/index/topic/53855-how-to-use-django-on-plesk/ this post].

[[Category:Tutorials]]

Flask

2026-04-04T16:38:00Z

KazVee: Add new Step 1 that users should confirm they already checked the list of installed modules

== 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].

== Viewing Installed Python Modules ==

{{Info|To check if a module is already installed, find use the '''View''' link for the server, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away.}}

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and can be used right away, so you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the list of modules already installed on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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. 
<a href="/flasktest/python/version/">Python version</a> 
<a href="/flasktest/flask/version/">Flask version</a>

"""

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

@app.route("/flask/version/")
def f_version():
return "Flask version %s <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 Flask 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]]

Converting an Existing Django App

2026-04-04T16:22:35Z

KazVee: Add new Step 1 that users should confirm they already checked the list of installed modules

== 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|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[#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 [[:MariaDB|MariaDB]], MySQL, [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and you do not need to request it.

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 you have checked''' the list of modules 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]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 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. 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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== 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].

[[Category:Tutorials]]

Django on HelioHost

2026-04-04T16:19:22Z

KazVee: Add new Step 1 that users should confirm they already checked the list of installed modules

== Django 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|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[:Django_on_HelioHost#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]].
}}

== Complete Django ==

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

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and you do not need to request it.

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 you have checked''' the list of modules 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]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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.

== Getting started with Django on HelioHost ==

This brief tutorial will guide you through setting up a Django test app without using the command line on your development system.

If you already have an existing Django app or prefer to use the command line, our tutorial on [[:Converting_an_Existing_Django_App|Converting an Existing Django App]] may better suit your needs.

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

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 'djangotest' directory 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>

== Create another 'djangotest' directory within the first 'djangotest' directory ==

This directory structure 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' is being used in this example.

== Create a 'dispatch.wsgi' file inside the second 'djangotest' 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.

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"}}

<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>

== Create a '__init__.py' file inside the second 'djangotest' directory ==

This file should remain empty.

== Create a 'urls.py' file inside the second 'djangotest' directory with these contents: ==

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

== Create a 'settings.py' file inside the second 'djangotest' directory with these contents: ==

<pre>
from pathlib import Path
# Build paths inside the project like this: BASE_DIR / 'subdir'.
BASE_DIR = Path(__file__).resolve().parent.parent
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/4.1/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'django-makeyoursecretbetterthanthis'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = ['*']
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'djangotest.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'djangotest.wsgi.application'
# Database
# https://docs.djangoproject.com/en/4.1/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
# Password validation
# https://docs.djangoproject.com/en/4.1/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/4.1/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.1/howto/static-files/
STATIC_URL = 'static/'
# Default primary key field type
# https://docs.djangoproject.com/en/4.1/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
</pre>

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

<pre>
djangotest/
├── djangotest
│ ├── dispatch.wsgi
│ ├── __init__.py
│ ├── settings.py
│ └── urls.py
└── .htaccess
1 directory, 5 files
</pre>

== Visit Your Site ==

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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 Django 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 '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 ==

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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== References ==

This tutorial is adapted from [https://helionet.org/index/topic/53855-how-to-use-django-on-plesk/ this post].

[[Category:Tutorials]]

Python Tutorial

2026-04-04T16:13:56Z

KazVee: Removed extra word

== Python ==

The easiest way to get started with Python on a server is with CGI. The only real difference between CGI and running the script on your home computer is that CGI needs to output a 'Content-Type' header.

{{Info|We also have tutorials for building with [[:Flask|Flask]], [[:Django_on_HelioHost|creating a new Django project]], and [[:Converting_an_Existing_Django_App|converting an existing Django app to work on HelioHost]].}}

== Python Versions Available ==

Below are details of the Python versions available on each server, and links to view the Python modules already installed.

=== Viewing Installed Python Modules ===

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

=== Morty Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos3.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View]
|}

=== Tommy Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos1.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View]
|}

=== Johnny Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos2.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View]
|}

== Steps ==

* Open the File Manager in Plesk
* Open the 'httpdocs' webroot directory. (If you were transferred from the old cPanel, the directory will be called 'public_html'.)
* Open the 'cgi-bin' directory
* In the top left click the '+' button and select 'Create File'
* Type 'test.py' as your filename
* Click 'OK' to create the file
* Highlight the 'test.py' file and select 'Change Permissions'
* Add a checkmark to the 'Execute / Search' column for all three rows (Owner / Group / Others)
* Click the 'Save' button
* Make sure 'rwx r-x r-x' ('755') is displayed under the Permissions column
* Highlight 'test.py' and select 'Edit in Text Editor'
* Leave 'UTF-8' as the encoding, set 'Line break type' to 'Convert to Unix style' and copy/paste the below into the large text field:

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

print("Content-Type: text/html\n\n")

print("Heliohost rules!")
</pre>

* Click the 'Save' button
* Highlight the 'test.py' file and select 'Open in Browser' (Or manually navigate to: '<your subdomain>.helioho.st/cgi-bin/test.py')

If everything worked, you should see 'HelioHost rules!' displayed in your browser.

== Code Explanation ==

In the code pasted in, the first line is called the 'shebang'. It tells the server which version of Python to use.

The second line of code is the 'Content-Type' header. This is important so the server knows what to do with the output that follows. If you forget it, your script will give you an error. The 'Content-Type' header always has to have the two end lines immediately after it. That's what the two '\n' are.

== Troubleshooting ==

If you don't see the module you need, your script will probably give you an error when you try to import the missing module. You can [[View_Error_Logs|view your account error logs]] for details on which module is missing and causing the error.

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you checked the list of modules already installed on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== Running Python scripts outside cgi-bin folder ==

Executing a CGI script outside the 'cgi-bin' folder is possible with some modifications.

== Steps ==

* Go to '/home/<your username>/httpdocs'. (If you were transferred from the old cPanel, the folder will be called 'public_html')
* Create a file named '.htaccess' and copy/paste the below in:

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

The first two lines make '.py' files executable outside 'cgi-bin', and the last line makes the filename 'index.py' show up if someone goes to your domain without having to type out the filename like 'domain.helioho.st/index.py'. This also supports other CGI file extensions.

== 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.

Python Tutorial

2026-04-04T16:13:27Z

KazVee: Add new Step 1 that users should confirm they already checked the list of installed modules

== Python ==

The easiest way to get started with Python on a server is with CGI. The only real difference between CGI and running the script on your home computer is that CGI needs to output a 'Content-Type' header.

{{Info|We also have tutorials for building with [[:Flask|Flask]], [[:Django_on_HelioHost|creating a new Django project]], and [[:Converting_an_Existing_Django_App|converting an existing Django app to work on HelioHost]].}}

== Python Versions Available ==

Below are details of the Python versions available on each server, and links to view the Python modules already installed.

=== Viewing Installed Python Modules ===

{{Info|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

=== Morty Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos3.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos3.heliohost.org/pyinfo/info3.12.py View]
|}

=== Tommy Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos1.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos1.heliohost.org/pyinfo/info3.12.py View]
|}

=== Johnny Server ===

{| class="wikitable" style="margin:auto"
|-
! Python Version !! Python Path !! Python Modules Installed
|-
| 3.9 || #!/usr/bin/python3.9 || [https://krydos2.heliohost.org/pyinfo/info3.9.py View]
|-
| 3.12 || #!/usr/bin/python3.12 || [https://krydos2.heliohost.org/pyinfo/info3.12.py View]
|}

== Steps ==

* Open the File Manager in Plesk
* Open the 'httpdocs' webroot directory. (If you were transferred from the old cPanel, the directory will be called 'public_html'.)
* Open the 'cgi-bin' directory
* In the top left click the '+' button and select 'Create File'
* Type 'test.py' as your filename
* Click 'OK' to create the file
* Highlight the 'test.py' file and select 'Change Permissions'
* Add a checkmark to the 'Execute / Search' column for all three rows (Owner / Group / Others)
* Click the 'Save' button
* Make sure 'rwx r-x r-x' ('755') is displayed under the Permissions column
* Highlight 'test.py' and select 'Edit in Text Editor'
* Leave 'UTF-8' as the encoding, set 'Line break type' to 'Convert to Unix style' and copy/paste the below into the large text field:

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

print("Content-Type: text/html\n\n")

print("Heliohost rules!")
</pre>

* Click the 'Save' button
* Highlight the 'test.py' file and select 'Open in Browser' (Or manually navigate to: '<your subdomain>.helioho.st/cgi-bin/test.py')

If everything worked, you should see 'HelioHost rules!' displayed in your browser.

== Code Explanation ==

In the code pasted in, the first line is called the 'shebang'. It tells the server which version of Python to use.

The second line of code is the 'Content-Type' header. This is important so the server knows what to do with the output that follows. If you forget it, your script will give you an error. The 'Content-Type' header always has to have the two end lines immediately after it. That's what the two '\n' are.

== Troubleshooting ==

If you don't see the module you need, your script will probably give you an error when you try to import the missing module. You can [[View_Error_Logs|view your account error logs]] for details on which module is missing and causing the error.

== Request Additional Python Modules ==

{{Caution|
Before requesting additional modules, make sure you check the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and you do not need to request it.

Please do not request modules that are already installed.}}

'''After you have checked''' the [[:Python_Tutorial#Python_Versions_Available|list of modules already installed]] on your server, if there is another module you'd like to request, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum]. Make sure you provide ALL the details below:
# Confirm that you already checked the list of modules already installed on your server for the version of Python you're using.
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== Running Python scripts outside cgi-bin folder ==

Executing a CGI script outside the 'cgi-bin' folder is possible with some modifications.

== Steps ==

* Go to '/home/<your username>/httpdocs'. (If you were transferred from the old cPanel, the folder will be called 'public_html')
* Create a file named '.htaccess' and copy/paste the below in:

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

The first two lines make '.py' files executable outside 'cgi-bin', and the last line makes the filename 'index.py' show up if someone goes to your domain without having to type out the filename like 'domain.helioho.st/index.py'. This also supports other CGI file extensions.

== 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.

Flask

2026-03-17T22:53:45Z

KazVee: Fix accidental reference to Django, since this is the Flask page

== 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. 
<a href="/flasktest/python/version/">Python version</a> 
<a href="/flasktest/flask/version/">Flask version</a>

"""

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

@app.route("/flask/version/")
def f_version():
return "Flask version %s <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 Flask 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]]

WordPress

2026-01-10T23:52:31Z

KazVee: Add Pelican to the list of WP alternatives

== 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.
* '''Pelican''' is a static site generator powered by Python.

=== 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.

FAQ

2026-01-06T03:03:00Z

KazVee: Add login link to the 'How do I change the contact email address on my account?' FAQ

== FAQ / Frequently Asked Questions ==

== ETA for New Features, Version Upgrades, and Server Repairs ==

{{Info|For information on ETAs for new features, software version upgrades, or server fixes, please review our [[:ETA|ETA]] page.}}

== Where do I ask for help? ==

Wherever you prefer to ask for help, please ask your question '''in one place only'''. HelioHost is run by volunteers who contribute their free time, and some are more active on certain platforms than others. Posting the same question across multiple platforms (like Discord, the HelioNet Forum, or email) or creating duplicate requests on the same platform for the same issue can result in unnecessary duplication of volunteer effort and delay responses to you, as well as to others who need help.

We recommend using the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] for support questions. If you later decide to ask on Discord for live help, please update your forum thread to let us know your issue has been resolved or moved elsewhere.

== How does community-powered support work? ==

HelioHost is a non-profit run entirely by volunteers. All support staff are volunteers who donate their free time to help others. In many cases, other users will also step in to offer support, simply because they want to give back to our community. Every staff member started out as a regular user who appreciated the project and began helping others with their questions and issues.

All support requests in the [https://helionet.org/ HelioNet Forum] are public, since this is the most efficient way for users to get help from the entire HelioHost community. This community-powered support model ensures that solutions are searchable and reusable by any other users who face similar issues in the future. Without public support, we wouldn’t attract new volunteers, and support would likely disappear altogether.

We do not currently offer private support, and do not consider the following items to be private information:
* [[:Signing_Up#Usernames_are_not_private | Usernames]]
* Domain names
* IP addresses
* [[#Providing_PayPal_Transaction_ID | PayPal Transaction IDs]]

If you choose to request support, you may be asked to provide some or all of the above details to assist with the resolution of your request.

If you do not wish to provide this information publicly, you could instead choose to use [https://wiki.helionet.org/ this Wiki] or the [https://helionet.org/ HelioNet Forum] as a completely self-serve option to try to resolve your queries yourself, without assistance or support from our community.

Requests to remove non-private information from forum posts are handled at the sole discretion of staff. In some cases, staff may choose to prioritize helping users with technical issues instead. Resolving actual problems can feel more meaningful and rewarding for volunteers than editing out public information from a public post on a public forum on the internet.

Requests to remove non-private information from public forum posts may eventually be considered under a [[#Can_I_get_Private_Support? | paid donation-only private support model]], where in exchange for a donation a staff member will remove public information from a public support post.

== Can I PM an administrator for help? ==

No, do not PM the administrators expecting support unless we explicitly tell you to. Please use the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] instead. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', and '''server name''' along with any requests. If you are sending your support request via email to 'support@heliohost.org', make sure to contact us '''from the same email address as your hosting account'''.

== Can I get Private Support? ==

There is currently no option for private support of any kind. Some users have expressed concerns about privacy, so we’re planning to offer a private support option for donors only, but there is [[:ETA|no ETA]] on when this may be implemented.

Eventually, for users who do not want their requests and the responses to them made public, where hundreds of community members might otherwise be able to help, private support requests will only be visible to staff. Then, if one of the handful of volunteer staff members has some spare time outside of their jobs, studies, and personal lives, they could pick up a donor-only paid support request.

Since a private support model for donors only will tie up an admin's time and prevent everyone else within the wider user community from helping out, it will likely be even slower than the existing community-powered model, with [[:ETA|no ETAs]] for private support requests from donors.

== Your homepage says "Professional-Grade Hosting", but your support sucks / isn't helping me / is run by a number of volunteers, what gives?‌ ==

There is a difference between "Professional-Grade Hosting" and "Professional-Grade Customer Support". Most people are used to having dedicated customer support staff that will answer every little question; this comes standard with paid hosting. However, we don't do that here. Among the five of us, we have the collective knowledge and technical expertise of any other support staff, but in order for us to help you, we expect from you a certain competency. You must try to spell and use grammar correctly (to the best of your ability). You must provide necessary information (e.g. '''username''' and '''domain name'''). You must be able to read instructions, and you must be able to follow instructions. We will treat you with respect and professionalism if you follow these guidelines. We will probably be very annoyed if u tyep liek dis.‌

== Can I get a free VPS? ==

HelioHost does not offer free VPS. {{Template:VPSInfo}}

What HelioHost offers for free is '''[[#Can_I_have_more_than_one_account?|1 account per person]]''' on our shared web hosting server, [[:Johnny]]. Check out our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny | list of helpful tips for getting a free account on Johnny]] if you would like to sign up.

== I log in frequently but am still receiving inactivity emails, what gives? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], to ensure that your logins are logged, log in to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review the [[:Suspension_Policy#Inactivity_Policy|Inactivity Policy]] section of our [[:Suspension_Policy|Suspension Policy]].

== Why must all posts on HelioNet be in English? ==

The support staff is fluent and reliable only in English.

== Why does HelioHost crash? ==

Sometimes users will abuse server resources and cause the server to crash. We try to fix this as quickly as we can. Since the servers and Plesk are handling such a high volume of users, errors are bound to come up. We also try to fix these ASAP. Also, when [[:Ashoat|djbob]] works on the server, he occasionally screws up, which also causes crashes.

== Why was my account suspended? ==

Our [[:Suspension_Policy|Suspension Policy]] provides comprehensive details on why we will suspend accounts.

A few common reasons for account suspensions are:

* [[:Terms|Terms of Service]] violation(s).
* [[:Suspension_Policy#Inactivity_Policy|Account Inactivity]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Renew your account [http://heliohost.org/renew/ here].
* [[:Suspension_Policy#Duplicate_Accounts|Duplicate Accounts]] on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers. The limit is '''1 account per human being'''.
** Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.
* Exceeding the [[:Suspension_Policy#Account_Storage_Limits|Account Storage limits]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We offer 1000 MB of free web space and optional one-time paid donation options for [[:Donations_for_Increased_Storage|increased account storage]] {{Template:VPSInfo}}
** Our [[:Morty|Morty]] server also offers 1000 MB of free web space. If you exceed this limit, instead of suspending your account, we will charge you for the overages.
* Exceeding the [[:Suspension_Policy#High_Server_Usage|High Server Usage]] limits on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We enforce a memory limit of no more than {{Template:MemoryLimit}} and a limit of {{Template:CPULimit}} per day. You can monitor your load numbers on [https://heliohost.org/dashboard/load/ the load page within your dashboard].
** Our [[:Morty|Morty]] server also has a memory limit of no more than {{Template:MemoryLimit}} and limit of {{Template:CPULimit}} per day. If you exceed these limits, instead of suspending your account, we will charge you for the overages.

It is also possible that this was an error in our system. If you suspect that this is the case, report the error in a new post [https://helionet.org/index/forum/81-suspended-and-queued-accounts/ here], making sure to provide your '''username'''.

== Why does my new subdomain show a "Queued" page? ==

{{Info|All domain and subdomain changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

During the first 2 hours, seeing the queued page is normal and only means the change hasn't taken effect yet. If it's been longer than '''a full 2 hours''', try [[:Clear_Your_Cache|clearing your browser cache]].

== Why can't I log in? ==

{{Info|If you just registered, please wait '''up to 2 hours''' for your Plesk account to become fully active.}}

If it has been longer than '''a full 2 hours''' since you registered and you still see an 'Account Queued' page, try [[:Clear_Your_Cache|clearing your browser cache]]. If you are still experiencing problems, make sure you are entering your username in all lowercase letters, i.e. "wizard", not "Wizard" or "WIZARD".

== How do I keep my account active / prevent being suspended? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], login to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review our [[:Suspension_Policy|Inactivity Policy]].

On our scaling hosting server, [[:Morty|Morty]], as long as there is a positive balance on your account, it will remain active without needing to log in.

== What is a Daily Signup Limit and why is it stopping me from registering? ==

Each server has a daily limit for sign-ups so that it doesn't crash from all the people wanting to use HelioHost. Free signups on Johnny now reset [https://helionet.org/index/topic/59660-midnight-and-noon/ every 12 hours] at midnight UTC and noon 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]].

== What if I have at least $2 USD and don't want to wait to sign up? ==

For a one-time donation of as little as $2 USD, you can open an account on our [[:Tommy|Tommy]] server any time of day. We offer various [https://heliohost.org/tommy/ Donor Plans], enabling you to sign up anytime with your donation via Credit card, Debit card, or PayPal.

If you prefer to donate Crypto to get a Tommy account, visit the [https://heliohost.org/donate/ Donate] page to view our Cryptocurrency wallets. Make sure that after transaction fees/gas the donation amount is $2 USD or more. After making the donation, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] so the transaction can be verified. Make sure you let us know the currency, amount, time of the transaction, and the email address you want the Tommy invite sent to. Please be aware that crypto donations can take time to verify. In the case of XMR and AEON, these can take several days to verify and are not recommended.

Users on our Tommy donor server and the free Johnny server are [[:Suspension_Policy#Inactivity Policy|required to log in at least once a month]] to keep their accounts active.

== What other options are available if I want to sign up right away? ==

For users who prefer not to have to log in regularly, our [[:Morty|Morty]] scaling server has no login requirement as long as there is a positive balance on your account.

{{Template:VPSInfo}}

== My account was deleted. Can I get my data back? ==

No. We do not keep backups of your data nor is it our responsibility to, as mentioned in our [[:Terms|Terms of Service]]. You must backup your own data regularly and download the backup to your local machine.

If you're not sure how to backup your data, please see our [[:Account_Backups|Account Backups tutorial]] page. It contains guidance on creating manual backups to download to your local machine, and instructions for setting up scheduled automated backups within Plesk.

== Can I have more than one account? ==

The first line of our [[:Terms | Terms of Service]] confirms that the limit is '''[[:Suspension_Policy#Duplicate_Accounts |1 account per human being]]''' on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers, even if you use different email addresses.

=== Multiple Accounts Allowed on Morty ===

Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.

== How do I reset my hosting account to start fresh? ==

{{Danger|Before requesting an account reset, make sure that the email address on your account is not hosted on HelioHost or else '''you will not be able to receive the invite email to recreate your account''' after it is wiped.

To check which email address is associated with your hosting account, go to: '''Plesk > Account > My Profile > General > External email address'''}}

=== Admin Account Reset Limits ===

{{Info|Due to certain users abusing our generosity in the past and requesting 5 or so resets in less than a week, we now limit each account to '''1 free reset per week''' done by an admin, with the option to [[#Purchasing_Additional_Account_Resets|donate for additional account resets if needed.]]}}

=== Free Self-Serve Account Resets (with Account Delete/Account Recreate) ===

We will eventually be adding the ability for users to reset their accounts automatically, without the need for admin assistance. However, there is [[:ETA|no estimated timeframe for this]], since there are many other higher-priority projects to be completed first.

In the meantime, users may delete their account and then recreate it, which effectively resets all account settings and contents, accomplishing the same thing as an account reset does.

Before deleting your account, [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|make a backup]]. Then, to delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button. Please make sure to allow some time for the deletion process to complete.

To recreate your account, try to login. You will be greeted with a 'Welcome back!' message, and prompted to enter your email address to receive an email invite to recreate your old account. Make sure to enter the same email address that was on the account you just deleted. Follow the steps to complete account recreation. You will receive an email confirming the new account has been successfully created.

{{Info|Account creation can take '''up to 2 hours''' because it requires an Apache reset. }}

=== Purchasing Additional Account Resets ===

If you need to purchase an additional account reset, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for account reset]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your account reset request, so the donation can be verified.

'''Note:''' Account resets must be purchased one at a time, and cannot be pre-ordered in bulk.

=== Before Asking an Admin for an Account Reset ===

Because wiping an account is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

Before asking for an account reset, we strongly recommend creating an [[:Account_Backups | account backup]], and '''downloading it to your local machine''' first. Any backups left inside Plesk will be wiped out during the reset.

To request that we reset your account so you can start over, send an email '''from the same email address listed in Plesk as your external email address''' to 'support@heliohost.org' so we can verify your identity and wipe your account. Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your hosting account.

Once your account has been reset, you will receive an email with a link to restart your account. '''You will have 7 days to use the link.''' If you don't use the link to restart your account within 7 days, you will need to signup for a brand new account.

=== Account Resets Disable Webmail ===

If you had webmail on your account, you will need to re-enable it after the reset has been completed. You can do this by going to:

'''Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > click the Save button'''

{{Caution|
Webmail can take '''up to 2 hours''' to become active after enabling it because it requires an Apache restart.
}}

=== Account Resets Remove WSGI Control Access ===

If you had WSGI Control Access on your [[:Morty]] server account for [[:Flask|Flask]] or [[:Django|Django]] and you want this re-enabled after the 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.

=== Account Resets Remove Addon Domains ===

If you had [[:Addon_Domains | additional domains]] on your account, you will need to re-request them after the reset has been completed.

== VPS Rebuilds ==

Due to certain users abusing our generosity in the past and requesting 50 or so rebuilds in less than a month, we now limit each VPS to '''1 free rebuild per month''' with the option to [[#Purchasing_Additional_VPS_Rebuilds | donate for additional VPS rebuilds]] if needed.

=== How do I request a VPS rebuild? ===

Because rebuilding a VPS is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

To request that we rebuild your VPS, send an email '''from the same email address as your VPS account''' to 'support@heliohost.org' so we can verify your identity and rebuild your VPS. If you would like a free dashboard (Hestia, KeyHelp, etc.) installed after the rebuild, please include this in the request.

Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your VPS account. If you're not sure what email address is associated with your VPS account, you can check by logging into the [https://heliohost.org/login/ VPS Dashboard] with your VPS Username and Password. The email address attached to your VPS account will be displayed at the top right of the page.

=== Purchasing Additional VPS Rebuilds ===

If you need to purchase an additional VPS rebuild, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for VPS Rebuild]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your VPS rebuild request, so the donation can be verified.

== 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].

== How do I change the contact email address on my account? ==

We recommend using a reliable external email address for your contact address because if you lose access to your HelioHost account, the contact email is the only way you have of recovering your account. If that email is hosted by us, you likely won't be able to access it either.

To change the email address on your account, go to: '''[https://heliohost.org/login/ Login] > Plesk > Account > My Profile > General > External email address'''

When you change your email address it may take '''up to 2 hours''' to sync to the main website. In the meantime, login with your username (not email) on the main [https://heliohost.org/ heliohost.org] website. After a couple hours you should be able to login with either your username or your new external email address.

== How do I delete my hosting account? ==

To delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button.

To delete your HelioNet Forum account, post a topic in the [https://helionet.org/index/forum/4-contact-helionet/?do=add Contact HelioNet forum].

== How do I change my main domain? ==

To change the main domain on your HelioHost Plesk account, 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 domain name''' you want as your main domain, '''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.)

{{Caution|There is a risk of data loss when main domains are changed. We strongly recommend you [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|create an account backup]] and '''download the backup to your local machine''' before requesting a main domain change. As mentioned in our [[:Terms|Terms of Service]], it is not HelioHost's responsibility to keep backups of your data.}}

As an alternative to changing your main domain, consider using [[:Parked_(Alias)_Domains|Parked (Alias)]], [[:Addon_Domains|Addon]], and/or [[:Subdomains|Subdomains]].

== What are the nameservers for HelioHost? ==

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

== What IP addresses should I add to my DNS? ==

To add A (IPv4) or AAAA (IPv6) records to your domain registrar's dashboard, follow these steps to view the IP addresses for your server:

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

== The server is slow / Feature XYZ doesn't work / Something's wrong with my account / etc. ==

Please post the issue in the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] and we will try to solve the problem. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', '''server name''', and any '''error messages''' you are encountering.

== Can Feature XYZ be installed? ==

Softaculous [https://helionet.org/index/topic/59683-softaculous-has-returned/ returned in March 2024] and is offered on our [[:Morty|Morty]], [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, making it possible to install the latest version of 459 different software packages with just a single click.

To browse the available options, login to Plesk and select Softaculous from the menu:

[[File:softaculous_menu_item.png]]

If you need a system-wide feature installed, please post a request in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and any applicable '''version numbers'''.

== Can I use SSH? ==

On hosting accounts, secure shell access (SSH) is disabled for security reasons.

However, it is possible to run jailed shell commands using Plesk's [[:Cron_Jobs|Scheduled Tasks (cron jobs)]] feature.

In many cases, SSH is not actually necessary. Please post a request in our our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''the command you want to run''', and we'll be happy to investigate other ways to accomplish the same task without SSH.

If you absolutely require SSH access, you will need a VPS. {{Template:VPSInfo}}

== Can I use proc_open(), exec(), popen(), etc.? ==

These functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

== Can I use Docker / Podman / Containers, etc? ==
Container technologies are not supported on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]), and there are no plans to support containerization on our shared hosting servers in the future.

If you would like to use Docker or other container technologies, you will need a VPS. {{Template:VPSInfo}}

== Does HelioHost support sockets? Which ports are open? ==

Our [[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]] servers have zero inbound ports available to be opened. All ports that are currently open already have services listening, such as 80 http, 443 https, 3306 MariaDB, and 5432 PostgreSQL.

Outbound ports are similar: ports like 80, 443, 3306, 5432, 25, 465, etc., are open to allow scripts to connect to common services on remote servers.

If you can proxy your websocket through Apache or Nginx, it can work without opening a port:
* You could use an '.htaccess' file to proxy the websocket connection through Apache.
* With the help of a root admin, you could get an Nginx proxy set up. To explore this option, please post a request in our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''details about your websocket application''', and we'll be happy to help.

If you absolutely need a port opened, you'll need to get a VPS, and you will then have all 65535 ports available to open or close as you want. {{Template:VPSInfo}}

== Are directory indexes enabled? ==

Yes. Directory indexes have been enabled by default on the shared hosting servers since late 2024. This is a feature many users have requested over the past few years, but if you don't want directory listings for a folder, simply create an empty 'index.html' file inside it. Please check our [[:Create_Website#Directory_Index | Directory Index]] section for further information.

== Can I change my document root directory? ==

Typically, your domain root directory is 'httpdocs' (or 'public_html' if you were transferred from the old cPanel). Users cannot change the document root themselves inside Plesk.

If you're planning on using Laravel, you can set the document root yourself by using the [[:Laravel#Document_Root | Laravel Toolkit]].

If you have a legitimate reason for needing the document root changed, please create a post in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and make sure to provide your '''username''', '''domain name''', '''server name''', '''the new document root directory you want''', and a '''valid reason''' explaining why you are unable to use your existing document root. The admins will review your request to determine if the change can be made.

== I can login to Plesk, but can't login to SFTP, what do I do? ==

Sometimes the SFTP and Plesk passwords get out of sync. Please try changing the SFTP password by following these steps:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Connection Info > System user credentials > Click the 'edit icon' next to password'''

== How do I stop my Node.js app? ==

Node tutorials found elsewhere on the internet probably assume you have a VPS (not shared hosting) and you'll quickly get suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]].

If you need to stop a Node process that is already running, deleting the Node.js files via the file manager will '''not''' stop already running processes.

To stop an already running Node.js process, you should disable Node by following the steps below:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Get Started > Node.js > Disable Node.js'''

If you follow our [[:Node.js|Node.js guide]], it will use Passenger which automatically stops Node.js processes if your website isn't getting any visitors. This will help try to keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]].

If you do not want to use Passenger, we recommend you upgrade to a VPS. {{Template:VPSInfo}}

== Can I use your services to mine cryptocurrency? ==

No. We do not allow mining on any of our plans (free or paid).

== Your hosting SUCKS! So do YOU!!! ==

Please see [http://helionet.org/index/topic/4723-suspended/page__p__46231#entry46231 this].

== I still have a question about HelioHost. ==

Post in the [https://helionet.org/index/forum/48-questions/ Questions forum] and we'll try to help you the best we can.

Uploading Files

2026-01-04T16:05:51Z

KazVee: Add subsection about Creating an FTP User

== Uploading Files ==

== FTP / SFTP ==

Just one of the ways to upload and modify your website is through [http://en.wikipedia.org/wiki/FTP FTP (File Transfer Protocol)], which allows you to connect to your site and perform various file operations directly from your computer.

Once connected, you can perform the appropriate actions just as you would with any other file/folder on your computer. Simply drag and drop or copy and paste files to upload them. Right click on a file/folder to perform a variety of actions such as Rename, Delete, and Create Directory.

To connect to your site's FTP server, you will need to use an FTP Client, such as [http://filezilla-project.org/ FileZilla], which is completely free software used by millions across the world. The various settings you will need to connect to the servers are provided in the table below.

If you are having problems connecting to the FTP service, then it might be a temporary failure with the service due to high server load. You can retrieve real-time statistics on server load (including FTP service) at [https://status.heliohost.org/ status.heliohost.org].

{| class="wikitable" style="margin:auto"
|-
! Parameter !! Morty!! Tommy !! Johnny
|-
| Host || morty.heliohost.org || tommy.heliohost.org || johnny.heliohost.org
|-
| Port || 1373 || 1373 || 1373
|-
| Protocol || SFTP - SSH File Transfer Protocol || SFTP - SSH File Transfer Protocol || SFTP - SSH File Transfer Protocol
|-
| Logon Type || Normal || Normal || Normal
|-
| User || Your Plesk username || Your Plesk username || Your Plesk username
|-
| Password || Your Plesk password || Your Plesk password || Your Plesk password
|}

=== Creating an FTP User ===

If you prefer to create an FTP user account instead of using your Plesk account credentials, you can do this inside Plesk.

Navigate to: '''Login > Plesk > Websites & Domains > Hosting & DNS > Hosting Settings > Webspace settings > System user's credentials''' and set a username and password for your FTP user.

== FileZilla ==

== Step-by-step: Connect to your server with SFTP using FileZilla ==

# Click 'File → Site Manager'
# Click 'New Site'
# Name it something like 'Johnny SFTP' and press enter
# Enter settings from the table above
# Click 'Connect'
# Approve the remote server key, and check the box to not ask you about this server again.

{{Info|
You can manage your files with SFTP, or FTPS (on Port 21).
We recommend not using FTP because it is insecure, but it's available too.
}}

== Plesk File Manager ==

The Plesk online file manager is a great built-in facility available to all users as part of HelioHost. It has all the features you could need to manage the files for your website, even the invisible and hidden ones. Follow the navigation steps below to access the Plesk file manager:

'''Login > Plesk > Websites & Domains > [ domain ] > Files'''

{{Caution|Do not bookmark your Plesk File Manager page, as it is not a supported login method and your visits will not be recorded. On the [[:Johnny|Johnny]] and [[:Tommy|Tommy]] servers, this means you risk being [[:Suspension_Policy#Inactivity_Policy|suspended for inactivity]] after 30 days.}}

== Net2FTP ==

Net2FTP is a popular online file manager which can be installed using [[:Softaculous|Softaculous]], the auto-installer service built right into Plesk. Follow the navigation steps below to install Net2FTP:

'''Login > Plesk > Softaculous > search for 'net2ftp' or find it under the list of 'File Management' options'''

== Pydio ==

Pydio, formerly known as AjaXplorer, is another online file manager which includes file editors, multiple users, and more. Pydio can be installed using [[:Softaculous|Softaculous]], the auto-installer service built right into Plesk. Follow the navigation steps below to install Pydio:

'''Login > Plesk > Softaculous > search for 'Pydio' or find it under the list of 'File Management' options'''

== WebDAV ==

WebDAV / Web Disk / File Sharing has been [https://docs.plesk.com/release-notes/obsidian/deprecation-plan/ deprecated in Plesk], however SFTP is a much better choice anyway.

== Troubleshooting ==

If you can login to Plesk, but cannot login to SFTP, this can sometimes happen if the SFTP and Plesk passwords get out of sync. Please try changing the SFTP password by following these steps:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Connection Info > System user credentials > Click the 'edit icon' next to password'''

FAQ

2026-01-03T01:08:26Z

KazVee: Add FAQ about Docker/Podman/Containers support

== FAQ / Frequently Asked Questions ==

== ETA for New Features, Version Upgrades, and Server Repairs ==

{{Info|For information on ETAs for new features, software version upgrades, or server fixes, please review our [[:ETA|ETA]] page.}}

== Where do I ask for help? ==

Wherever you prefer to ask for help, please ask your question '''in one place only'''. HelioHost is run by volunteers who contribute their free time, and some are more active on certain platforms than others. Posting the same question across multiple platforms (like Discord, the HelioNet Forum, or email) or creating duplicate requests on the same platform for the same issue can result in unnecessary duplication of volunteer effort and delay responses to you, as well as to others who need help.

We recommend using the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] for support questions. If you later decide to ask on Discord for live help, please update your forum thread to let us know your issue has been resolved or moved elsewhere.

== How does community-powered support work? ==

HelioHost is a non-profit run entirely by volunteers. All support staff are volunteers who donate their free time to help others. In many cases, other users will also step in to offer support, simply because they want to give back to our community. Every staff member started out as a regular user who appreciated the project and began helping others with their questions and issues.

All support requests in the [https://helionet.org/ HelioNet Forum] are public, since this is the most efficient way for users to get help from the entire HelioHost community. This community-powered support model ensures that solutions are searchable and reusable by any other users who face similar issues in the future. Without public support, we wouldn’t attract new volunteers, and support would likely disappear altogether.

We do not currently offer private support, and do not consider the following items to be private information:
* [[:Signing_Up#Usernames_are_not_private | Usernames]]
* Domain names
* IP addresses
* [[#Providing_PayPal_Transaction_ID | PayPal Transaction IDs]]

If you choose to request support, you may be asked to provide some or all of the above details to assist with the resolution of your request.

If you do not wish to provide this information publicly, you could instead choose to use [https://wiki.helionet.org/ this Wiki] or the [https://helionet.org/ HelioNet Forum] as a completely self-serve option to try to resolve your queries yourself, without assistance or support from our community.

Requests to remove non-private information from forum posts are handled at the sole discretion of staff. In some cases, staff may choose to prioritize helping users with technical issues instead. Resolving actual problems can feel more meaningful and rewarding for volunteers than editing out public information from a public post on a public forum on the internet.

Requests to remove non-private information from public forum posts may eventually be considered under a [[#Can_I_get_Private_Support? | paid donation-only private support model]], where in exchange for a donation a staff member will remove public information from a public support post.

== Can I PM an administrator for help? ==

No, do not PM the administrators expecting support unless we explicitly tell you to. Please use the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] instead. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', and '''server name''' along with any requests. If you are sending your support request via email to 'support@heliohost.org', make sure to contact us '''from the same email address as your hosting account'''.

== Can I get Private Support? ==

There is currently no option for private support of any kind. Some users have expressed concerns about privacy, so we’re planning to offer a private support option for donors only, but there is [[:ETA|no ETA]] on when this may be implemented.

Eventually, for users who do not want their requests and the responses to them made public, where hundreds of community members might otherwise be able to help, private support requests will only be visible to staff. Then, if one of the handful of volunteer staff members has some spare time outside of their jobs, studies, and personal lives, they could pick up a donor-only paid support request.

Since a private support model for donors only will tie up an admin's time and prevent everyone else within the wider user community from helping out, it will likely be even slower than the existing community-powered model, with [[:ETA|no ETAs]] for private support requests from donors.

== Your homepage says "Professional-Grade Hosting", but your support sucks / isn't helping me / is run by a number of volunteers, what gives?‌ ==

There is a difference between "Professional-Grade Hosting" and "Professional-Grade Customer Support". Most people are used to having dedicated customer support staff that will answer every little question; this comes standard with paid hosting. However, we don't do that here. Among the five of us, we have the collective knowledge and technical expertise of any other support staff, but in order for us to help you, we expect from you a certain competency. You must try to spell and use grammar correctly (to the best of your ability). You must provide necessary information (e.g. '''username''' and '''domain name'''). You must be able to read instructions, and you must be able to follow instructions. We will treat you with respect and professionalism if you follow these guidelines. We will probably be very annoyed if u tyep liek dis.‌

== Can I get a free VPS? ==

HelioHost does not offer free VPS. {{Template:VPSInfo}}

What HelioHost offers for free is '''[[#Can_I_have_more_than_one_account?|1 account per person]]''' on our shared web hosting server, [[:Johnny]]. Check out our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny | list of helpful tips for getting a free account on Johnny]] if you would like to sign up.

== I log in frequently but am still receiving inactivity emails, what gives? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], to ensure that your logins are logged, log in to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review the [[:Suspension_Policy#Inactivity_Policy|Inactivity Policy]] section of our [[:Suspension_Policy|Suspension Policy]].

== Why must all posts on HelioNet be in English? ==

The support staff is fluent and reliable only in English.

== Why does HelioHost crash? ==

Sometimes users will abuse server resources and cause the server to crash. We try to fix this as quickly as we can. Since the servers and Plesk are handling such a high volume of users, errors are bound to come up. We also try to fix these ASAP. Also, when [[:Ashoat|djbob]] works on the server, he occasionally screws up, which also causes crashes.

== Why was my account suspended? ==

Our [[:Suspension_Policy|Suspension Policy]] provides comprehensive details on why we will suspend accounts.

A few common reasons for account suspensions are:

* [[:Terms|Terms of Service]] violation(s).
* [[:Suspension_Policy#Inactivity_Policy|Account Inactivity]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Renew your account [http://heliohost.org/renew/ here].
* [[:Suspension_Policy#Duplicate_Accounts|Duplicate Accounts]] on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers. The limit is '''1 account per human being'''.
** Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.
* Exceeding the [[:Suspension_Policy#Account_Storage_Limits|Account Storage limits]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We offer 1000 MB of free web space and optional one-time paid donation options for [[:Donations_for_Increased_Storage|increased account storage]] {{Template:VPSInfo}}
** Our [[:Morty|Morty]] server also offers 1000 MB of free web space. If you exceed this limit, instead of suspending your account, we will charge you for the overages.
* Exceeding the [[:Suspension_Policy#High_Server_Usage|High Server Usage]] limits on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We enforce a memory limit of no more than {{Template:MemoryLimit}} and a limit of {{Template:CPULimit}} per day. You can monitor your load numbers on [https://heliohost.org/dashboard/load/ the load page within your dashboard].
** Our [[:Morty|Morty]] server also has a memory limit of no more than {{Template:MemoryLimit}} and limit of {{Template:CPULimit}} per day. If you exceed these limits, instead of suspending your account, we will charge you for the overages.

It is also possible that this was an error in our system. If you suspect that this is the case, report the error in a new post [https://helionet.org/index/forum/81-suspended-and-queued-accounts/ here], making sure to provide your '''username'''.

== Why does my new subdomain show a "Queued" page? ==

{{Info|All domain and subdomain changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

During the first 2 hours, seeing the queued page is normal and only means the change hasn't taken effect yet. If it's been longer than '''a full 2 hours''', try [[:Clear_Your_Cache|clearing your browser cache]].

== Why can't I log in? ==

{{Info|If you just registered, please wait '''up to 2 hours''' for your Plesk account to become fully active.}}

If it has been longer than '''a full 2 hours''' since you registered and you still see an 'Account Queued' page, try [[:Clear_Your_Cache|clearing your browser cache]]. If you are still experiencing problems, make sure you are entering your username in all lowercase letters, i.e. "wizard", not "Wizard" or "WIZARD".

== How do I keep my account active / prevent being suspended? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], login to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review our [[:Suspension_Policy|Inactivity Policy]].

On our scaling hosting server, [[:Morty|Morty]], as long as there is a positive balance on your account, it will remain active without needing to log in.

== What is a Daily Signup Limit and why is it stopping me from registering? ==

Each server has a daily limit for sign-ups so that it doesn't crash from all the people wanting to use HelioHost. Free signups on Johnny now reset [https://helionet.org/index/topic/59660-midnight-and-noon/ every 12 hours] at midnight UTC and noon 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]].

== What if I have at least $2 USD and don't want to wait to sign up? ==

For a one-time donation of as little as $2 USD, you can open an account on our [[:Tommy|Tommy]] server any time of day. We offer various [https://heliohost.org/tommy/ Donor Plans], enabling you to sign up anytime with your donation via Credit card, Debit card, or PayPal.

If you prefer to donate Crypto to get a Tommy account, visit the [https://heliohost.org/donate/ Donate] page to view our Cryptocurrency wallets. Make sure that after transaction fees/gas the donation amount is $2 USD or more. After making the donation, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] so the transaction can be verified. Make sure you let us know the currency, amount, time of the transaction, and the email address you want the Tommy invite sent to. Please be aware that crypto donations can take time to verify. In the case of XMR and AEON, these can take several days to verify and are not recommended.

Users on our Tommy donor server and the free Johnny server are [[:Suspension_Policy#Inactivity Policy|required to log in at least once a month]] to keep their accounts active.

== What other options are available if I want to sign up right away? ==

For users who prefer not to have to log in regularly, our [[:Morty|Morty]] scaling server has no login requirement as long as there is a positive balance on your account.

{{Template:VPSInfo}}

== My account was deleted. Can I get my data back? ==

No. We do not keep backups of your data nor is it our responsibility to, as mentioned in our [[:Terms|Terms of Service]]. You must backup your own data regularly and download the backup to your local machine.

If you're not sure how to backup your data, please see our [[:Account_Backups|Account Backups tutorial]] page. It contains guidance on creating manual backups to download to your local machine, and instructions for setting up scheduled automated backups within Plesk.

== Can I have more than one account? ==

The first line of our [[:Terms | Terms of Service]] confirms that the limit is '''[[:Suspension_Policy#Duplicate_Accounts |1 account per human being]]''' on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers, even if you use different email addresses.

=== Multiple Accounts Allowed on Morty ===

Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.

== How do I reset my hosting account to start fresh? ==

{{Danger|Before requesting an account reset, make sure that the email address on your account is not hosted on HelioHost or else '''you will not be able to receive the invite email to recreate your account''' after it is wiped.

To check which email address is associated with your hosting account, go to: '''Plesk > Account > My Profile > General > External email address'''}}

=== Admin Account Reset Limits ===

{{Info|Due to certain users abusing our generosity in the past and requesting 5 or so resets in less than a week, we now limit each account to '''1 free reset per week''' done by an admin, with the option to [[#Purchasing_Additional_Account_Resets|donate for additional account resets if needed.]]}}

=== Free Self-Serve Account Resets (with Account Delete/Account Recreate) ===

We will eventually be adding the ability for users to reset their accounts automatically, without the need for admin assistance. However, there is [[:ETA|no estimated timeframe for this]], since there are many other higher-priority projects to be completed first.

In the meantime, users may delete their account and then recreate it, which effectively resets all account settings and contents, accomplishing the same thing as an account reset does.

Before deleting your account, [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|make a backup]]. Then, to delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button. Please make sure to allow some time for the deletion process to complete.

To recreate your account, try to login. You will be greeted with a 'Welcome back!' message, and prompted to enter your email address to receive an email invite to recreate your old account. Make sure to enter the same email address that was on the account you just deleted. Follow the steps to complete account recreation. You will receive an email confirming the new account has been successfully created.

{{Info|Account creation can take '''up to 2 hours''' because it requires an Apache reset. }}

=== Purchasing Additional Account Resets ===

If you need to purchase an additional account reset, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for account reset]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your account reset request, so the donation can be verified.

'''Note:''' Account resets must be purchased one at a time, and cannot be pre-ordered in bulk.

=== Before Asking an Admin for an Account Reset ===

Because wiping an account is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

Before asking for an account reset, we strongly recommend creating an [[:Account_Backups | account backup]], and '''downloading it to your local machine''' first. Any backups left inside Plesk will be wiped out during the reset.

To request that we reset your account so you can start over, send an email '''from the same email address listed in Plesk as your external email address''' to 'support@heliohost.org' so we can verify your identity and wipe your account. Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your hosting account.

Once your account has been reset, you will receive an email with a link to restart your account. '''You will have 7 days to use the link.''' If you don't use the link to restart your account within 7 days, you will need to signup for a brand new account.

=== Account Resets Disable Webmail ===

If you had webmail on your account, you will need to re-enable it after the reset has been completed. You can do this by going to:

'''Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > click the Save button'''

{{Caution|
Webmail can take '''up to 2 hours''' to become active after enabling it because it requires an Apache restart.
}}

=== Account Resets Remove WSGI Control Access ===

If you had WSGI Control Access on your [[:Morty]] server account for [[:Flask|Flask]] or [[:Django|Django]] and you want this re-enabled after the 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.

=== Account Resets Remove Addon Domains ===

If you had [[:Addon_Domains | additional domains]] on your account, you will need to re-request them after the reset has been completed.

== VPS Rebuilds ==

Due to certain users abusing our generosity in the past and requesting 50 or so rebuilds in less than a month, we now limit each VPS to '''1 free rebuild per month''' with the option to [[#Purchasing_Additional_VPS_Rebuilds | donate for additional VPS rebuilds]] if needed.

=== How do I request a VPS rebuild? ===

Because rebuilding a VPS is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

To request that we rebuild your VPS, send an email '''from the same email address as your VPS account''' to 'support@heliohost.org' so we can verify your identity and rebuild your VPS. If you would like a free dashboard (Hestia, KeyHelp, etc.) installed after the rebuild, please include this in the request.

Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your VPS account. If you're not sure what email address is associated with your VPS account, you can check by logging into the [https://heliohost.org/login/ VPS Dashboard] with your VPS Username and Password. The email address attached to your VPS account will be displayed at the top right of the page.

=== Purchasing Additional VPS Rebuilds ===

If you need to purchase an additional VPS rebuild, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for VPS Rebuild]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your VPS rebuild request, so the donation can be verified.

== 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].

== How do I change the contact email address on my account? ==

We recommend using a reliable external email address for your contact address because if you lose access to your HelioHost account, the contact email is the only way you have of recovering your account. If that email is hosted by us, you likely won't be able to access it either.

To change the email address on your account, login and go to: '''Plesk > Account > My Profile > General > External email address'''

When you change your email address it may take '''up to 2 hours''' to sync to the main website. In the meantime, login with your username (not email) on the main [https://heliohost.org/ heliohost.org] website. After a couple hours you should be able to login with either your username or your new external email address.

== How do I delete my hosting account? ==

To delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button.

To delete your HelioNet Forum account, post a topic in the [https://helionet.org/index/forum/4-contact-helionet/?do=add Contact HelioNet forum].

== How do I change my main domain? ==

To change the main domain on your HelioHost Plesk account, 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 domain name''' you want as your main domain, '''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.)

{{Caution|There is a risk of data loss when main domains are changed. We strongly recommend you [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|create an account backup]] and '''download the backup to your local machine''' before requesting a main domain change. As mentioned in our [[:Terms|Terms of Service]], it is not HelioHost's responsibility to keep backups of your data.}}

As an alternative to changing your main domain, consider using [[:Parked_(Alias)_Domains|Parked (Alias)]], [[:Addon_Domains|Addon]], and/or [[:Subdomains|Subdomains]].

== What are the nameservers for HelioHost? ==

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

== What IP addresses should I add to my DNS? ==

To add A (IPv4) or AAAA (IPv6) records to your domain registrar's dashboard, follow these steps to view the IP addresses for your server:

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

== The server is slow / Feature XYZ doesn't work / Something's wrong with my account / etc. ==

Please post the issue in the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] and we will try to solve the problem. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', '''server name''', and any '''error messages''' you are encountering.

== Can Feature XYZ be installed? ==

Softaculous [https://helionet.org/index/topic/59683-softaculous-has-returned/ returned in March 2024] and is offered on our [[:Morty|Morty]], [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, making it possible to install the latest version of 459 different software packages with just a single click.

To browse the available options, login to Plesk and select Softaculous from the menu:

[[File:softaculous_menu_item.png]]

If you need a system-wide feature installed, please post a request in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and any applicable '''version numbers'''.

== Can I use SSH? ==

On hosting accounts, secure shell access (SSH) is disabled for security reasons.

However, it is possible to run jailed shell commands using Plesk's [[:Cron_Jobs|Scheduled Tasks (cron jobs)]] feature.

In many cases, SSH is not actually necessary. Please post a request in our our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''the command you want to run''', and we'll be happy to investigate other ways to accomplish the same task without SSH.

If you absolutely require SSH access, you will need a VPS. {{Template:VPSInfo}}

== Can I use proc_open(), exec(), popen(), etc.? ==

These functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

== Can I use Docker / Podman / Containers, etc? ==
Container technologies are not supported on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]), and there are no plans to support containerization on our shared hosting servers in the future.

If you would like to use Docker or other container technologies, you will need a VPS. {{Template:VPSInfo}}

== Does HelioHost support sockets? Which ports are open? ==

Our [[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]] servers have zero inbound ports available to be opened. All ports that are currently open already have services listening, such as 80 http, 443 https, 3306 MariaDB, and 5432 PostgreSQL.

Outbound ports are similar: ports like 80, 443, 3306, 5432, 25, 465, etc., are open to allow scripts to connect to common services on remote servers.

If you can proxy your websocket through Apache or Nginx, it can work without opening a port:
* You could use an '.htaccess' file to proxy the websocket connection through Apache.
* With the help of a root admin, you could get an Nginx proxy set up. To explore this option, please post a request in our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''details about your websocket application''', and we'll be happy to help.

If you absolutely need a port opened, you'll need to get a VPS, and you will then have all 65535 ports available to open or close as you want. {{Template:VPSInfo}}

== Are directory indexes enabled? ==

Yes. Directory indexes have been enabled by default on the shared hosting servers since late 2024. This is a feature many users have requested over the past few years, but if you don't want directory listings for a folder, simply create an empty 'index.html' file inside it. Please check our [[:Create_Website#Directory_Index | Directory Index]] section for further information.

== Can I change my document root directory? ==

Typically, your domain root directory is 'httpdocs' (or 'public_html' if you were transferred from the old cPanel). Users cannot change the document root themselves inside Plesk.

If you're planning on using Laravel, you can set the document root yourself by using the [[:Laravel#Document_Root | Laravel Toolkit]].

If you have a legitimate reason for needing the document root changed, please create a post in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and make sure to provide your '''username''', '''domain name''', '''server name''', '''the new document root directory you want''', and a '''valid reason''' explaining why you are unable to use your existing document root. The admins will review your request to determine if the change can be made.

== I can login to Plesk, but can't login to SFTP, what do I do? ==

Sometimes the SFTP and Plesk passwords get out of sync. Please try changing the SFTP password by following these steps:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Connection Info > System user credentials > Click the 'edit icon' next to password'''

== How do I stop my Node.js app? ==

Node tutorials found elsewhere on the internet probably assume you have a VPS (not shared hosting) and you'll quickly get suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]].

If you need to stop a Node process that is already running, deleting the Node.js files via the file manager will '''not''' stop already running processes.

To stop an already running Node.js process, you should disable Node by following the steps below:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Get Started > Node.js > Disable Node.js'''

If you follow our [[:Node.js|Node.js guide]], it will use Passenger which automatically stops Node.js processes if your website isn't getting any visitors. This will help try to keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]].

If you do not want to use Passenger, we recommend you upgrade to a VPS. {{Template:VPSInfo}}

== Can I use your services to mine cryptocurrency? ==

No. We do not allow mining on any of our plans (free or paid).

== Your hosting SUCKS! So do YOU!!! ==

Please see [http://helionet.org/index/topic/4723-suspended/page__p__46231#entry46231 this].

== I still have a question about HelioHost. ==

Post in the [https://helionet.org/index/forum/48-questions/ Questions forum] and we'll try to help you the best we can.

PHP

2025-12-31T14:48:18Z

KazVee: Add PHP 8.5 to Morty server versions available

Unlimited Email Accounts

2025-12-21T15:28:45Z

KazVee: Add additional context on what the 'i' button provides, which was shown in the screenshot but wasn't in the guide as searchable text

== Unlimited Email Accounts ==

HelioHost offers its users email accounts under their domains. This means that if your domain is 'example.com', you can create email accounts such as 'yourname@example.com'. Unlike other free web hosts, HelioHost does not limit the amount of email accounts each domain can host. Since more email accounts do not burden our server, we see no good reason to restrict them.

== Webmail ==

=== Webmail is Disabled by Default ===

Most users don't use webmail, so it is a waste of system resources to have it on by default. If you regularly use Roundcube webmail, you can enable it on your account by going to:

'''Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > click on the Save button'''

{{Caution|
Webmail can take '''up to 2 hours''' to become active after enabling it because it requires an Apache restart.
}}

Any email account you create on HelioHost can be used and managed through a web interface. HelioHost offers multiple webmail software options:

== RoundCube ==

RoundCube comes preinstalled within the [[:Plesk|Plesk]] control panel, and can be accessed by navigating to:

'''Login > Plesk > Mail'''

== AfterLogic ==

AfterLogic (WebMail Lite v8.6.0 and WebMail Pro v8.6.0) can be user-installed inside Plesk, by navigating to:

'''Login > Plesk > Applications > All Available Applications > Collaboration > Email'''

[[File:plesk-install-email-service.png]]

== Mail Services Available with Softaculous ==

Other mail services can be user-installed using [[:Softaculous]].

[[File:softaculous-mails.png]]

== Supported Protocols ==

If you would prefer to use an email application (such as Outlook or Thunderbird) or your phone to read and send email, you can do this with your HelioHost email accounts. We offer compatibility with both the POP3 and IMAP protocols for incoming mail, and employ the standard SMTP protocol for outgoing mail.

For more information on how to set this up, navigate to:

'''Login > Plesk > Mail > Email Addresses > [ your email address ] > Click the 'i' button''' to learn how to set up your email account in a mail client program, such as Microsoft Outlook, Outlook Express, Thunderbird, and Apple Mail.

[[File:plesk-setup-email-on-device.png]]

Click on 'Manual setup'

{{Info|When configuring mail clients, use your account's server name ('morty.heliohost.org', 'tommy.heliohost.org', or 'johnny.heliohost.org') as the SMTP host address instead of your domain.}}

[[File:plesk-setup-email-on-device-2.png]]

== Custom Mail ==

If you wish to use another mail server to handle your domain's email addresses, then HelioHost is the place for you. We allow users to [[:HelioHost_DNS_Records|request configuration of custom MX records]] for their domain, effectively forwarding all email load from HelioHost to a specified mail server.

== SpamAssassin ==

SpamAssassin is the most popular anti-spam solution for Linux systems and has won awards for its excellent performance. HelioHost offers SpamAssassin with all its accounts, allowing all users to prevent spam on their configured email accounts.

== 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 Support forum] and include '''the full report link''', your hosting account '''username''', and your '''domain name''' so we can help you fix any remaining issues.

== Archived Accounts Lose SPF, DKIM, and DMARC Setup ==

{{Caution|If your account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]] gets archived due to prolonged [[:Suspension_Policy#Inactivity_Policy|inactivity]], any SPF, DKIM, and DMARC settings configured on your account will be lost.

After you have reactivated your archived account, you will need to [[#Set_Up_SPF,_DKIM,_and_DMARC_Records|request SPF, DKIM, and DMARC setup]] again.}}

Express

2025-12-21T01:53:29Z

KazVee: Add recommendation to change Application Mode to Development to enable detailed error reporting

== Express.js ==

{{Caution|If you use Node.js, we strongly recommend that you [https://heliohost.org/dashboard/load/ monitor your site load here].

Node apps often require a lot of server resources, and exceeding the account load limits will cause your user account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]] on [[:Tommy|Tommy]] and [[:Johnny|Johnny]], or charged for overages on [[:Morty|Morty]].}}

== About Express.js ==

Express.js is a web application framework for [[:Node.js|Node.js]]. It provides a set of tools and features to build web applications and APIs quickly and easily. Express.js simplifies common tasks like routing, handling HTTP requests and responses, setting up middleware, and managing sessions. It is lightweight and flexible, allowing developers to structure their applications as they see fit. It is commonly used for building RESTful APIs or server-side applications.

== Node.js on Plesk Uses Passenger ==

== What is Passenger? ==

Passenger is a way of running Node.js and other applications that normally require a constantly running background process. Instead of the process always running in the background just waiting for connections, Passenger shuts it down if there are no connections. When someone visits the website, Passenger fires up the Node.js (or Ruby, or whatever language you're using) process. If another person visits the website while the Node.js process is still running, page loads will be very fast. If there are no further page hits for 5 minutes or so, Passenger kills the background process.

== Why Does HelioHost Use Passenger? ==

It doesn't make sense to leave your car running 24/7 in front of your house just in case you need to drive somewhere so it saves you a second to start the engine. This is a massive waste of gas. Likewise, it doesn't make sense to leave Node.js sites running 24/7 just to save a second of load time in case someone needs to view the page. This is a massive waste of memory. At HelioHost, we want to ensure that the server memory is used efficiently so our servers work efficiently for the hundreds of users on our shared hosting platform.

== Will Passenger Slow My Site Down? ==

A recent speed test on HelioHost servers showed that our app [https://gtmetrix.com/reports/node.krydos1.heliohost.org/esvkM1p0/ only took 177ms to load from a cold start]. That's just under 1/5 of a second, roughly the amount of time it takes to blink.

== How Can I Use Passenger? ==

By following the steps in this tutorial, Plesk will automatically use Passenger to run your Node.js application.

== Can I Change the Inactivity Timeout? ==

No, the background process timeout is set to ensure fair resource usage for all our users and cannot be changed. If you need more control over memory management, we recommend you upgrade to a VPS where you can configure your settings. {{Template:VPSInfo}}

== Can I Prevent My Site from Sleeping? ==

Passenger is designed to keep our shared hosting servers running efficiently and help keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]]. Deliberately preventing your site from sleeping is likely to get your account suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]] on our [[:Johnny|Johnny]] and [[:Tommy|Tommy]] servers, and charged for account load overages on our [[:Morty|Morty]] server.

== What If My Users Cannot Wait For My Site To Load? ==

If your application is highly time-sensitive and every millisecond of load time matters, you could upgrade to a VPS. {{Template:VPSInfo}} With a VPS, you won’t share your server with other users, so you can run any continuous process(es) that you want.

== Setup ==

If you prefer visual guidance, we have a [https://www.youtube.com/watch?v==Ak2yI8w-mew&ab_channel==HelioHost video tutorial] available for you to watch.
To follow the written instructions, please continue reading below.

Go into your project root. (If you don't have a project, you can use [https://github.com/HelioNetworks/Node.JS-Example this example project].)

== How to Setup Express.js ==

'''Note:''' If you created an 'index.html' file inside your 'httpdocs' directory, delete it or rename it to something else.

Your Node.js files will go into your user directory ('''NOT''' 'httpdocs'):

[[File:plesk_file_manager.png]]

If you're not using the above example, then create a new file 'app.js' and put this inside:

<pre>
const http = require('http');
const express = require('express');
const port = 3000;

const app = express();

app.get('/', (req, res) => {
res.status(200).send('Node.js is working with Express and http.');
});

// Create an HTTP server using the Express app
const server = http.createServer(app);

server.listen(port, () => {
console.log(`Server running`);
});
</pre>

Create a new file 'package.json' and put this inside:

<pre>
{
"name": "node-test",
"version": "0.0.0",
"private": true,
"scripts": {
"start": "node app.js"
},
"dependencies": {
"cookie-parser": "~1.4.4",
"debug": "~2.6.9",
"express": "~4.16.1",
"http-errors": "~1.6.3",
"morgan": "~1.9.1",
"pug": "^3.0.2"
}
}
</pre>

In Plesk, go to: 'Website & Domains > [domain]'

[[File:nodejs-link.png]]

== Server Setup ==

Upload all your files to your server. Then go to the Node.js section and set the following:

* Node.js Version: we recommend using [[:Node.js#Supported_Versions|the latest available]].
* Application Root: '/' (This is the folder where you uploaded your project.)
* Application Startup File: 'app.js' (The entry point of our app, use the file we created earlier.)
* Here, you're able to configure settings for your application.

{{Info|We strongly recommend you change the '''Application Mode''' to '''Development''' as this will provide you with more detailed error reporting to help with troubleshooting and debugging any issues.}}

[[File:nodejs-settings.png]]

== Starting the Server ==

Once all of the above steps are done, press the 'Enable Node.js' button.

[[File:enableNodeJs.png]]

Then you need to run the 'NPM install' command.

[[File:nodejs-npm-install.png]]

Finally, you will need to wait '''up to 2 hours''' for the server to update.

Node.js application deployment can take '''up to 2 hours''' to go into effect as it requires an Apache restart. After an entire 2 hours, if your Node app is not working for you, please [[:Clear_Your_Cache|clear your web browser cache]].

Once the Node.js application has been deployed, you should be able to visit 'domain.helioho.st' in your web browser and see the text 'Node.js is working with Express and http.'

[[File:nodejs-working-with-express.png]]

== Further Support ==

If it's been more than 2 hours, and the Node.js application still isn't working, please go back and check all of your steps again. If it's been more than a full 2 hours since your changes, and it still isn't working even after you [[:Clear_Your_Cache|clear your web browser cache]], 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 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''', and any '''error message(s)''' encountered.

[[Category:Tutorials]]

Node.js

2025-12-21T01:51:20Z

KazVee: Add recommendation to change Application Mode to Development to enable detailed error reporting

== Node.js Tutorials ==

{{Info|This page features our Node.js tutorial.

We also have tutorials for building [[:Express|Express]] or [[:Next.js|Next.js]] apps with Node.js.}}

== Node.js Server Resource Usage ==

{{Caution|
If you use Node.js, we strongly recommend that you [https://heliohost.org/dashboard/load/ monitor your site load here].

Node apps often require a lot of server resources, and exceeding the account load limits will cause your user account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]] on [[:Tommy|Tommy]] and [[:Johnny|Johnny]], or charged for overages on [[:Morty|Morty]].}}

== Node.js Versions Supported ==

The Node.js versions currently supported on the shared hosting servers are listed below. While we aim to keep Node versions current, please make sure you review our [[:ETA|ETAs for new features]].

{{Info|If you require a different version of Node.js than the options offered below, you'll need to get a VPS. {{Template:VPSInfo}}}}

== Morty server ==
* Node 16
* Node 18
* Node 20
* Node 21
* Node 22
* Node 23

== Tommy server ==
* Node 16
* Node 18
* Node 20
* Node 21
* Node 22
* Node 23

== Johnny server ==
* Node 16
* Node 18
* Node 20
* Node 21
* Node 22
* Node 23

== About Node.js ==

As an asynchronous event-driven JavaScript runtime, Node.js is designed to build scalable network applications. In Node.js applications, many connections can be handled concurrently. Upon each connection, the callback is fired, but if there is no work to be done, Node.js will sleep.

This is in contrast to today's more common concurrency model, in which OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Furthermore, users of Node.js are free from worries of dead-locking the process, since there are no locks. Almost no function in Node.js directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.js.

== Node.js on Plesk Uses Passenger ==

== What is Passenger? ==

Passenger is a way of running Node.js and other applications that normally require a constantly running background process. Instead of the process always running in the background just waiting for connections, Passenger shuts it down if there are no connections. When someone visits the website, Passenger fires up the Node.js (or Ruby, or whatever language you're using) process. If another person visits the website while the Node.js process is still running, page loads will be very fast. If there are no further page hits for 5 minutes or so, Passenger kills the background process.

== Why Does HelioHost Use Passenger? ==

It doesn't make sense to leave your car running 24/7 in front of your house just in case you need to drive somewhere so it saves you a second to start the engine. This is a massive waste of gas. Likewise, it doesn't make sense to leave Node.js sites running 24/7 just to save a second of load time in case someone needs to view the page. This is a massive waste of memory. At HelioHost, we want to ensure that the server memory is used efficiently so our servers work efficiently for the hundreds of users on our shared hosting platform.

== Will Passenger Slow My Site Down? ==

A recent speed test on HelioHost servers showed that our app only took 177ms to load from a cold start. That's just under 1/5 of a second, roughly the amount of time it takes to blink.

== How Can I Use Passenger? ==

By following the steps in this tutorial, Plesk will automatically use Passenger to run your Node.js application.

== Can I Change the Inactivity Timeout? ==

No, the background process timeout is set to ensure fair resource usage for all our users and cannot be changed. If you need more control over memory management, HelioHost offers a range of [https://heliohost.org/vps/ VPS plans], where you can configure your settings, and a 10% discount when you pay for 6 months upfront.

== Can I Prevent My Site from Sleeping? ==

Passenger is designed to keep our shared hosting servers running efficiently and help keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]]. Deliberately preventing your site from sleeping is likely to get your account suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]] on our [[:Johnny|Johnny]] and [[:Tommy|Tommy]] servers, and charged for account load overages on our [[:Morty]] server.

== What If My Users Cannot Wait For My Site To Load? ==

If your application is highly time-sensitive and every millisecond of load time matters, you could upgrade to a VPS. {{Template:VPSInfo}} With a VPS, you won’t share your server with other users, so you can run any continuous process(es) that you want.

== How to setup Node.js ==

==== Delete the 'index.html' file (if it exists) ====

First, if you have an 'index.html' file inside your 'httpdocs' folder, delete it (or rename it to something else).

Your Node.js files will go into your home directory ('''NOT''' 'httpdocs'):

[[File:plesk_file_manager.png]]

==== Create an app.js file ====

In your home directory folder, create an 'app.js' file with these contents:

<pre>
const http = require('http');
const hostname = '127.0.0.1';
const port = 3000;

const server = http.createServer((req, res) => {
res.statusCode = 200;
res.setHeader('Content-Type', 'text/html');
res.end('Node.js is working.');
});

server.listen(port, hostname, () => {
console.log(`Server running at http://${hostname}:${port}/`);
});
</pre>

==== Configure Node.js settings ====

In Plesk, go to: '''Website & Domains > [domain] click on the 'Get Started' tab'''

[[File:nodejs-link.png]]

Here, you're able to configure settings for your application.

{{Info|We strongly recommend you change the '''Application Mode''' to '''Development''' as this will provide you with more detailed error reporting to help with troubleshooting and debugging any issues.}}

[[File:nodejs-settings.png]]

You don't need to worry about environment variables on this simple example. Select 'app.js' for your startup file. If you have any NPM packages, Plesk can install them for you.

[[File:nodejs-npm-install.png]]

==== Wait for the next Apache server restart ====

Finally, you will need to wait '''up to 2 hours''' for the server to update.

{{Caution|
Node.js application deployment can take '''up to 2 hours''' to go into effect as it requires an Apache restart. After an entire 2 hours, if your Node app is not working for you, please [[:Clear_Your_Cache|clear your web browser cache]].
}}

Once the Node.js application has been deployed, you should be able to visit 'domain.helioho.st' in your web browser and see the text 'Node.js is working.'

[[File:nodejs-working.png]]

== Further Support ==

If you encounter any Phusion Passenger(R) application server errors, please review our [[:Could_Not_Spawn_Process#Troubleshooting_Node_/_Passenger_Issues|Passenger troubleshooting help page]] for guidance on switching your application environment to 'Development' mode to see more detailed error reporting.

If it's been more than 2 hours, and the Node.js application still isn't working, please go back and check all of your steps again. If it's been more than a full 2 hours since your changes, and it still isn't working even after you [[:Clear_Your_Cache|cleared your web browser cache]], 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 create 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''', and any '''error message(s)''' encountered.

[[Category:Tutorials]]

File:Nodejs-settings.png

2025-12-21T01:45:03Z

KazVee:

FAQ

2025-12-11T00:40:11Z

KazVee: Update FAQ about exec() to reflect that it is no longer offered on Lily

== FAQ / Frequently Asked Questions ==

== ETA for New Features, Version Upgrades, and Server Repairs ==

{{Info|For information on ETAs for new features, software version upgrades, or server fixes, please review our [[:ETA|ETA]] page.}}

== Where do I ask for help? ==

Wherever you prefer to ask for help, please ask your question '''in one place only'''. HelioHost is run by volunteers who contribute their free time, and some are more active on certain platforms than others. Posting the same question across multiple platforms (like Discord, the HelioNet Forum, or email) or creating duplicate requests on the same platform for the same issue can result in unnecessary duplication of volunteer effort and delay responses to you, as well as to others who need help.

We recommend using the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] for support questions. If you later decide to ask on Discord for live help, please update your forum thread to let us know your issue has been resolved or moved elsewhere.

== How does community-powered support work? ==

HelioHost is a non-profit run entirely by volunteers. All support staff are volunteers who donate their free time to help others. In many cases, other users will also step in to offer support, simply because they want to give back to our community. Every staff member started out as a regular user who appreciated the project and began helping others with their questions and issues.

All support requests in the [https://helionet.org/ HelioNet Forum] are public, since this is the most efficient way for users to get help from the entire HelioHost community. This community-powered support model ensures that solutions are searchable and reusable by any other users who face similar issues in the future. Without public support, we wouldn’t attract new volunteers, and support would likely disappear altogether.

We do not currently offer private support, and do not consider the following items to be private information:
* [[:Signing_Up#Usernames_are_not_private | Usernames]]
* Domain names
* IP addresses
* [[#Providing_PayPal_Transaction_ID | PayPal Transaction IDs]]

If you choose to request support, you may be asked to provide some or all of the above details to assist with the resolution of your request.

If you do not wish to provide this information publicly, you could instead choose to use [https://wiki.helionet.org/ this Wiki] or the [https://helionet.org/ HelioNet Forum] as a completely self-serve option to try to resolve your queries yourself, without assistance or support from our community.

Requests to remove non-private information from forum posts are handled at the sole discretion of staff. In some cases, staff may choose to prioritize helping users with technical issues instead. Resolving actual problems can feel more meaningful and rewarding for volunteers than editing out public information from a public post on a public forum on the internet.

Requests to remove non-private information from public forum posts may eventually be considered under a [[#Can_I_get_Private_Support? | paid donation-only private support model]], where in exchange for a donation a staff member will remove public information from a public support post.

== Can I PM an administrator for help? ==

No, do not PM the administrators expecting support unless we explicitly tell you to. Please use the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] instead. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', and '''server name''' along with any requests. If you are sending your support request via email to 'support@heliohost.org', make sure to contact us '''from the same email address as your hosting account'''.

== Can I get Private Support? ==

There is currently no option for private support of any kind. Some users have expressed concerns about privacy, so we’re planning to offer a private support option for donors only, but there is [[:ETA|no ETA]] on when this may be implemented.

Eventually, for users who do not want their requests and the responses to them made public, where hundreds of community members might otherwise be able to help, private support requests will only be visible to staff. Then, if one of the handful of volunteer staff members has some spare time outside of their jobs, studies, and personal lives, they could pick up a donor-only paid support request.

Since a private support model for donors only will tie up an admin's time and prevent everyone else within the wider user community from helping out, it will likely be even slower than the existing community-powered model, with [[:ETA|no ETAs]] for private support requests from donors.

== Your homepage says "Professional-Grade Hosting", but your support sucks / isn't helping me / is run by a number of volunteers, what gives?‌ ==

There is a difference between "Professional-Grade Hosting" and "Professional-Grade Customer Support". Most people are used to having dedicated customer support staff that will answer every little question; this comes standard with paid hosting. However, we don't do that here. Among the five of us, we have the collective knowledge and technical expertise of any other support staff, but in order for us to help you, we expect from you a certain competency. You must try to spell and use grammar correctly (to the best of your ability). You must provide necessary information (e.g. '''username''' and '''domain name'''). You must be able to read instructions, and you must be able to follow instructions. We will treat you with respect and professionalism if you follow these guidelines. We will probably be very annoyed if u tyep liek dis.‌

== Can I get a free VPS? ==

HelioHost does not offer free VPS. {{Template:VPSInfo}}

What HelioHost offers for free is '''[[#Can_I_have_more_than_one_account?|1 account per person]]''' on our shared web hosting server, [[:Johnny]]. Check out our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny | list of helpful tips for getting a free account on Johnny]] if you would like to sign up.

== I log in frequently but am still receiving inactivity emails, what gives? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], to ensure that your logins are logged, log in to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review the [[:Suspension_Policy#Inactivity_Policy|Inactivity Policy]] section of our [[:Suspension_Policy|Suspension Policy]].

== Why must all posts on HelioNet be in English? ==

The support staff is fluent and reliable only in English.

== Why does HelioHost crash? ==

Sometimes users will abuse server resources and cause the server to crash. We try to fix this as quickly as we can. Since the servers and Plesk are handling such a high volume of users, errors are bound to come up. We also try to fix these ASAP. Also, when [[:Ashoat|djbob]] works on the server, he occasionally screws up, which also causes crashes.

== Why was my account suspended? ==

Our [[:Suspension_Policy|Suspension Policy]] provides comprehensive details on why we will suspend accounts.

A few common reasons for account suspensions are:

* [[:Terms|Terms of Service]] violation(s).
* [[:Suspension_Policy#Inactivity_Policy|Account Inactivity]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Renew your account [http://heliohost.org/renew/ here].
* [[:Suspension_Policy#Duplicate_Accounts|Duplicate Accounts]] on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers. The limit is '''1 account per human being'''.
** Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.
* Exceeding the [[:Suspension_Policy#Account_Storage_Limits|Account Storage limits]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We offer 1000 MB of free web space and optional one-time paid donation options for [[:Donations_for_Increased_Storage|increased account storage]] {{Template:VPSInfo}}
** Our [[:Morty|Morty]] server also offers 1000 MB of free web space. If you exceed this limit, instead of suspending your account, we will charge you for the overages.
* Exceeding the [[:Suspension_Policy#High_Server_Usage|High Server Usage]] limits on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We enforce a memory limit of no more than {{Template:MemoryLimit}} and a limit of {{Template:CPULimit}} per day. You can monitor your load numbers on [https://heliohost.org/dashboard/load/ the load page within your dashboard].
** Our [[:Morty|Morty]] server also has a memory limit of no more than {{Template:MemoryLimit}} and limit of {{Template:CPULimit}} per day. If you exceed these limits, instead of suspending your account, we will charge you for the overages.

It is also possible that this was an error in our system. If you suspect that this is the case, report the error in a new post [https://helionet.org/index/forum/81-suspended-and-queued-accounts/ here], making sure to provide your '''username'''.

== Why does my new subdomain show a "Queued" page? ==

{{Info|All domain and subdomain changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

During the first 2 hours, seeing the queued page is normal and only means the change hasn't taken effect yet. If it's been longer than '''a full 2 hours''', try [[:Clear_Your_Cache|clearing your browser cache]].

== Why can't I log in? ==

{{Info|If you just registered, please wait '''up to 2 hours''' for your Plesk account to become fully active.}}

If it has been longer than '''a full 2 hours''' since you registered and you still see an 'Account Queued' page, try [[:Clear_Your_Cache|clearing your browser cache]]. If you are still experiencing problems, make sure you are entering your username in all lowercase letters, i.e. "wizard", not "Wizard" or "WIZARD".

== How do I keep my account active / prevent being suspended? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], login to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review our [[:Suspension_Policy|Inactivity Policy]].

On our scaling hosting server, [[:Morty|Morty]], as long as there is a positive balance on your account, it will remain active without needing to log in.

== What is a Daily Signup Limit and why is it stopping me from registering? ==

Each server has a daily limit for sign-ups so that it doesn't crash from all the people wanting to use HelioHost. Free signups on Johnny now reset [https://helionet.org/index/topic/59660-midnight-and-noon/ every 12 hours] at midnight UTC and noon 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]].

== What if I have at least $2 USD and don't want to wait to sign up? ==

For a one-time donation of as little as $2 USD, you can open an account on our [[:Tommy|Tommy]] server any time of day. We offer various [https://heliohost.org/tommy/ Donor Plans], enabling you to sign up anytime with your donation via Credit card, Debit card, or PayPal.

If you prefer to donate Crypto to get a Tommy account, visit the [https://heliohost.org/donate/ Donate] page to view our Cryptocurrency wallets. Make sure that after transaction fees/gas the donation amount is $2 USD or more. After making the donation, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] so the transaction can be verified. Make sure you let us know the currency, amount, time of the transaction, and the email address you want the Tommy invite sent to. Please be aware that crypto donations can take time to verify. In the case of XMR and AEON, these can take several days to verify and are not recommended.

Users on our Tommy donor server and the free Johnny server are [[:Suspension_Policy#Inactivity Policy|required to log in at least once a month]] to keep their accounts active.

== What other options are available if I want to sign up right away? ==

For users who prefer not to have to log in regularly, our [[:Morty|Morty]] scaling server has no login requirement as long as there is a positive balance on your account.

{{Template:VPSInfo}}

== My account was deleted. Can I get my data back? ==

No. We do not keep backups of your data nor is it our responsibility to, as mentioned in our [[:Terms|Terms of Service]]. You must backup your own data regularly and download the backup to your local machine.

If you're not sure how to backup your data, please see our [[:Account_Backups|Account Backups tutorial]] page. It contains guidance on creating manual backups to download to your local machine, and instructions for setting up scheduled automated backups within Plesk.

== Can I have more than one account? ==

The first line of our [[:Terms | Terms of Service]] confirms that the limit is '''[[:Suspension_Policy#Duplicate_Accounts |1 account per human being]]''' on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers, even if you use different email addresses.

=== Multiple Accounts Allowed on Morty ===

Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.

== How do I reset my hosting account to start fresh? ==

{{Danger|Before requesting an account reset, make sure that the email address on your account is not hosted on HelioHost or else '''you will not be able to receive the invite email to recreate your account''' after it is wiped.

To check which email address is associated with your hosting account, go to: '''Plesk > Account > My Profile > General > External email address'''}}

=== Admin Account Reset Limits ===

{{Info|Due to certain users abusing our generosity in the past and requesting 5 or so resets in less than a week, we now limit each account to '''1 free reset per week''' done by an admin, with the option to [[#Purchasing_Additional_Account_Resets|donate for additional account resets if needed.]]}}

=== Free Self-Serve Account Resets (with Account Delete/Account Recreate) ===

We will eventually be adding the ability for users to reset their accounts automatically, without the need for admin assistance. However, there is [[:ETA|no estimated timeframe for this]], since there are many other higher-priority projects to be completed first.

In the meantime, users may delete their account and then recreate it, which effectively resets all account settings and contents, accomplishing the same thing as an account reset does.

Before deleting your account, [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|make a backup]]. Then, to delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button. Please make sure to allow some time for the deletion process to complete.

To recreate your account, try to login. You will be greeted with a 'Welcome back!' message, and prompted to enter your email address to receive an email invite to recreate your old account. Make sure to enter the same email address that was on the account you just deleted. Follow the steps to complete account recreation. You will receive an email confirming the new account has been successfully created.

{{Info|Account creation can take '''up to 2 hours''' because it requires an Apache reset. }}

=== Purchasing Additional Account Resets ===

If you need to purchase an additional account reset, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for account reset]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your account reset request, so the donation can be verified.

'''Note:''' Account resets must be purchased one at a time, and cannot be pre-ordered in bulk.

=== Before Asking an Admin for an Account Reset ===

Because wiping an account is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

Before asking for an account reset, we strongly recommend creating an [[:Account_Backups | account backup]], and '''downloading it to your local machine''' first. Any backups left inside Plesk will be wiped out during the reset.

To request that we reset your account so you can start over, send an email '''from the same email address listed in Plesk as your external email address''' to 'support@heliohost.org' so we can verify your identity and wipe your account. Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your hosting account.

Once your account has been reset, you will receive an email with a link to restart your account. '''You will have 7 days to use the link.''' If you don't use the link to restart your account within 7 days, you will need to signup for a brand new account.

=== Account Resets Disable Webmail ===

If you had webmail on your account, you will need to re-enable it after the reset has been completed. You can do this by going to:

'''Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > click the Save button'''

{{Caution|
Webmail can take '''up to 2 hours''' to become active after enabling it because it requires an Apache restart.
}}

=== Account Resets Remove WSGI Control Access ===

If you had WSGI Control Access on your [[:Morty]] server account for [[:Flask|Flask]] or [[:Django|Django]] and you want this re-enabled after the 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.

=== Account Resets Remove Addon Domains ===

If you had [[:Addon_Domains | additional domains]] on your account, you will need to re-request them after the reset has been completed.

== VPS Rebuilds ==

Due to certain users abusing our generosity in the past and requesting 50 or so rebuilds in less than a month, we now limit each VPS to '''1 free rebuild per month''' with the option to [[#Purchasing_Additional_VPS_Rebuilds | donate for additional VPS rebuilds]] if needed.

=== How do I request a VPS rebuild? ===

Because rebuilding a VPS is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

To request that we rebuild your VPS, send an email '''from the same email address as your VPS account''' to 'support@heliohost.org' so we can verify your identity and rebuild your VPS. If you would like a free dashboard (Hestia, KeyHelp, etc.) installed after the rebuild, please include this in the request.

Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your VPS account. If you're not sure what email address is associated with your VPS account, you can check by logging into the [https://heliohost.org/login/ VPS Dashboard] with your VPS Username and Password. The email address attached to your VPS account will be displayed at the top right of the page.

=== Purchasing Additional VPS Rebuilds ===

If you need to purchase an additional VPS rebuild, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for VPS Rebuild]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your VPS rebuild request, so the donation can be verified.

== 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].

== How do I change the contact email address on my account? ==

We recommend using a reliable external email address for your contact address because if you lose access to your HelioHost account, the contact email is the only way you have of recovering your account. If that email is hosted by us, you likely won't be able to access it either.

To change the email address on your account, login and go to: '''Plesk > Account > My Profile > General > External email address'''

When you change your email address it may take '''up to 2 hours''' to sync to the main website. In the meantime, login with your username (not email) on the main [https://heliohost.org/ heliohost.org] website. After a couple hours you should be able to login with either your username or your new external email address.

== How do I delete my hosting account? ==

To delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button.

To delete your HelioNet Forum account, post a topic in the [https://helionet.org/index/forum/4-contact-helionet/?do=add Contact HelioNet forum].

== How do I change my main domain? ==

To change the main domain on your HelioHost Plesk account, 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 domain name''' you want as your main domain, '''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.)

{{Caution|There is a risk of data loss when main domains are changed. We strongly recommend you [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|create an account backup]] and '''download the backup to your local machine''' before requesting a main domain change. As mentioned in our [[:Terms|Terms of Service]], it is not HelioHost's responsibility to keep backups of your data.}}

As an alternative to changing your main domain, consider using [[:Parked_(Alias)_Domains|Parked (Alias)]], [[:Addon_Domains|Addon]], and/or [[:Subdomains|Subdomains]].

== What are the nameservers for HelioHost? ==

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

== What IP addresses should I add to my DNS? ==

To add A (IPv4) or AAAA (IPv6) records to your domain registrar's dashboard, follow these steps to view the IP addresses for your server:

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

== The server is slow / Feature XYZ doesn't work / Something's wrong with my account / etc. ==

Please post the issue in the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] and we will try to solve the problem. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', '''server name''', and any '''error messages''' you are encountering.

== Can Feature XYZ be installed? ==

Softaculous [https://helionet.org/index/topic/59683-softaculous-has-returned/ returned in March 2024] and is offered on our [[:Morty|Morty]], [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, making it possible to install the latest version of 459 different software packages with just a single click.

To browse the available options, login to Plesk and select Softaculous from the menu:

[[File:softaculous_menu_item.png]]

If you need a system-wide feature installed, please post a request in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and any applicable '''version numbers'''.

== Can I use SSH? ==

On hosting accounts, secure shell access (SSH) is disabled for security reasons.

However, it is possible to run jailed shell commands using Plesk's [[:Cron_Jobs|Scheduled Tasks (cron jobs)]] feature.

In many cases, SSH is not actually necessary. Please post a request in our our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''the command you want to run''', and we'll be happy to investigate other ways to accomplish the same task without SSH.

If you absolutely require SSH access, you will need a VPS. {{Template:VPSInfo}}

== Can I use proc_open(), exec(), popen(), etc.? ==

These these functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

== Does HelioHost support sockets? Which ports are open? ==

Our [[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]] servers have zero inbound ports available to be opened. All ports that are currently open already have services listening, such as 80 http, 443 https, 3306 MariaDB, and 5432 PostgreSQL.

Outbound ports are similar: ports like 80, 443, 3306, 5432, 25, 465, etc., are open to allow scripts to connect to common services on remote servers.

If you can proxy your websocket through Apache or Nginx, it can work without opening a port:
* You could use an '.htaccess' file to proxy the websocket connection through Apache.
* With the help of a root admin, you could get an Nginx proxy set up. To explore this option, please post a request in our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''details about your websocket application''', and we'll be happy to help.

If you absolutely need a port opened, you'll need to get a VPS, and you will then have all 65535 ports available to open or close as you want. {{Template:VPSInfo}}

== Are directory indexes enabled? ==

Yes. Directory indexes have been enabled by default on the shared hosting servers since late 2024. This is a feature many users have requested over the past few years, but if you don't want directory listings for a folder, simply create an empty 'index.html' file inside it. Please check our [[:Create_Website#Directory_Index | Directory Index]] section for further information.

== Can I change my document root directory? ==

Typically, your domain root directory is 'httpdocs' (or 'public_html' if you were transferred from the old cPanel). Users cannot change the document root themselves inside Plesk.

If you're planning on using Laravel, you can set the document root yourself by using the [[:Laravel#Document_Root | Laravel Toolkit]].

If you have a legitimate reason for needing the document root changed, please create a post in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and make sure to provide your '''username''', '''domain name''', '''server name''', '''the new document root directory you want''', and a '''valid reason''' explaining why you are unable to use your existing document root. The admins will review your request to determine if the change can be made.

== I can login to Plesk, but can't login to SFTP, what do I do? ==

Sometimes the SFTP and Plesk passwords get out of sync. Please try changing the SFTP password by following these steps:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Connection Info > System user credentials > Click the 'edit icon' next to password'''

== How do I stop my Node.js app? ==

Node tutorials found elsewhere on the internet probably assume you have a VPS (not shared hosting) and you'll quickly get suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]].

If you need to stop a Node process that is already running, deleting the Node.js files via the file manager will '''not''' stop already running processes.

To stop an already running Node.js process, you should disable Node by following the steps below:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Get Started > Node.js > Disable Node.js'''

If you follow our [[:Node.js|Node.js guide]], it will use Passenger which automatically stops Node.js processes if your website isn't getting any visitors. This will help try to keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]].

If you do not want to use Passenger, we recommend you upgrade to a VPS. {{Template:VPSInfo}}

== Can I use your services to mine cryptocurrency? ==

No. We do not allow mining on any of our plans (free or paid).

== Your hosting SUCKS! So do YOU!!! ==

Please see [http://helionet.org/index/topic/4723-suspended/page__p__46231#entry46231 this].

== I still have a question about HelioHost. ==

Post in the [https://helionet.org/index/forum/48-questions/ Questions forum] and we'll try to help you the best we can.

Lily

2025-12-11T00:33:46Z

KazVee: Add PHP 8.4 & PHP 8.5 to versions offered on Lily server

== 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 ==

* 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
* PHP 8.4
* PHP 8.5

== Databases ==

* MariaDB
* MS SQL Server Express 2017

NET NET Core Classic ASP

2025-12-11T00:33:12Z

KazVee: Add .NET 9.0 to versions offered on Lily

== .NET / .NET Core / Classic ASP ==

== .NET ==

HelioHost offers the following .NET versions:

* .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

To use these, you would need to request an account on [[:Lily|Lily]].

== How to Request a Lily Account ==

To request an account on [[:Lily|Lily]], you must already have a Plesk account on [[:Morty|Morty]], [[:Tommy|Tommy]], or [[:Johnny|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.

PHP

2025-12-11T00:30:18Z

KazVee: Add PHP 8.4 & PHP 8.5 to Lily server section

FAQ

2025-12-08T15:33:07Z

KazVee: Update wording for clarity

== FAQ / Frequently Asked Questions ==

== ETA for New Features, Version Upgrades, and Server Repairs ==

{{Info|For information on ETAs for new features, software version upgrades, or server fixes, please review our [[:ETA|ETA]] page.}}

== Where do I ask for help? ==

Wherever you prefer to ask for help, please ask your question '''in one place only'''. HelioHost is run by volunteers who contribute their free time, and some are more active on certain platforms than others. Posting the same question across multiple platforms (like Discord, the HelioNet Forum, or email) or creating duplicate requests on the same platform for the same issue can result in unnecessary duplication of volunteer effort and delay responses to you, as well as to others who need help.

We recommend using the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] for support questions. If you later decide to ask on Discord for live help, please update your forum thread to let us know your issue has been resolved or moved elsewhere.

== How does community-powered support work? ==

HelioHost is a non-profit run entirely by volunteers. All support staff are volunteers who donate their free time to help others. In many cases, other users will also step in to offer support, simply because they want to give back to our community. Every staff member started out as a regular user who appreciated the project and began helping others with their questions and issues.

All support requests in the [https://helionet.org/ HelioNet Forum] are public, since this is the most efficient way for users to get help from the entire HelioHost community. This community-powered support model ensures that solutions are searchable and reusable by any other users who face similar issues in the future. Without public support, we wouldn’t attract new volunteers, and support would likely disappear altogether.

We do not currently offer private support, and do not consider the following items to be private information:
* [[:Signing_Up#Usernames_are_not_private | Usernames]]
* Domain names
* IP addresses
* [[#Providing_PayPal_Transaction_ID | PayPal Transaction IDs]]

If you choose to request support, you may be asked to provide some or all of the above details to assist with the resolution of your request.

If you do not wish to provide this information publicly, you could instead choose to use [https://wiki.helionet.org/ this Wiki] or the [https://helionet.org/ HelioNet Forum] as a completely self-serve option to try to resolve your queries yourself, without assistance or support from our community.

Requests to remove non-private information from forum posts are handled at the sole discretion of staff. In some cases, staff may choose to prioritize helping users with technical issues instead. Resolving actual problems can feel more meaningful and rewarding for volunteers than editing out public information from a public post on a public forum on the internet.

Requests to remove non-private information from public forum posts may eventually be considered under a [[#Can_I_get_Private_Support? | paid donation-only private support model]], where in exchange for a donation a staff member will remove public information from a public support post.

== Can I PM an administrator for help? ==

No, do not PM the administrators expecting support unless we explicitly tell you to. Please use the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] instead. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', and '''server name''' along with any requests. If you are sending your support request via email to 'support@heliohost.org', make sure to contact us '''from the same email address as your hosting account'''.

== Can I get Private Support? ==

There is currently no option for private support of any kind. Some users have expressed concerns about privacy, so we’re planning to offer a private support option for donors only, but there is [[:ETA|no ETA]] on when this may be implemented.

Eventually, for users who do not want their requests and the responses to them made public, where hundreds of community members might otherwise be able to help, private support requests will only be visible to staff. Then, if one of the handful of volunteer staff members has some spare time outside of their jobs, studies, and personal lives, they could pick up a donor-only paid support request.

Since a private support model for donors only will tie up an admin's time and prevent everyone else within the wider user community from helping out, it will likely be even slower than the existing community-powered model, with [[:ETA|no ETAs]] for private support requests from donors.

== Your homepage says "Professional-Grade Hosting", but your support sucks / isn't helping me / is run by a number of volunteers, what gives?‌ ==

There is a difference between "Professional-Grade Hosting" and "Professional-Grade Customer Support". Most people are used to having dedicated customer support staff that will answer every little question; this comes standard with paid hosting. However, we don't do that here. Among the five of us, we have the collective knowledge and technical expertise of any other support staff, but in order for us to help you, we expect from you a certain competency. You must try to spell and use grammar correctly (to the best of your ability). You must provide necessary information (e.g. '''username''' and '''domain name'''). You must be able to read instructions, and you must be able to follow instructions. We will treat you with respect and professionalism if you follow these guidelines. We will probably be very annoyed if u tyep liek dis.‌

== Can I get a free VPS? ==

HelioHost does not offer free VPS. {{Template:VPSInfo}}

What HelioHost offers for free is '''[[#Can_I_have_more_than_one_account?|1 account per person]]''' on our shared web hosting server, [[:Johnny]]. Check out our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny | list of helpful tips for getting a free account on Johnny]] if you would like to sign up.

== I log in frequently but am still receiving inactivity emails, what gives? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], to ensure that your logins are logged, log in to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review the [[:Suspension_Policy#Inactivity_Policy|Inactivity Policy]] section of our [[:Suspension_Policy|Suspension Policy]].

== Why must all posts on HelioNet be in English? ==

The support staff is fluent and reliable only in English.

== Why does HelioHost crash? ==

Sometimes users will abuse server resources and cause the server to crash. We try to fix this as quickly as we can. Since the servers and Plesk are handling such a high volume of users, errors are bound to come up. We also try to fix these ASAP. Also, when [[:Ashoat|djbob]] works on the server, he occasionally screws up, which also causes crashes.

== Why was my account suspended? ==

Our [[:Suspension_Policy|Suspension Policy]] provides comprehensive details on why we will suspend accounts.

A few common reasons for account suspensions are:

* [[:Terms|Terms of Service]] violation(s).
* [[:Suspension_Policy#Inactivity_Policy|Account Inactivity]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Renew your account [http://heliohost.org/renew/ here].
* [[:Suspension_Policy#Duplicate_Accounts|Duplicate Accounts]] on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers. The limit is '''1 account per human being'''.
** Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.
* Exceeding the [[:Suspension_Policy#Account_Storage_Limits|Account Storage limits]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We offer 1000 MB of free web space and optional one-time paid donation options for [[:Donations_for_Increased_Storage|increased account storage]] {{Template:VPSInfo}}
** Our [[:Morty|Morty]] server also offers 1000 MB of free web space. If you exceed this limit, instead of suspending your account, we will charge you for the overages.
* Exceeding the [[:Suspension_Policy#High_Server_Usage|High Server Usage]] limits on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We enforce a memory limit of no more than {{Template:MemoryLimit}} and a limit of {{Template:CPULimit}} per day. You can monitor your load numbers on [https://heliohost.org/dashboard/load/ the load page within your dashboard].
** Our [[:Morty|Morty]] server also has a memory limit of no more than {{Template:MemoryLimit}} and limit of {{Template:CPULimit}} per day. If you exceed these limits, instead of suspending your account, we will charge you for the overages.

It is also possible that this was an error in our system. If you suspect that this is the case, report the error in a new post [https://helionet.org/index/forum/81-suspended-and-queued-accounts/ here], making sure to provide your '''username'''.

== Why does my new subdomain show a "Queued" page? ==

{{Info|All domain and subdomain changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

During the first 2 hours, seeing the queued page is normal and only means the change hasn't taken effect yet. If it's been longer than '''a full 2 hours''', try [[:Clear_Your_Cache|clearing your browser cache]].

== Why can't I log in? ==

{{Info|If you just registered, please wait '''up to 2 hours''' for your Plesk account to become fully active.}}

If it has been longer than '''a full 2 hours''' since you registered and you still see an 'Account Queued' page, try [[:Clear_Your_Cache|clearing your browser cache]]. If you are still experiencing problems, make sure you are entering your username in all lowercase letters, i.e. "wizard", not "Wizard" or "WIZARD".

== How do I keep my account active / prevent being suspended? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], login to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review our [[:Suspension_Policy|Inactivity Policy]].

On our scaling hosting server, [[:Morty|Morty]], as long as there is a positive balance on your account, it will remain active without needing to log in.

== What is a Daily Signup Limit and why is it stopping me from registering? ==

Each server has a daily limit for sign-ups so that it doesn't crash from all the people wanting to use HelioHost. Free signups on Johnny now reset [https://helionet.org/index/topic/59660-midnight-and-noon/ every 12 hours] at midnight UTC and noon 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]].

== What if I have at least $2 USD and don't want to wait to sign up? ==

For a one-time donation of as little as $2 USD, you can open an account on our [[:Tommy|Tommy]] server any time of day. We offer various [https://heliohost.org/tommy/ Donor Plans], enabling you to sign up anytime with your donation via Credit card, Debit card, or PayPal.

If you prefer to donate Crypto to get a Tommy account, visit the [https://heliohost.org/donate/ Donate] page to view our Cryptocurrency wallets. Make sure that after transaction fees/gas the donation amount is $2 USD or more. After making the donation, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] so the transaction can be verified. Make sure you let us know the currency, amount, time of the transaction, and the email address you want the Tommy invite sent to. Please be aware that crypto donations can take time to verify. In the case of XMR and AEON, these can take several days to verify and are not recommended.

Users on our Tommy donor server and the free Johnny server are [[:Suspension_Policy#Inactivity Policy|required to log in at least once a month]] to keep their accounts active.

== What other options are available if I want to sign up right away? ==

For users who prefer not to have to log in regularly, our [[:Morty|Morty]] scaling server has no login requirement as long as there is a positive balance on your account.

{{Template:VPSInfo}}

== My account was deleted. Can I get my data back? ==

No. We do not keep backups of your data nor is it our responsibility to, as mentioned in our [[:Terms|Terms of Service]]. You must backup your own data regularly and download the backup to your local machine.

If you're not sure how to backup your data, please see our [[:Account_Backups|Account Backups tutorial]] page. It contains guidance on creating manual backups to download to your local machine, and instructions for setting up scheduled automated backups within Plesk.

== Can I have more than one account? ==

The first line of our [[:Terms | Terms of Service]] confirms that the limit is '''[[:Suspension_Policy#Duplicate_Accounts |1 account per human being]]''' on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers, even if you use different email addresses.

=== Multiple Accounts Allowed on Morty ===

Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.

== How do I reset my hosting account to start fresh? ==

{{Danger|Before requesting an account reset, make sure that the email address on your account is not hosted on HelioHost or else '''you will not be able to receive the invite email to recreate your account''' after it is wiped.

To check which email address is associated with your hosting account, go to: '''Plesk > Account > My Profile > General > External email address'''}}

=== Admin Account Reset Limits ===

{{Info|Due to certain users abusing our generosity in the past and requesting 5 or so resets in less than a week, we now limit each account to '''1 free reset per week''' done by an admin, with the option to [[#Purchasing_Additional_Account_Resets|donate for additional account resets if needed.]]}}

=== Free Self-Serve Account Resets (with Account Delete/Account Recreate) ===

We will eventually be adding the ability for users to reset their accounts automatically, without the need for admin assistance. However, there is [[:ETA|no estimated timeframe for this]], since there are many other higher-priority projects to be completed first.

In the meantime, users may delete their account and then recreate it, which effectively resets all account settings and contents, accomplishing the same thing as an account reset does.

Before deleting your account, [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|make a backup]]. Then, to delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button. Please make sure to allow some time for the deletion process to complete.

To recreate your account, try to login. You will be greeted with a 'Welcome back!' message, and prompted to enter your email address to receive an email invite to recreate your old account. Make sure to enter the same email address that was on the account you just deleted. Follow the steps to complete account recreation. You will receive an email confirming the new account has been successfully created.

{{Info|Account creation can take '''up to 2 hours''' because it requires an Apache reset. }}

=== Purchasing Additional Account Resets ===

If you need to purchase an additional account reset, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for account reset]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your account reset request, so the donation can be verified.

'''Note:''' Account resets must be purchased one at a time, and cannot be pre-ordered in bulk.

=== Before Asking an Admin for an Account Reset ===

Because wiping an account is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

Before asking for an account reset, we strongly recommend creating an [[:Account_Backups | account backup]], and '''downloading it to your local machine''' first. Any backups left inside Plesk will be wiped out during the reset.

To request that we reset your account so you can start over, send an email '''from the same email address listed in Plesk as your external email address''' to 'support@heliohost.org' so we can verify your identity and wipe your account. Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your hosting account.

Once your account has been reset, you will receive an email with a link to restart your account. '''You will have 7 days to use the link.''' If you don't use the link to restart your account within 7 days, you will need to signup for a brand new account.

=== Account Resets Disable Webmail ===

If you had webmail on your account, you will need to re-enable it after the reset has been completed. You can do this by going to:

'''Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > click the Save button'''

{{Caution|
Webmail can take '''up to 2 hours''' to become active after enabling it because it requires an Apache restart.
}}

=== Account Resets Remove WSGI Control Access ===

If you had WSGI Control Access on your [[:Morty]] server account for [[:Flask|Flask]] or [[:Django|Django]] and you want this re-enabled after the 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.

=== Account Resets Remove Addon Domains ===

If you had [[:Addon_Domains | additional domains]] on your account, you will need to re-request them after the reset has been completed.

== VPS Rebuilds ==

Due to certain users abusing our generosity in the past and requesting 50 or so rebuilds in less than a month, we now limit each VPS to '''1 free rebuild per month''' with the option to [[#Purchasing_Additional_VPS_Rebuilds | donate for additional VPS rebuilds]] if needed.

=== How do I request a VPS rebuild? ===

Because rebuilding a VPS is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

To request that we rebuild your VPS, send an email '''from the same email address as your VPS account''' to 'support@heliohost.org' so we can verify your identity and rebuild your VPS. If you would like a free dashboard (Hestia, KeyHelp, etc.) installed after the rebuild, please include this in the request.

Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your VPS account. If you're not sure what email address is associated with your VPS account, you can check by logging into the [https://heliohost.org/login/ VPS Dashboard] with your VPS Username and Password. The email address attached to your VPS account will be displayed at the top right of the page.

=== Purchasing Additional VPS Rebuilds ===

If you need to purchase an additional VPS rebuild, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for VPS Rebuild]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your VPS rebuild request, so the donation can be verified.

== 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].

== How do I change the contact email address on my account? ==

We recommend using a reliable external email address for your contact address because if you lose access to your HelioHost account, the contact email is the only way you have of recovering your account. If that email is hosted by us, you likely won't be able to access it either.

To change the email address on your account, login and go to: '''Plesk > Account > My Profile > General > External email address'''

When you change your email address it may take '''up to 2 hours''' to sync to the main website. In the meantime, login with your username (not email) on the main [https://heliohost.org/ heliohost.org] website. After a couple hours you should be able to login with either your username or your new external email address.

== How do I delete my hosting account? ==

To delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button.

To delete your HelioNet Forum account, post a topic in the [https://helionet.org/index/forum/4-contact-helionet/?do=add Contact HelioNet forum].

== How do I change my main domain? ==

To change the main domain on your HelioHost Plesk account, 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 domain name''' you want as your main domain, '''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.)

{{Caution|There is a risk of data loss when main domains are changed. We strongly recommend you [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|create an account backup]] and '''download the backup to your local machine''' before requesting a main domain change. As mentioned in our [[:Terms|Terms of Service]], it is not HelioHost's responsibility to keep backups of your data.}}

As an alternative to changing your main domain, consider using [[:Parked_(Alias)_Domains|Parked (Alias)]], [[:Addon_Domains|Addon]], and/or [[:Subdomains|Subdomains]].

== What are the nameservers for HelioHost? ==

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

== What IP addresses should I add to my DNS? ==

To add A (IPv4) or AAAA (IPv6) records to your domain registrar's dashboard, follow these steps to view the IP addresses for your server:

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

== The server is slow / Feature XYZ doesn't work / Something's wrong with my account / etc. ==

Please post the issue in the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] and we will try to solve the problem. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', '''server name''', and any '''error messages''' you are encountering.

== Can Feature XYZ be installed? ==

Softaculous [https://helionet.org/index/topic/59683-softaculous-has-returned/ returned in March 2024] and is offered on our [[:Morty|Morty]], [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, making it possible to install the latest version of 459 different software packages with just a single click.

To browse the available options, login to Plesk and select Softaculous from the menu:

[[File:softaculous_menu_item.png]]

If you need a system-wide feature installed, please post a request in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and any applicable '''version numbers'''.

== Can I use SSH? ==

On hosting accounts, secure shell access (SSH) is disabled for security reasons.

However, it is possible to run jailed shell commands using Plesk's [[:Cron_Jobs|Scheduled Tasks (cron jobs)]] feature.

In many cases, SSH is not actually necessary. Please post a request in our our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''the command you want to run''', and we'll be happy to investigate other ways to accomplish the same task without SSH.

If you absolutely require SSH access, you will need a VPS. {{Template:VPSInfo}}

== Can I use proc_open(), exec(), popen(), etc.? ==

These these functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

Our [[:Lily|Lily]] server, which runs Windows Server, has exec() enabled on all PHP versions.

== Does HelioHost support sockets? Which ports are open? ==

Our [[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]] servers have zero inbound ports available to be opened. All ports that are currently open already have services listening, such as 80 http, 443 https, 3306 MariaDB, and 5432 PostgreSQL.

Outbound ports are similar: ports like 80, 443, 3306, 5432, 25, 465, etc., are open to allow scripts to connect to common services on remote servers.

If you can proxy your websocket through Apache or Nginx, it can work without opening a port:
* You could use an '.htaccess' file to proxy the websocket connection through Apache.
* With the help of a root admin, you could get an Nginx proxy set up. To explore this option, please post a request in our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''details about your websocket application''', and we'll be happy to help.

If you absolutely need a port opened, you'll need to get a VPS, and you will then have all 65535 ports available to open or close as you want. {{Template:VPSInfo}}

== Are directory indexes enabled? ==

Yes. Directory indexes have been enabled by default on the shared hosting servers since late 2024. This is a feature many users have requested over the past few years, but if you don't want directory listings for a folder, simply create an empty 'index.html' file inside it. Please check our [[:Create_Website#Directory_Index | Directory Index]] section for further information.

== Can I change my document root directory? ==

Typically, your domain root directory is 'httpdocs' (or 'public_html' if you were transferred from the old cPanel). Users cannot change the document root themselves inside Plesk.

If you're planning on using Laravel, you can set the document root yourself by using the [[:Laravel#Document_Root | Laravel Toolkit]].

If you have a legitimate reason for needing the document root changed, please create a post in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and make sure to provide your '''username''', '''domain name''', '''server name''', '''the new document root directory you want''', and a '''valid reason''' explaining why you are unable to use your existing document root. The admins will review your request to determine if the change can be made.

== I can login to Plesk, but can't login to SFTP, what do I do? ==

Sometimes the SFTP and Plesk passwords get out of sync. Please try changing the SFTP password by following these steps:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Connection Info > System user credentials > Click the 'edit icon' next to password'''

== How do I stop my Node.js app? ==

Node tutorials found elsewhere on the internet probably assume you have a VPS (not shared hosting) and you'll quickly get suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]].

If you need to stop a Node process that is already running, deleting the Node.js files via the file manager will '''not''' stop already running processes.

To stop an already running Node.js process, you should disable Node by following the steps below:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Get Started > Node.js > Disable Node.js'''

If you follow our [[:Node.js|Node.js guide]], it will use Passenger which automatically stops Node.js processes if your website isn't getting any visitors. This will help try to keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]].

If you do not want to use Passenger, we recommend you upgrade to a VPS. {{Template:VPSInfo}}

== Can I use your services to mine cryptocurrency? ==

No. We do not allow mining on any of our plans (free or paid).

== Your hosting SUCKS! So do YOU!!! ==

Please see [http://helionet.org/index/topic/4723-suspended/page__p__46231#entry46231 this].

== I still have a question about HelioHost. ==

Post in the [https://helionet.org/index/forum/48-questions/ Questions forum] and we'll try to help you the best we can.

FAQ

2025-12-04T18:06:54Z

KazVee: Add note that Laravel Toolkit enables users to change their document root

== FAQ / Frequently Asked Questions ==

== ETA for New Features, Version Upgrades, and Server Repairs ==

{{Info|For information on ETAs for new features, software version upgrades, or server fixes, please review our [[:ETA|ETA]] page.}}

== Where do I ask for help? ==

Wherever you prefer to ask for help, please ask your question '''in one place only'''. HelioHost is run by volunteers who contribute their free time, and some are more active on certain platforms than others. Posting the same question across multiple platforms (like Discord, the HelioNet Forum, or email) or creating duplicate requests on the same platform for the same issue can result in unnecessary duplication of volunteer effort and delay responses to you, as well as to others who need help.

We recommend using the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] for support questions. If you later decide to ask on Discord for live help, please update your forum thread to let us know your issue has been resolved or moved elsewhere.

== How does community-powered support work? ==

HelioHost is a non-profit run entirely by volunteers. All support staff are volunteers who donate their free time to help others. In many cases, other users will also step in to offer support, simply because they want to give back to our community. Every staff member started out as a regular user who appreciated the project and began helping others with their questions and issues.

All support requests in the [https://helionet.org/ HelioNet Forum] are public, since this is the most efficient way for users to get help from the entire HelioHost community. This community-powered support model ensures that solutions are searchable and reusable by any other users who face similar issues in the future. Without public support, we wouldn’t attract new volunteers, and support would likely disappear altogether.

We do not currently offer private support, and do not consider the following items to be private information:
* [[:Signing_Up#Usernames_are_not_private | Usernames]]
* Domain names
* IP addresses
* [[#Providing_PayPal_Transaction_ID | PayPal Transaction IDs]]

If you choose to request support, you may be asked to provide some or all of the above details to assist with the resolution of your request.

If you do not wish to provide this information publicly, you could instead choose to use [https://wiki.helionet.org/ this Wiki] or the [https://helionet.org/ HelioNet Forum] as a completely self-serve option to try to resolve your queries yourself, without assistance or support from our community.

Requests to remove non-private information from forum posts are handled at the sole discretion of staff. In some cases, staff may choose to prioritize helping users with technical issues instead. Resolving actual problems can feel more meaningful and rewarding for volunteers than editing out public information from a public post on a public forum on the internet.

Requests to remove non-private information from public forum posts may eventually be considered under a [[#Can_I_get_Private_Support? | paid donation-only private support model]], where in exchange for a donation a staff member will remove public information from a public support post.

== Can I PM an administrator for help? ==

No, do not PM the administrators expecting support unless we explicitly tell you to. Please use the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] instead. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', and '''server name''' along with any requests. If you are sending your support request via email to 'support@heliohost.org', make sure to contact us '''from the same email address as your hosting account'''.

== Can I get Private Support? ==

There is currently no option for private support of any kind. Some users have expressed concerns about privacy, so we’re planning to offer a private support option for donors only, but there is [[:ETA|no ETA]] on when this may be implemented.

Eventually, for users who do not want their requests and the responses to them made public, where hundreds of community members might otherwise be able to help, private support requests will only be visible to staff. Then, if one of the handful of volunteer staff members has some spare time outside of their jobs, studies, and personal lives, they could pick up a donor-only paid support request.

Since a private support model for donors only will tie up an admin's time and prevent everyone else within the wider user community from helping out, it will likely be even slower than the existing community-powered model, with [[:ETA|no ETAs]] for private support requests from donors.

== Your homepage says "Professional-Grade Hosting", but your support sucks / isn't helping me / is run by a number of volunteers, what gives?‌ ==

There is a difference between "Professional-Grade Hosting" and "Professional-Grade Customer Support". Most people are used to having dedicated customer support staff that will answer every little question; this comes standard with paid hosting. However, we don't do that here. Among the five of us, we have the collective knowledge and technical expertise of any other support staff, but in order for us to help you, we expect from you a certain competency. You must try to spell and use grammar correctly (to the best of your ability). You must provide necessary information (e.g. '''username''' and '''domain name'''). You must be able to read instructions, and you must be able to follow instructions. We will treat you with respect and professionalism if you follow these guidelines. We will probably be very annoyed if u tyep liek dis.‌

== Can I get a free VPS? ==

HelioHost does not offer free VPS. {{Template:VPSInfo}}

What HelioHost offers for free is '''[[#Can_I_have_more_than_one_account?|1 account per person]]''' on our shared web hosting server, [[:Johnny]]. Check out our [[:Signing_Up#Helpful_Tips_for_Getting_a_Free_Account_on_Johnny | list of helpful tips for getting a free account on Johnny]] if you would like to sign up.

== I log in frequently but am still receiving inactivity emails, what gives? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], to ensure that your logins are logged, log in to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review the [[:Suspension_Policy#Inactivity_Policy|Inactivity Policy]] section of our [[:Suspension_Policy|Suspension Policy]].

== Why must all posts on HelioNet be in English? ==

The support staff is fluent and reliable only in English.

== Why does HelioHost crash? ==

Sometimes users will abuse server resources and cause the server to crash. We try to fix this as quickly as we can. Since the servers and Plesk are handling such a high volume of users, errors are bound to come up. We also try to fix these ASAP. Also, when [[:Ashoat|djbob]] works on the server, he occasionally screws up, which also causes crashes.

== Why was my account suspended? ==

Our [[:Suspension_Policy|Suspension Policy]] provides comprehensive details on why we will suspend accounts.

A few common reasons for account suspensions are:

* [[:Terms|Terms of Service]] violation(s).
* [[:Suspension_Policy#Inactivity_Policy|Account Inactivity]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. Renew your account [http://heliohost.org/renew/ here].
* [[:Suspension_Policy#Duplicate_Accounts|Duplicate Accounts]] on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers. The limit is '''1 account per human being'''.
** Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.
* Exceeding the [[:Suspension_Policy#Account_Storage_Limits|Account Storage limits]] on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We offer 1000 MB of free web space and optional one-time paid donation options for [[:Donations_for_Increased_Storage|increased account storage]] {{Template:VPSInfo}}
** Our [[:Morty|Morty]] server also offers 1000 MB of free web space. If you exceed this limit, instead of suspending your account, we will charge you for the overages.
* Exceeding the [[:Suspension_Policy#High_Server_Usage|High Server Usage]] limits on our [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers. We enforce a memory limit of no more than {{Template:MemoryLimit}} and a limit of {{Template:CPULimit}} per day. You can monitor your load numbers on [https://heliohost.org/dashboard/load/ the load page within your dashboard].
** Our [[:Morty|Morty]] server also has a memory limit of no more than {{Template:MemoryLimit}} and limit of {{Template:CPULimit}} per day. If you exceed these limits, instead of suspending your account, we will charge you for the overages.

It is also possible that this was an error in our system. If you suspect that this is the case, report the error in a new post [https://helionet.org/index/forum/81-suspended-and-queued-accounts/ here], making sure to provide your '''username'''.

== Why does my new subdomain show a "Queued" page? ==

{{Info|All domain and subdomain changes take '''up to 2 hours''' to go into effect as they require an Apache restart.}}

During the first 2 hours, seeing the queued page is normal and only means the change hasn't taken effect yet. If it's been longer than '''a full 2 hours''', try [[:Clear_Your_Cache|clearing your browser cache]].

== Why can't I log in? ==

{{Info|If you just registered, please wait '''up to 2 hours''' for your Plesk account to become fully active.}}

If it has been longer than '''a full 2 hours''' since you registered and you still see an 'Account Queued' page, try [[:Clear_Your_Cache|clearing your browser cache]]. If you are still experiencing problems, make sure you are entering your username in all lowercase letters, i.e. "wizard", not "Wizard" or "WIZARD".

== How do I keep my account active / prevent being suspended? ==

If you have an account on [[:Tommy|Tommy]] or [[:Johnny|Johnny]], login to [https://heliohost.org heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] at least once a month. Each time you do so your last login date is set to the current time. Your account will then remain active for another 30 days. For more details, review our [[:Suspension_Policy|Inactivity Policy]].

On our scaling hosting server, [[:Morty|Morty]], as long as there is a positive balance on your account, it will remain active without needing to log in.

== What is a Daily Signup Limit and why is it stopping me from registering? ==

Each server has a daily limit for sign-ups so that it doesn't crash from all the people wanting to use HelioHost. Free signups on Johnny now reset [https://helionet.org/index/topic/59660-midnight-and-noon/ every 12 hours] at midnight UTC and noon 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]].

== What if I have at least $2 USD and don't want to wait to sign up? ==

For a one-time donation of as little as $2 USD, you can open an account on our [[:Tommy|Tommy]] server any time of day. We offer various [https://heliohost.org/tommy/ Donor Plans], enabling you to sign up anytime with your donation via Credit card, Debit card, or PayPal.

If you prefer to donate Crypto to get a Tommy account, visit the [https://heliohost.org/donate/ Donate] page to view our Cryptocurrency wallets. Make sure that after transaction fees/gas the donation amount is $2 USD or more. After making the donation, please create a post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] so the transaction can be verified. Make sure you let us know the currency, amount, time of the transaction, and the email address you want the Tommy invite sent to. Please be aware that crypto donations can take time to verify. In the case of XMR and AEON, these can take several days to verify and are not recommended.

Users on our Tommy donor server and the free Johnny server are [[:Suspension_Policy#Inactivity Policy|required to log in at least once a month]] to keep their accounts active.

== What other options are available if I want to sign up right away? ==

For users who prefer not to have to log in regularly, our [[:Morty|Morty]] scaling server has no login requirement as long as there is a positive balance on your account.

{{Template:VPSInfo}}

== My account was deleted. Can I get my data back? ==

No. We do not keep backups of your data nor is it our responsibility to, as mentioned in our [[:Terms|Terms of Service]]. You must backup your own data regularly and download the backup to your local machine.

If you're not sure how to backup your data, please see our [[:Account_Backups|Account Backups tutorial]] page. It contains guidance on creating manual backups to download to your local machine, and instructions for setting up scheduled automated backups within Plesk.

== Can I have more than one account? ==

The first line of our [[:Terms | Terms of Service]] confirms that the limit is '''[[:Suspension_Policy#Duplicate_Accounts |1 account per human being]]''' on our [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers, even if you use different email addresses.

=== Multiple Accounts Allowed on Morty ===

Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.

== How do I reset my hosting account to start fresh? ==

{{Danger|Before requesting an account reset, make sure that the email address on your account is not hosted on HelioHost or else '''you will not be able to receive the invite email to recreate your account''' after it is wiped.

To check which email address is associated with your hosting account, go to: '''Plesk > Account > My Profile > General > External email address'''}}

=== Admin Account Reset Limits ===

{{Info|Due to certain users abusing our generosity in the past and requesting 5 or so resets in less than a week, we now limit each account to '''1 free reset per week''' done by an admin, with the option to [[#Purchasing_Additional_Account_Resets|donate for additional account resets if needed.]]}}

=== Free Self-Serve Account Resets (with Account Delete/Account Recreate) ===

We will eventually be adding the ability for users to reset their accounts automatically, without the need for admin assistance. However, there is [[:ETA|no estimated timeframe for this]], since there are many other higher-priority projects to be completed first.

In the meantime, users may delete their account and then recreate it, which effectively resets all account settings and contents, accomplishing the same thing as an account reset does.

Before deleting your account, [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|make a backup]]. Then, to delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button. Please make sure to allow some time for the deletion process to complete.

To recreate your account, try to login. You will be greeted with a 'Welcome back!' message, and prompted to enter your email address to receive an email invite to recreate your old account. Make sure to enter the same email address that was on the account you just deleted. Follow the steps to complete account recreation. You will receive an email confirming the new account has been successfully created.

{{Info|Account creation can take '''up to 2 hours''' because it requires an Apache reset. }}

=== Purchasing Additional Account Resets ===

If you need to purchase an additional account reset, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for account reset]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your account reset request, so the donation can be verified.

'''Note:''' Account resets must be purchased one at a time, and cannot be pre-ordered in bulk.

=== Before Asking an Admin for an Account Reset ===

Because wiping an account is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

Before asking for an account reset, we strongly recommend creating an [[:Account_Backups | account backup]], and '''downloading it to your local machine''' first. Any backups left inside Plesk will be wiped out during the reset.

To request that we reset your account so you can start over, send an email '''from the same email address listed in Plesk as your external email address''' to 'support@heliohost.org' so we can verify your identity and wipe your account. Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your hosting account.

Once your account has been reset, you will receive an email with a link to restart your account. '''You will have 7 days to use the link.''' If you don't use the link to restart your account within 7 days, you will need to signup for a brand new account.

=== Account Resets Disable Webmail ===

If you had webmail on your account, you will need to re-enable it after the reset has been completed. You can do this by going to:

'''Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > click the Save button'''

{{Caution|
Webmail can take '''up to 2 hours''' to become active after enabling it because it requires an Apache restart.
}}

=== Account Resets Remove WSGI Control Access ===

If you had WSGI Control Access on your [[:Morty]] server account for [[:Flask|Flask]] or [[:Django|Django]] and you want this re-enabled after the 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.

=== Account Resets Remove Addon Domains ===

If you had [[:Addon_Domains | additional domains]] on your account, you will need to re-request them after the reset has been completed.

== VPS Rebuilds ==

Due to certain users abusing our generosity in the past and requesting 50 or so rebuilds in less than a month, we now limit each VPS to '''1 free rebuild per month''' with the option to [[#Purchasing_Additional_VPS_Rebuilds | donate for additional VPS rebuilds]] if needed.

=== How do I request a VPS rebuild? ===

Because rebuilding a VPS is destructive, we have to verify your identity before we do so. This is to prevent someone from pretending to be you and deleting all your data.

To request that we rebuild your VPS, send an email '''from the same email address as your VPS account''' to 'support@heliohost.org' so we can verify your identity and rebuild your VPS. If you would like a free dashboard (Hestia, KeyHelp, etc.) installed after the rebuild, please include this in the request.

Alternatively, you can make a post on the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] from a forum account with the same email address as your VPS account. If you're not sure what email address is associated with your VPS account, you can check by logging into the [https://heliohost.org/login/ VPS Dashboard] with your VPS Username and Password. The email address attached to your VPS account will be displayed at the top right of the page.

=== Purchasing Additional VPS Rebuilds ===

If you need to purchase an additional VPS rebuild, please use the link below to donate $1 USD:

[https://www.paypal.com/ncp/payment/6Z88J5KJZJ3RJ Donate $1 USD for VPS Rebuild]

After you have made the donation, please provide your [[#Providing_PayPal_Transaction_ID|PayPal Transaction ID]] as part of your VPS rebuild request, so the donation can be verified.

== 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].

== How do I change the contact email address on my account? ==

We recommend using a reliable external email address for your contact address because if you lose access to your HelioHost account, the contact email is the only way you have of recovering your account. If that email is hosted by us, you likely won't be able to access it either.

To change the email address on your account, login and go to: '''Plesk > Account > My Profile > General > External email address'''

When you change your email address it may take '''up to 2 hours''' to sync to the main website. In the meantime, login with your username (not email) on the main [https://heliohost.org/ heliohost.org] website. After a couple hours you should be able to login with either your username or your new external email address.

== How do I delete my hosting account? ==

To delete your HelioHost Plesk account, go to your dashboard and click on the [https://heliohost.org/dashboard/delete/ Delete your account and remove all content] button.

To delete your HelioNet Forum account, post a topic in the [https://helionet.org/index/forum/4-contact-helionet/?do=add Contact HelioNet forum].

== How do I change my main domain? ==

To change the main domain on your HelioHost Plesk account, 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 domain name''' you want as your main domain, '''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.)

{{Caution|There is a risk of data loss when main domains are changed. We strongly recommend you [[:Account_Backups#Making_Your_Own_Manual_Account_Backup|create an account backup]] and '''download the backup to your local machine''' before requesting a main domain change. As mentioned in our [[:Terms|Terms of Service]], it is not HelioHost's responsibility to keep backups of your data.}}

As an alternative to changing your main domain, consider using [[:Parked_(Alias)_Domains|Parked (Alias)]], [[:Addon_Domains|Addon]], and/or [[:Subdomains|Subdomains]].

== What are the nameservers for HelioHost? ==

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

== What IP addresses should I add to my DNS? ==

To add A (IPv4) or AAAA (IPv6) records to your domain registrar's dashboard, follow these steps to view the IP addresses for your server:

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

== The server is slow / Feature XYZ doesn't work / Something's wrong with my account / etc. ==

Please post the issue in the [https://helionet.org/index/forum/45-customer-service/ Customer Service forum] and we will try to solve the problem. Also, in order for us to provide the best and most efficient support, please provide your '''username''', '''domain name''', '''server name''', and any '''error messages''' you are encountering.

== Can Feature XYZ be installed? ==

Softaculous [https://helionet.org/index/topic/59683-softaculous-has-returned/ returned in March 2024] and is offered on our [[:Morty|Morty]], [[:Tommy|Tommy]] and [[:Johnny|Johnny]] servers, making it possible to install the latest version of 459 different software packages with just a single click.

To browse the available options, login to Plesk and select Softaculous from the menu:

[[File:softaculous_menu_item.png]]

If you need a system-wide feature installed, please post a request in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and any applicable '''version numbers'''.

== Can I use SSH? ==

On hosting accounts, secure shell access (SSH) is disabled for security reasons.

However, it is possible to run jailed shell commands using Plesk's [[:Cron_Jobs|Scheduled Tasks (cron jobs)]] feature.

In many cases, SSH is not actually necessary. Please post a request in our our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''the command you want to run''', and we'll be happy to investigate other ways to accomplish the same task without SSH.

If you absolutely require SSH access, you will need a VPS. {{Template:VPSInfo}}

== Can I use proc_open(), exec(), popen(), etc.? ==

These these functions are disabled on our shared hosting servers ([[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]]) for security reasons. If you need to run proc_open(), exec(), popen(), etc., you will need a VPS. {{Template:VPSInfo}}

Our [[:Lily|Lily]] server, which runs Windows Server, has exec() enabled on all PHP versions.

== Does HelioHost support sockets? Which ports are open? ==

Our [[:Morty|Morty]], [[:Tommy|Tommy]], and [[:Johnny|Johnny]] servers have zero inbound ports available to be opened. All ports that are currently open already have services listening, such as 80 http, 443 https, 3306 MariaDB, and 5432 PostgreSQL.

Outbound ports are similar: ports like 80, 443, 3306, 5432, 25, 465, etc., are open to allow scripts to connect to common services on remote servers.

If you can proxy your websocket through Apache or Nginx, it can work without opening a port:
* You could use an '.htaccess' file to proxy the websocket connection through Apache.
* With the help of a root admin, you could get an Nginx proxy set up. To explore this option, please post a request in our [https://helionet.org/index/forum/45-customer-service/ Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and '''details about your websocket application''', and we'll be happy to help.

If you absolutely need a port opened, you'll need to get a VPS, and you will then have all 65535 ports available to open or close as you want. {{Template:VPSInfo}}

== Are directory indexes enabled? ==

Yes. Directory indexes have been enabled by default on the shared hosting servers since late 2024. This is a feature many users have requested over the past few years, but if you don't want directory listings for a folder, simply create an empty 'index.html' file inside it. Please check our [[:Create_Website#Directory_Index | Directory Index]] section for further information.

== Can I change my document root directory? ==

Typically, your domain root directory is 'httpdocs' (or 'public_html' if you were transferred from the old cPanel). Users cannot change the document root themselves inside Plesk.

If you're planning on using Laravel, Plesk offers a way to set the document root yourself, by using the [[:Laravel#Document_Root | Laravel Toolkit]].

If you have a legitimate reason for needing the document root changed, please create a post in our [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum] and make sure to provide your '''username''', '''domain name''', '''server name''', '''the new document root directory you want''', and a '''valid reason''' explaining why you are unable to use your existing document root. The admins will review your request to determine if the change can be made.

== I can login to Plesk, but can't login to SFTP, what do I do? ==

Sometimes the SFTP and Plesk passwords get out of sync. Please try changing the SFTP password by following these steps:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Connection Info > System user credentials > Click the 'edit icon' next to password'''

== How do I stop my Node.js app? ==

Node tutorials found elsewhere on the internet probably assume you have a VPS (not shared hosting) and you'll quickly get suspended for [[:Suspension_Policy#High_Server_Usage|high server usage]].

If you need to stop a Node process that is already running, deleting the Node.js files via the file manager will '''not''' stop already running processes.

To stop an already running Node.js process, you should disable Node by following the steps below:

'''Login > Continue to Plesk > Websites & Domains > [domain] > Get Started > Node.js > Disable Node.js'''

If you follow our [[:Node.js|Node.js guide]], it will use Passenger which automatically stops Node.js processes if your website isn't getting any visitors. This will help try to keep your account within the [[:Suspension_Policy#Account_Load_Limits|account load limits]].

If you do not want to use Passenger, we recommend you upgrade to a VPS. {{Template:VPSInfo}}

== Can I use your services to mine cryptocurrency? ==

No. We do not allow mining on any of our plans (free or paid).

== Your hosting SUCKS! So do YOU!!! ==

Please see [http://helionet.org/index/topic/4723-suspended/page__p__46231#entry46231 this].

== I still have a question about HelioHost. ==

Post in the [https://helionet.org/index/forum/48-questions/ Questions forum] and we'll try to help you the best we can.

SSL Certificate Problems

2025-11-26T00:22:02Z

KazVee: Add note about Wildcard certificates not being supported

== SSL Certificate Problems ==

== Installing a Let's Encrypt SSL Certificate ==

=== Navigate to the Let's Encrypt Settings ===

Navigate to the Let's Encrypt settings using the steps below:

'''Login > Plesk > Websites & Domains > [ domain ] > Dashboard tab > Security section> SSL/TLS Certificates button > Let's Encrypt settings'''

=== Install the Certificate ===

Click on the 'Install' button.

[[File:ssl-install.png]]

=== Select Certificate Options ===

In addition to selecting the `Secure the domain name` option, we also recommend selecting the following options:
* Include a "www" subdomain for the domain and each selected alias.
* Secure webmail on this domain.
* Assign the certificate to the mail domain.

'''Note:''' Securing webmail cannot be done during the 2 hours following domain creation, because it requires an Apache restart. Apache restarts every 2 hours, so if you're setting up SSL on a brand new account or a new domain that's just been added, you will need to return to these settings later to activate the webmail security feature.

Click on the 'Get it free' button to install the certificate.

[[File:ssl-get-cert.png]]

You should see that 'Keep websites secured' is now 'Enabled'.

We also recommend activating the 'Redirect from http to https' option.

[[File:ssl-check-settings.png]]

==== Wildcard Certificates ====

HelioHost does not currently support Wildcard certificates, due to a lack of integration between Plesk and our DNS. We cannot change this setting, so please disregard the message in Plesk suggesting your hosting provider can fix it. Wildcard SSL is actually less secure than installing a certificate on each domain. We recommend installing a certificate on each domain instead.

== Troubleshooting ==

If you have issues with the Let's Encrypt SSL certificate on your domain or subdomain, here are some things to check:

== Check if the Certificate is Expired or Invalid ==

If the certificate is expired or invalid:

* Reissue the certificate.
* Wait '''a full 2 hours'''.
* [[:Clear_Your_Cache|Clear your cache]] to ensure the changes are applied correctly.

== If the Certificate is NOT Expired ==

If the certificate is not expired:

* Unassign the certificate from the domain.
* Reassign the certificate to the domain.
* Wait '''a full 2 hours'''.
* [[:Clear_Your_Cache|Clear your cache]] to ensure the changes are applied correctly.

== Ensure Redirect HTTP to HTTPS is Off ==

If you can't issue a new certificate it might be because your website is redirecting to https. The verification file required to install SSL must be served over http, and if your website redirects to https the install will fail. Make sure you don't have a redirect to https in your .htaccess file, or make an exception to allow the .well-known directory to be served over http.

<pre>
# redirect to https but allow http on .well-known
RewriteCond %{HTTPS} !=on
RewriteCond %{THE_REQUEST} !/.well-known/(.*)$ [NC]
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</pre>

Plesk can also redirect to https. To disable this redirect:

* Login at [https://heliohost.org/login/ heliohost.org].
* Continue to Plesk.
* Websites & Domains.
* Hosting & DNS.
* Hosting.
* Uncheck the option Redirect visitors from HTTP to HTTPS.

[[File:redirect_http_to_https.png]]

After ensuring that neither .htaccess or Plesk redirect to https try issuing SSL again.

== Further Support ==

If after following the above steps, waiting '''a full 2 hours''', and [[:Clear_Your_Cache|clearing your cache]], the problem is not fixed, please post a topic in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum]. Make sure you provide your '''username''', '''domain name''', and any '''error message(s)''' received.

SSL Certificate Problems

2025-11-26T00:13:52Z

KazVee: Fix numbered headers

== SSL Certificate Problems ==

== Installing a Let's Encrypt SSL Certificate ==

==== Navigate to the Let's Encrypt Settings ====

Navigate to the Let's Encrypt settings using the steps below:

'''Login > Plesk > Websites & Domains > [ domain ] > Dashboard tab > Security section> SSL/TLS Certificates button > Let's Encrypt settings'''

==== Install the Certificate ====

Click on the 'Install' button.

[[File:ssl-install.png]]

==== Select Certificate Options ====

In addition to selecting the `Secure the domain name` option, we also recommend selecting the following options:
* Include a "www" subdomain for the domain and each selected alias
* Secure webmail on this domain
* Assign the certificate to the mail domain

'''Note:''' Securing webmail cannot be done during the 2 hours following domain creation, because it requires an Apache restart. Apache restarts every 2 hours, so if you're setting up SSL on a brand new account or a new domain that's just been added, you will need to return to these settings later to activate the webmail security feature.

Click on the 'Get it free' button to install the certificate.

[[File:ssl-get-cert.png]]

You should see that 'Keep websites secured' is now 'Enabled'

We also recommend activating the 'Redirect from http to https' option

[[File:ssl-check-settings.png]]

== Troubleshooting ==

If you have issues with the Let's Encrypt SSL certificate on your domain or subdomain, here are some things to check:

== Check if the Certificate is Expired or Invalid ==

If the certificate is expired or invalid:

* Reissue the certificate
* Wait '''a full 2 hours'''
* [[:Clear_Your_Cache|Clear your cache]] to ensure the changes are applied correctly

== If the Certificate is NOT Expired ==

If the certificate is not expired:

* Unassign the certificate from the domain
* Reassign the certificate to the domain
* Wait '''a full 2 hours'''
* [[:Clear_Your_Cache|Clear your cache]] to ensure the changes are applied correctly

== Ensure Redirect HTTP to HTTPS is Off ==

If you can't issue a new certificate it might be because your website is redirecting to https. The verification file required to install SSL must be served over http, and if your website redirects to https the install will fail. Make sure you don't have a redirect to https in your .htaccess file, or make an exception to allow the .well-known directory to be served over http.

<pre>
# redirect to https but allow http on .well-known
RewriteCond %{HTTPS} !=on
RewriteCond %{THE_REQUEST} !/.well-known/(.*)$ [NC]
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</pre>

Plesk can also redirect to https. To disable this redirect:

* Login at [https://heliohost.org/login/ heliohost.org]
* Continue to Plesk
* Websites & Domains
* Hosting & DNS
* Hosting
* Uncheck the option Redirect visitors from HTTP to HTTPS

[[File:redirect_http_to_https.png]]

After ensuring that neither .htaccess or Plesk redirect to https try issuing SSL again.

== Further Support ==

If after following the above steps, waiting '''a full 2 hours''', and [[:Clear_Your_Cache|clearing your cache]], the problem is not fixed, please post a topic in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Support forum]. Make sure you provide your '''username''', '''domain name''', and any '''error message(s)''' received.

MediaWiki:Sidebar

2025-11-22T03:33:27Z

KazVee: Rename link from MySQL to MariaDB

Morty

2025-11-22T03:31:35Z

KazVee: Rename link from MySQL to MariaDB

== 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 ==

{{Info|There is a '''$5 minimum''' for prepay balance increases.}}

To add funds to your Morty account, go to [https://heliohost.org/donate/ heliohost.org/donate] and type in the amount ('''at least $5''' or more) that 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]]
* [[:MariaDB|MariaDB]], the fully free, fully open source version of MySQL
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Django]] (with option to request WSGI Control Access)
* [[:Flask]] (with option to request WSGI Control Access)
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]
* Multiple Accounts are allowed on Morty. (Note: Each account must be registered with a different email address.)

Plesk Features

2025-11-22T03:30:55Z

KazVee: Rename link from MySQL to MariaDB

== Plesk ==

== What is Plesk? ==

Plesk is a powerful, yet user-friendly hosting account dashboard. Plesk has a simple-to-use interface that makes editing your hosting details extremely easy.

== What can Plesk do? ==

With Plesk, which is included with all HelioHost hosting accounts, you can:

* Install Blog, Forum, CMS, or other software with the [[:Softaculous|Softaculous]] auto-installer service
* Install software using Plesk Applications Installer ('''Plesk > Applications''')
* Update your HelioHost account information (email address / password)
** '''[https://heliohost.org/login/ Login] > Plesk > Account > My Profile > General > External email address and/or Password'''
*** '''Note:''' When you change your email address it may take '''up to 2 hours''' to sync to the main website. In the meantime, login with your username (not email) on the main [https://heliohost.org/ heliohost.org] website. After a couple hours you should be able to login with either your username or your new external email address.
* Create and manage FTP accounts for access using [[:Uploading_Files|external FTP clients]] ('''Plesk > Websites & Domains > [domain] > Dashboard tab > Connection Info for FTP, Database''')
* Use the built-in Plesk File Manager ('''Plesk > Files''')
* [[:View_Error_Logs|View error logs]] for your site
* [[:Password_Protect_a_Directory|Password protect directories]] on your site
* Create [[:MariaDB|MariaDB]]/[[:PostgreSQL|PostgreSQL]] databases/users
* Edit SQL tables using [[:MariaDB#Managing_the_database_with_phpMyAdmin|phpMyAdmin]] ('''Plesk > Databases''')
* Create and manage [[:Unlimited_Email_Accounts|unlimited email accounts]] for your domain(s)
* Check webmail using the preinstalled [[:Unlimited_Email_Accounts#RoundCube|RoundCube web interface]], or install [[:Unlimited_Email_Accounts#SquirrelMail_and_AfterLogic|SquirrelMail]] or [[:Unlimited_Email_Accounts#SquirrelMail_and_AfterLogic|AfterLogic]]
* [[:Unlimited_Email_Accounts|Set-up e-mail clients]] (such as Outlook, Gmail, Thunderbird, or iOS Mail on iPhone/iPad) for use with your e-mail addresses (through POP3/SMTP)

== How do I access Plesk? ==

To access Plesk, log in to the HelioHost website at [https://heliohost.org/ heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] and click on the Plesk button.

{{Caution|
We strongly recommend that you '''do not''' bookmark your Plesk dashboard URL. Using the Plesk URL without first logging in at [https://heliohost.org/ heliohost.org] or [https://heliohost.org/login/ heliohost.org/login] will not track your logins and risks your account being [[:Suspension_Policy#Inactivity_Policy|suspended for inactivity]] after 30 days.
}}

Tommy

2025-11-22T03:29:40Z

KazVee: Rename link from MySQL to MariaDB

== 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 $2 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]]
* [[:MariaDB|MariaDB]], the fully free, fully open source version of MySQL
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Django]]
* [[:Flask]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

Johnny

2025-11-22T03:29:20Z

KazVee: Rename link from MySQL to MariaDB

== 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]]
* [[:MariaDB|MariaDB]], the fully free, fully open source version of MySQL
* [[:Node.js|Node.js]]
* [[:Perl|Perl]]
* [[:PHP|PHP]]
* [[:PostgreSQL|PostgreSQL]]
* [[:Python|Python]]
* [[:Django]]
* [[:Flask]]
* [[:Ruby_on_Rails|Ruby on Rails]]
* [[:Softaculous|Softaculous]]

Converting an Existing Django App

2025-11-22T03:28:21Z

KazVee: Add link to new MariaDB page

== 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|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[#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 [[:MariaDB|MariaDB]], MySQL, [[:PostgreSQL|PostgreSQL]], and [[:SQLite|SQLite]] database engines.

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and you do not need to request it.

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 you have checked''' the list of modules 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]. Make sure you provide:
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 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. 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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== 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].

[[Category:Tutorials]]

Django on HelioHost

2025-11-22T03:27:52Z

KazVee: Add link to new MariaDB page

== Django 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|To check if a module is already installed, use the '''View''' link for the server and Python version of your choice, and then press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server.}}

{| 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
|}

=== Running Django on a Different Python Version ===

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

== 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 [[:Django_on_HelioHost#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]].
}}

== Complete Django ==

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

== Additional Libraries ==

{{Caution|
Before requesting additional modules, make sure you check the list of modules already installed.

When viewing the list of Python modules already installed, press '''Ctrl + F''' to search the page for a module name. If there is a result, this means the module is already installed on the server and you do not need to request it.

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 you have checked''' the list of modules 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]. Make sure you provide:
# Your account username.
# Your server.
# The version of Python you're using.
# The module(s) you need, including any specific version numbers.

== 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.

== Getting started with Django on HelioHost ==

This brief tutorial will guide you through setting up a Django test app without using the command line on your development system.

If you already have an existing Django app or prefer to use the command line, our tutorial on [[:Converting_an_Existing_Django_App|Converting an Existing Django App]] may better suit your needs.

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

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 'djangotest' directory 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>

== Create another 'djangotest' directory within the first 'djangotest' directory ==

This directory structure 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' is being used in this example.

== Create a 'dispatch.wsgi' file inside the second 'djangotest' 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.

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"}}

<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>

== Create a '__init__.py' file inside the second 'djangotest' directory ==

This file should remain empty.

== Create a 'urls.py' file inside the second 'djangotest' directory with these contents: ==

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

== Create a 'settings.py' file inside the second 'djangotest' directory with these contents: ==

<pre>
from pathlib import Path
# Build paths inside the project like this: BASE_DIR / 'subdir'.
BASE_DIR = Path(__file__).resolve().parent.parent
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/4.1/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'django-makeyoursecretbetterthanthis'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = ['*']
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
]
ROOT_URLCONF = 'djangotest.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
],
},
},
]
WSGI_APPLICATION = 'djangotest.wsgi.application'
# Database
# https://docs.djangoproject.com/en/4.1/ref/settings/#databases
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': BASE_DIR / 'db.sqlite3',
}
}
# Password validation
# https://docs.djangoproject.com/en/4.1/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/4.1/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.1/howto/static-files/
STATIC_URL = 'static/'
# Default primary key field type
# https://docs.djangoproject.com/en/4.1/ref/settings/#default-auto-field
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
</pre>

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

<pre>
djangotest/
├── djangotest
│ ├── dispatch.wsgi
│ ├── __init__.py
│ ├── settings.py
│ └── urls.py
└── .htaccess
1 directory, 5 files
</pre>

== Visit Your Site ==

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 on the [[:Morty]] server only is the ability for users to restart their Django 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].

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 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]. Make sure to provide:
# Your username.
# Confirmation that you are on the Morty server.
# Confirmation that you have already created a 'dispatch.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 Django 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 '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 ==

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 ==

=== 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 upgrade to a VPS to get rid of the error. {{Template:VPSInfo}}

== 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.

== References ==

This tutorial is adapted from [https://helionet.org/index/topic/53855-how-to-use-django-on-plesk/ this post].

[[Category:Tutorials]]

Plesk

2025-11-22T03:26:52Z

KazVee: Rename link from MySQL to MariaDB

== How to Access Plesk ==

== What is Plesk? ==

Plesk is a control panel that enables you to easily manage your websites, applications, and other aspects of your hosting account.
Plesk offers a built-in [[:Uploading_Files#Plesk_File_Manager|File Manager]], [[:Unlimited_Email_Accounts|Email]], [[:MariaDB|MariaDB Databases]], [[:Softaculous|Softaculous]] (an auto-installer service for CMS, Forum, or Blog software), and more.

== How to Access Plesk ==

== Access over HTTPS (Port 8443) ==

The usual way to access your Plesk control panel is over HTTPS (Hypertext Transfer Protocol Secure). Plesk uses Port 8443 for this.

To access your Plesk control panel, navigate to [https://www.heliohost.org/login/ heliohost.org/login] or [https://www.heliohost.org/ heliohost.org] and enter your account details.

Using the above links will ensure that your logins are counted, removing the risk of your account being [[:Suspension_Policy#Inactivity_Policy|suspended due to inactivity]].

== Access over HTTP (Port 8880) ==

If your firewall blocks Port 8443, you can use Port 8880 which is the [https://docs.plesk.com/en-US/obsidian/administrator-guide/plesk-administration/ports-used-by-plesk.64950/ port Plesk uses] for HTTP access.

After trying to login at [https://heliohost.org/login/ heliohost.org/login], simply click the "insecure login" button at the bottom of the page.

{{Caution|We highly recommend logging in to Plesk securely with encryption enabled. So only use Port 8880 when you absolutely have no other way of connecting.}}

== Troubleshooting ==

If you cannot login to Plesk, there are a few common reasons:

== New Accounts ==

It can take '''up to 2 hours''' for your account to be fully active.

If you have just created your account, it can take '''up to 2 hours''' for your account to be fully active. In the meantime, you may not be able to login to Plesk, and your website may not load or display correctly. Please be patient and wait for the full 2 hours before assuming anything is broken.

== Check Account Activation Status ==

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

If after '''a full 2 hours''', you still see a message saying 'HelioHost Account Queued', please [[:Clear_Your_Cache|clear your cache]].

== Multiple Accounts ==

On HelioHost's [[:Tommy|Tommy]] or [[:Johnny|Johnny]] servers, each person/user is only allowed '''one account'''. Multiple accounts on Tommy or Johnny [[:Suspension_Policy#Duplicate_Accounts|will be suspended]].

Users who want multiple accounts are welcome to create them on our [[:Morty|Morty]] server. Please note that each Morty account must be registered with a different email address.

== Inactive Accounts ==

If it has been 30 days or more since your last Plesk login, your [[:Tommy|Tommy]] or [[:Johnny|Johnny]] account was likely [[:Suspension_Policy#Inactivity_Policy|suspended due to inactivity]].

To activate a suspended account which was suspended due to inactivity, go to [https://www.heliohost.org/renew/ heliohost.org/renew].

== Further Support ==

If none of the above reasons apply to you and you cannot access Plesk, please create a new post in the [https://helionet.org/index/forum/81-suspended-and-queued-accounts/?do=add Customer Service forum], making sure to provide your '''username''', '''domain name''', '''server name''', and any '''error message(s)''' received.

What HelioHost Offers

2025-11-22T03:25:55Z

KazVee: Rename link from MySQL to MariaDB

== What HelioHost Offers ==

== HelioHost offers free web hosting for all. ==

== Every account includes: ==

* Access to [[:Plesk_Tutorials|Plesk]]
* Users can create, download, and schedule [[:Account_Backups|Account Backups]]
* Ability to edit [[:Manage_HelioHost_DNS#Edit_A,_CNAME,_TXT,_and_MX_records|A, CNAME, TXT, and MX records]]
* [[:Storage|1000 MB of Disk Space]] (with the option to [[:Donations_for_Increased_Storage|donate for increased storage of up to 7000 MB total]])
* [[:Unlimited_Email_Accounts|Unlimited Email Accounts]]
* Ability to [[:Unlimited_Email_Accounts#SPF,_DKIM,_and_DMARC_Records|set up SPF, DKIM, and DMARC records]]
* Unlimited Mailing Lists
* [[:Unlimited_Bandwidth|Unlimited bandwidth]]
* Up to 10 domains ([[Addon_Domains|Addon Domains]], [[:Subdomains|Subdomains]], and [[Parked_(Alias)_Domains|Parked (Alias) Domains]]) on the [[:Tommy]] and [[:Johnny]] servers, and the option to move to the [[:Morty]] server and create multiple Morty accounts if you need more than 10 domains.
* Unlimited [[:Uploading_Files|FTP]]
* Unlimited [[:MariaDB|MariaDB]] / [[:PostgreSQL|PostgreSQL]] / [[:SQLite|SQLite]] databases
* Access to [[:MariaDB#Managing_the_database_with_phpMyAdmin|phpMyAdmin]]
* Ability to add [[:Perl|Perl]]
* [[:Using_SSL|Free SSL]] with 'SSL It!'
* [[:Softaculous|Softaculous]] for easy installation of popular software such as blogging and forum platforms

== HelioHost accounts can use the following scripting languages: ==

* [[:NET_NET_Core_Classic_ASP|.NET / .NET Core / Classic ASP]]
* [[:Golang|Golang]]
* [[:Java_JSP|Java / JSP]]
* [[:Node.js|Node.js]] (including [[:Express|Express]] and [[:Next.js|Next.js]])
* [[:PHP|PHP]]
* [[:Python|Python]], [[:Django|Django]], and [[:Flask|Flask]]
* [[:Perl|Perl]]
* [[:Ruby_on_Rails|Ruby on Rails (RoR)]]

== HelioHost offers the following paid options for users who outgrow their free account ==

* Ability to [[:Donations_for_Increased_Storage|donate for additional storage]] to a maximum of 7000 MB total.
* Ability to upgrade to our unlimited memory usage, and unlimited CPU usage [https://heliohost.org/morty/ scaling hosting plan].
* Ability to upgrade to a VPS. {{Template:VPSInfo}}

MySQL

2025-11-22T03:24:35Z

KazVee: KazVee moved page MySQL to MariaDB: Renaming 'MySQL' page to 'MariaDB' which is the fully free, fully open source version of MySQL offered on HelioHost

#REDIRECT [[MariaDB]]

MariaDB

2025-11-22T03:24:35Z

KazVee: KazVee moved page MySQL to MariaDB: Renaming 'MySQL' page to 'MariaDB' which is the fully free, fully open source version of MySQL offered on HelioHost

== 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 to Plesk.
# Click on 'Remote MariaDB'.
# Put a percent sign '%' for all IP or else enter the IP to give access to only that particular IP in the box and click 'Submit'.

== 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.

What HelioHost Offers

2025-11-22T01:23:42Z

KazVee: Update domain limits to note 10 max on Tommy and Johnny, also 10 max per Morty account with the option to have multiple Morty accounts

== What HelioHost Offers ==

== HelioHost offers free web hosting for all. ==

== Every account includes: ==

* Access to [[:Plesk_Tutorials|Plesk]]
* Users can create, download, and schedule [[:Account_Backups|Account Backups]]
* Ability to edit [[:Manage_HelioHost_DNS#Edit_A,_CNAME,_TXT,_and_MX_records|A, CNAME, TXT, and MX records]]
* [[:Storage|1000 MB of Disk Space]] (with the option to [[:Donations_for_Increased_Storage|donate for increased storage of up to 7000 MB total]])
* [[:Unlimited_Email_Accounts|Unlimited Email Accounts]]
* Ability to [[:Unlimited_Email_Accounts#SPF,_DKIM,_and_DMARC_Records|set up SPF, DKIM, and DMARC records]]
* Unlimited Mailing Lists
* [[:Unlimited_Bandwidth|Unlimited bandwidth]]
* Up to 10 domains ([[Addon_Domains|Addon Domains]], [[:Subdomains|Subdomains]], and [[Parked_(Alias)_Domains|Parked (Alias) Domains]]) on the [[:Tommy]] and [[:Johnny]] servers, and the option to move to the [[:Morty]] server and create multiple Morty accounts if you need more than 10 domains.
* Unlimited [[:Uploading_Files|FTP]]
* Unlimited [[:MySQL|MySQL]] / [[:PostgreSQL|PostgreSQL]] / [[:SQLite|SQLite]] databases
* Access to [[:MySQL#Managing_the_database_with_phpMyAdmin|phpMyAdmin]]
* Ability to add [[:Perl|Perl]]
* [[:Using_SSL|Free SSL]] with 'SSL It!'
* [[:Softaculous|Softaculous]] for easy installation of popular software such as blogging and forum platforms

== HelioHost accounts can use the following scripting languages: ==

* [[:NET_NET_Core_Classic_ASP|.NET / .NET Core / Classic ASP]]
* [[:Golang|Golang]]
* [[:Java_JSP|Java / JSP]]
* [[:Node.js|Node.js]] (including [[:Express|Express]] and [[:Next.js|Next.js]])
* [[:PHP|PHP]]
* [[:Python|Python]], [[:Django|Django]], and [[:Flask|Flask]]
* [[:Perl|Perl]]
* [[:Ruby_on_Rails|Ruby on Rails (RoR)]]

== HelioHost offers the following paid options for users who outgrow their free account ==

* Ability to [[:Donations_for_Increased_Storage|donate for additional storage]] to a maximum of 7000 MB total.
* Ability to upgrade to our unlimited memory usage, and unlimited CPU usage [https://heliohost.org/morty/ scaling hosting plan].
* Ability to upgrade to a VPS. {{Template:VPSInfo}}