Krydos

Glad you got it working!

Since this 6 month payment came from the same email address as the last one the system detected it automatically and updated the expiration date without any work on our part. I did get the email, but I forgot to ever reply. Sorry about that. Regarding India and PayPal, you're definitely not the only one having problems. We've had tons of reports from our Indian users that they've been having trouble sending donations too. We're considering setting up a PayTM account to better serve India. That might work better than PayPal for you too.

Both options work.

Changed.

We've had a few questions about our inactivity policy. VPS accounts are not affected by inactivity at all. As long as your VPS is paid for you don't ever have to login. Also accounts that are on cPanel still aren't affected, and they will remain active until after they are transferred to Plesk. This inactivity only affects users who have created new accounts on Plesk or have been transferred to Plesk already.

Oh, I see what the problem is. Since your donation email address was different from your existing account email address you received a new account invite. The reason the username is blocked is because you have an existing account with that username already. I have linked your donation to your existing Tommy account and sent you a new transfer invite. If you click the link in this new email you can move your existing account to Plesk instead of creating a new account. If you'd prefer to start over fresh with a new account we can delete the existing Tommy account and send you a new account invite instead.

For the last 15 months we have allowed all of our accounts to remain active without logging in. Now that we have a functional control panel and it's possible to login again we need to enable inactivity suspensions again. Starting on October 13th if you haven't logged in for 28 days you will receive an email reminder to login. If you ignore that email for 2 days your website will be taken offline at 30 days and replaced with an inactivity message. We need to have this policy because our server's speed and uptime will be negatively affected if there are too many accounts on the server. Even if your account is small and you barely get any traffic just having the virtualhosts enabled on the server increases the load and causes Apache restarts to take longer. We will be adding a new server named Morty eventually that won't have high load suspensions or inactivity suspensions, so if you don't like having to remember to login that may be a good option for you in the future.

Since emails are being delivered again we've decided to disable this feature for now. We are still planning on allowing people to create new accounts with Discord instead of email though eventually.

Does it work now?

Glad you got it working. Thanks for sharing the solution. Hopefully it will help someone else in the future.

This information is accurate for cPanel, but not for a VPS. Generally on a VPS the default webroot is /var/www/html/ Also make sure you have a a webserver installed to serve your index.html file. By default the VPS is just a bare operating system with nothing installed yet. The two most popular webserver software are Apache and Nginx, but there are others as well. If you're not too familiar with SSH and installing stuff by the command line we can also install a control panel for you so you can administrate your website via a browser. The most popular free control panel for HelioHost users is Hestia. You can install it yourself with the instructions at https://hestiacp.com/ or we can install it for you. Personally I prefer to not have a control panel and rather just installing things on the command line, but a control panel takes care of installing the webserver and a lot of other software that you may or may not need. Let us know if you have any other questions or need help with anything.

It might be because your .com is an alias instead of a full domain? Want me to try removing the alias and readding it as a full domain? Sometimes deleting and adding domains can cause the directories they're linked with to get deleted possibly so make sure you have a backup.

Click the link in the invitation email again and try to signup using the username opieantc now.

There you go https://heliohost.org/eta/?u=mrbuzz1%40me.com I'm not seeing the second donation though. Was it made under a different email address? Do you know the transaction ID for it? If I can find it I can add it to your ETA too. Thanks for the donations.

You can use any of the methods listed at https://heliohost.org/donate/ Regarding PayPal, we're seeing more and more people having issues with it. Since we have users and donors all around the world it would be nice to support some more options other than PayPal. We have a Skrill account, but they keep making it harder and harder to withdraw the money so we might end up closing that account. Some users in India, which is another country that PayPal rarely works in, suggested PayTM to us. Would PayTM work in Indonesia? Do you have any suggestions that would work well for your country?

There you go https://aoferta.com.br/ https://dolitoral.com.br/ and https://juliano.dev.br/ In your home directory there are directories with names matching the domains. Inside each of those directories there will be an index.html file. Just delete that index.html file and upload your website. Let us know if you need help with anything else.

