Krydos

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?

There you go https://heliohost.org/eta/?u=atomicbob Thanks for the donation.

Login at https://heliohost.org/login/ > Continue to Plesk > Mail tab on the left > Click email address > Click spam filter tab along the top > Configure your spam prevention rules.

Does it work now?

They've been removed now. If you have a coin that we don't have listed at https://heliohost.org/donate/ we may be accept it and add the wallet to the list. Like Wolstech said privacy coins aren't as easy to convert to USD for us to pay the bills so we discourage their use.

Yes, you can sign up for a VPS at https://heliohost.org/vps/ and they are available immediately.

Yep, you're right. Not sure why it was missing from ns2. As a bonus I created an AAAA record for you in case you want to support IPv6 on your domain. Make sure your webserver knows to respond on 2001:470:1:1ee::15 root@brody [/home/krydos]# dig +short A @ns1.heliohost.org norden.heliohost.us 216.218.228.92 root@brody [/home/krydos]# dig +short A @ns2.heliohost.org norden.heliohost.us 216.218.228.92 root@brody [/home/krydos]# dig +short AAAA @ns1.heliohost.org norden.heliohost.us 2001:470:1:1ee::15 root@brody [/home/krydos]# dig +short AAAA @ns2.heliohost.org norden.heliohost.us 2001:470:1:1ee::15 If you'd rather not deal with IPv6 let me know and I can delete the AAAA records again.

The username is hchang just like the forum account, and the forum email address matches the VPS account too. Your subscription has been canceled and you won't be charged again. Thank you for using our VPS service.

You database has been compressed and emailed to you.

I scoured the logs and it looks like you created your account on 2020-06-13, and then deleted it sometime during the next 5 months before 2020-11-05. We didn't log deletions back then so I don't know the exact date. The only people who are being transferred are people who have active accounts. If you're interested in signing up for a new account I can add you to the waitlist so you'll get an email when signups are available again.

Ubuntu's newest OS has been out for long enough, and enough software supports it that we're going to make it the default choice for new VPS now. If you signup for a VPS please make sure all of your software will work, and if not you can select Ubuntu 20 or any other OS we offer from the custom option during the signup process.

There you go https://heliohost.org/eta/?u=ytmusic You're currently #184 which at the current rate will be about 18 days. Everything seems to be going well though so we may raise the rate of invites.

You can either use our nameservers which are ns1.heliohost.org and ns2.heliohost.org OR You can use any external DNS provider, Cloudflare is a popular free choice, by creating an A record pointed to 65.19.141.77. You're on cPanel currently, but after you're transferred that would the IP address to set. Right now we're moving 10 accounts per day, but we're considering raising that amount. Without a donation you're currently #745 https://heliohost.org/eta/?u=atomicbob in line to be moved over so at 10 invites per day it would take 74 days, or for even just $1 donation it would move you up to October 20th at our current rate. Please note that the rate of invites can be raised or lowered or stopped entirely depending on if we run into any serious issues or if things are going well. So far everything is looking good though.

Ahhh, that's interesting. I've never heard that one before. Glad you got it working.

I reset your password thinking maybe your user was created without wheel privileges, and then tried logging in. login as: huberret huberret@65.19.191.157's password: Last login: Mon Sep 26 07:57:10 2022 from <removed> To run a command as administrator (user "root"), use "sudo <command>". See "man sudo_root" for details. huberret@vps74:~$ sudo su [sudo] password for huberret: root@vps74:/home/huberret# whoami root root@vps74:/home/huberret# The sudo su command works for me. I set your password back to what it was. Maybe try using the passwd command to change the huberret user's password and see if you can do sudo su after that.

Your VPS account has been updated to have the contact email address you DM'd me in addition to your Gmail. When there is a need to contact you we will send an email to both addresses. It's very odd to me that sudo su would work for hundreds of other VPS that we've created using the exact same process for years, and then suddenly doesn't work for you. I guess anything is possible though. I'll take a look.

You're right, the A records for your .com weren't changed correctly. I have fixed them. Due to DNS caching it may take a few hours for the change to propagate through the internet during which time you may still see the old website. You can check https://dnschecker.org/#A/bockowski.com for an idea of how far along the change has gone. 65.19.143.6 is the wrong cPanel ip, 65.19.141.77 is the correct Plesk ip.

What is your username? There was an account named heirloom created in 2017, but the email address of that hosting account doesn't match your disposable email address on this forum account. EDIT: I just noticed this was posted 7 months ago. Not sure why the forum just suddenly decided to show it to me as a new unread topic.

Your account has been deleted and I sent an invite to create a new account to your email address you use for this forum account. Let us know if you have any issues.

Great news! We are now sending out invites to donors again starting immediately. We started sending new account creation invites using slightly modified cPanel code a while back, but quickly realized that there were too many bugs. We decided to start over entirely and redesign the new account creation process again from the ground up with Plesk in mind. It was a lot more work, but we think it was worth it. The previous cPanel new account creation code has remained largely untouched since it was implemented in 2016, and we created over 100k accounts using that old code. We've learned a lot from our time creating so many accounts, and we hope that the new Plesk code will perform even better. We also have more great news! Gmail has begun delivering our emails instead of deleting them. More often than not the emails end up in the spam box, but if you flag them as not spam future emails will be delivered to the inbox. It's a great step in the right direction, and a lot better than our invites being deleted entirely. If you're not a big fan of email, or you're afraid you'll miss your invite in the spam box you can link your Discord account or improve your position in the queue using the ETA page https://heliohost.org/eta/ All of the HelioHost staff are really excited to be able to create new accounts again, and we're hoping this feature rollout will go smoothly. Once all the donors are on Plesk we will begin moving the free accounts as well. We will start out only sending a few invites per day, but as the new account creation gets well tested we will increase the rate of invites. Now that new account creation is implemented we can turn our attention to other tasks such as getting Django and Flask running on Tommy, setting up Johnny, and adding or deleting domains through Plesk. If you have any issues or have any questions let us know.

You can probably change the permissions of everything to make it work for both users. 644 = read/write by owner, read by group, and read by other. Your colleague's account is going to count as other so if you set the file's permission to 666 he should be able to edit those files. Filezilla has an option to recursively change all file permissions with just a few clicks so that might be the best solution for you. This isn't a Plesk issue, it's a Linux issue. Permissions like this have been in effect in Unix since like the 70s or so. It's a security feature to prevent other users on the same server from altering your files unless you want them to.

DM sent. Are you running sudo su or just sudo?

Yes, we are planning on adding Discord linking to both shared hosting account and VPS. However, Plesk requires an email address on file, and VPS use PayPal for payments so they require an email address on file as well. Once your Discord account is linked to your HelioHost account you will receive all of your notifications via Discord.