Since you are using WebFaction, have you confirmed that the request is actually getting through to the backend Apache by looking at the access log. Maybe it is actually failing at the front end they use for static file serving and proxying through to the backend.
I would suggest you go back to trying a hello world program first and if still have problems following steps in: http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide then ask on the WebFaction forums at: http://forum.webfaction.com/ as possibly more to do with their specific hosting arrangements and how you have configured it for their setup. Graham 2009/3/14 <[email protected]>: > I am just requesting the main site so, /. No errors in the apache log > except, page not found. It is an apache 404 response. > > I am using DEBUG in django but it does not even get to django. I am thinking > I completely botched the wsgi file so that it is not displaying anything > because no pages can be found to serve. > > I went through the entire Configuration of Django with mod_wsgi on the > modwsgi.org page and I can't seem to get it to display anything. Some of the > commands listed in the configuration page would not work in the httpd.conf > file, such as, Alias and AliasMatch. > > > > On Mar 13, 2009 4:20pm, Graham Dumpleton <[email protected]> wrote: >> >> >> >> 2009/3/14 branesks [email protected]>: >> >> >> > >> >> >> > I am trying to deploy pinax 0.5.1 on Webfaction. I have installed >> >> >> > django 1.0.2 and mod_wsgi 2.0. I have pinax on the server. I have >> >> >> > configured the settings.py file and manage.py. I was able to >> >> >> > successfully run syncdb and it created all of my tables. I seem to be >> >> >> > running into the problem between there and the wsgi configuration. >> >> >> > >> >> >> > Here is my httpd.conf and urls.py. http://dpaste.com/hold/13944/ >> >> >> >> >> >> You don't say what URL you are requesting. You don't say if there was >> >> >> any error messages in Apache error log. You don't say whether the 404 >> >> >> response is an Apache 404 response or a Django 404 response. >> >> >> >> >> >> If not already setting DEBUG in Django settings file do so, in case it >> >> >> is Django that is the issue here. It might then show more useful >> >> >> information in its 404 response. >> >> >> >> >> >> Graham >> >> >> >> >> >> >> >> >> >> >> >> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
