New Project 403 Forbidden Error

[Bestrafung]

I have been following these guides to setup Django on a CentOS cPanel server: http://forums.cpanel.net/f5/django-python-cpanel-71229-p2.html#post439009 and http://blog.perplexedlabs.com/2008/11/10/setup-python-25-mod_wsgi-and-django-10-on-centos-5-cpanel/. After following those guides everything would appear to be working normally except that when I visit the page I receive the Django 403 error specified in the vhost.conf file. I have checked folder and file permissions and everything appears to be correct. The guides said after following those steps I should have a working Django install. Am I missing something? Any help would;d be greatly appreciated.

[Amyth Arora]

What View are you getting the error on ? can you post the code to the View and the template ?

Thanks & Regards
----------------------------

Amyth [Admin - Techstricks]
Email - aroras....@gmail.com, ad...@techstricks.com
Twitter - @mytharora
http://techstricks.com/

[Bestrafung]

Ok, I'm very new to all of this. I assumed following that guide would give me a basic working setup including some kind of "default" or starting pages/templates. If I understand correctly I have to create some kind of pages and/or templates still. I'm trying to figure that out now.

[John Yeukhon Wong]

Just a quick question. Is is possible for you to manually setup this without bothering cpanel?
I mean u should have access to CentOS (ssh into it) right?

Then the setup should be very easy if you have that. I will use Nginx + gunicorn if you really have that option. I want to make sure you do without bothering these custom setup. Note that blog post is from 2008 and at the time there were very little tools usable for Django.

[Bestrafung]

I could probably set it up outside of cPanel but ultimately once I get it working and learn it I want to set it up for multiple accounts. Better to pound my head against the bugs and figure them out now, I think. I've noticed that if I run the built-in development web server the project seems to run fine on it's bound port. Does the built-in dev server provide it's own startup page or is that loaded from the Django testproject? It's basically just a page that says Django is setup and now needs to be customized or whatever. I'm fighting dependencies on another issue at the moment so I can't fire up the dev server again yet. I'm wondering if there isn't just a permissions or config error with the mod_wsgi. I know the guide was from 2008 and I kept that in mind as I made my way through checking for updated files and dependencies, while keeping as close to the guide as possible. I could have done a Python 2.7 setup with some extra work but I stayed with 2.5 following the guide for example.