Yes, it's $5 per 1000 MB up to a maximum of 5000 MB, so the first 1000 MB is free and $20 gets you 5000 MB. It's not automatic though so let us know the transaction ID after your account is moved and we can apply the increased storage.

The A records for the kcyan.ml domain have been updated to point at Plesk instead of cPanel.

Here is your updated ETA https://heliohost.org/eta/?u=tchesoen You're currently #200 in line to be moved to Plesk and you should receive your invite on or around October 21st as long as the rate on invites remains the same. Thanks for the donation.

You're fine. Over the last 7 weeks we've averaged 0.91% of our available bandwidth. You can download it as fast as you want and it shouldn't bother anyone.

Django 4.1.1 and Flask 2.2.2 have been installed on Tommy's Python 3.10. We will update the wiki eventually, but for now there are some quick guides on the forums to get you started. If you have any questions or comments please let us know.

We will update our wiki article on how to get started with Flask eventually, but just posting a quick example here so people can comment and ask questions on this thread. Create a directory on your main domain called flasktest. If you were transferred from 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: Options +ExecCGI RewriteEngine On RewriteBase / RewriteRule ^(media/.*)$ - [L] RewriteRule ^(admin_media/.*)$ - [L] RewriteRule ^(flask\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ flasktest/flask.wsgi/$1 [QSA,PT,L] Create a file named flask.wsgi inside the flasktest directory with these contents: 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' Create a file named myapp.py inside the flasktest directory with these contents: import sys from flask import Flask, __version__ app = Flask(__name__) application = app @app.route("/") def hello(): return """ Flask is working on HelioHost.<br><br> <a href="/flasktest/python/version/">Python version</a><br> <a href="/flasktest/flask/version/">Flask version</a> """ @app.route("/python/version/") def p_version(): return "Python version %s<br><br><a href='/flasktest/'>back</a>" % sys.version @app.route("/flask/version/") def f_version(): return "Flask version %s<br><br><a href='/flasktest/'>back</a>" % __version__ if __name__ == "__main__": app.run() Make sure your directory structure and files look like this: flasktest/ ├── flask.wsgi ├── .htaccess └── myapp.py 0 directories, 3 files If you did everything right it should look like this: https://krydos.heliohost.org/flasktest/ *** Please note that since wsgi uses server side caching your changes might not appear immediately, and in some cases might take several hours to update. We recommend developing your Flask app on your home computer and hosting the production copy on the server.

We will update our wiki article on how to get started with Django, but just posting a quick example here so people can comment and ask questions on this thread. Create a directory on your main domain called djangotest. If you were transferred from 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: 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] Next create another djangotest directory within the first djangotest directory. This is the standard directory structure for a Django project so don't give me that look. I'm sure they did it on purpose just to make it more confusing for you. Also you can't name your Django project django either, so don't even bother trying. That's why we're calling this example djangotest. Inside the second djangotest directory make a file named dispatch.wsgi with these contents: import os, sys # edit 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() Make sure you edit the path in the dispatch.wsgi file. On Plesk your path is /home/ and then your main domain, and then httpdocs if you're a new account or public_html if you've been transferred from cPanel. Inside the second djangotest directory create an empty file named __init__.py Inside the second djangotest directory make a file named urls.py with these contents: from django.contrib import admin from django.urls import path urlpatterns = [ # path('admin/', admin.site.urls), ] Inside the second djangotest directory make a file named settings.py with these contents: 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' Make sure your directory structure and files look like this: djangotest/ ├── djangotest │ ├── dispatch.wsgi │ ├── __init__.py │ ├── settings.py │ └── urls.py └── .htaccess 1 directory, 5 files If you did everything right it should look like this: https://krydos.heliohost.org/djangotest/

Your donation has been linked and your ETA can be found at https://heliohost.org/eta/?u=animal You're currently #41 so you should receive your invite on October 5th or so depending on if the rate remains the same. Yes, you will be able to create an account on Tommy now even though you were on Johnny before. Thanks for the donation.

Between install attempts did you fully delete and recreate the database?