Hi Dennis - probably a good idea to submit a new topic if you're running into a specific issue.

The changes described in this thread were made a long time ago and did fix things for me. I do find it sometimes tricky to get things up and running at first, but it's usually related to something other than Ajenti.

I can tell you a bit about my own setup in light of the original post:

• I add a Python WSGI entry on the Content tab of the website:
  • My Application Module is Django's wsgi.py in the project directory, relative to the path set in the General tab for your overall website. In one of my projects my base path is /srv/client/project. My wsgi.py is at /srv/client/project/config/wsgi.py. My entry here is thus "config.wsgi".
  • In Python settings, I set my virtualenv path. This is where Django, Python, gunicorn etc are all installed for this website.
  • Under Advanced I have "Append URL pattern to path (root)" checked
  • You can write python in the Custom configuration textbox under Python, e.g. for environment variables.
• You'd also make entries for static files etc.

See: http://support.ajenti.org/topics/1125-setting-up-a-python-website-with-ajenti-v-django-example/ for some tips here (don't follow the Django setup steps as they look outdated to me, but do consult Setting up Ajenti V onwards).

Logs for Gunicorn will be under the supervisor folder (/var/log/supervisor I think), which is usually the first thing I check if things aren't working. As a sanity check you should also see if Django's runserver command launches or points out errors in your Django app.