will do, going through now... i did find this:

# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client.  When set "On", Apache will use the value of the
# ServerName directive.
#
UseCanonicalName Off

should i set this to On?

now... i just took a look at the apache docs and then ran across

http://www.issociate.de/board/goto/915418/NameVirtualHost_xxx:0_has_no_VirtualHosts.html

i went with the IP address and added _default_ and now it appears to
be working, despite a warning "Starting httpd: [Sun Jan 04 18:29:52
2009] [warn] NameVirtualHost 72.167.92.152:80 has no VirtualHosts"

django apps work, however now my style sheet does not

On Jan 4, 6:15 pm, Graham Dumpleton <graham.dumple...@gmail.com>
wrote:
> Go through all the Apache configuration files and find all mentions of
> NameVirtualHost, Listen and SetHandler directives. Post what they are
> here. If SetHandler is inside of a Location/Directory container, post
> what that container directive is declared as. In turn, if they are
> inside of VirtualHost, post what that container directive is as well.
> Show the order of all relative to each other.
>
> In other words, triple check that there are not multiple
> NameVirtualHost directives, or a SetHandler directive at global server
> level which is disabling mod_python inside of VirtualHost. Duplicate
> NameVirtualHost directives is only thing I can think of that could be
> an issue.
>
> BTW, do you have an images directory in the carclubhub DocumentRoot.
> Ie., should it be found by the browser?
>
> Graham
>
> On Jan 5, 9:54 am, garagefan <monkeygar...@gmail.com> wrote:
>
> > I have root access. I've just now attempted both moving the
> > NameVirtualHost *:80 around, from the python.conf to the httpd.conf,
> > and changed its location in the httpd.conf.
>
> > i've also moved the import for the python.conf as well, from above to
> > below the NameVirtualHost and there have been no changes
> > is there possibly something else that needs to be set up for the
> > VirtualHost to work?
>
> > On Jan 4, 5:44 pm, Graham Dumpleton <graham.dumple...@gmail.com>
> > wrote:
>
> > > On Jan 5, 8:54 am, garagefan <monkeygar...@gmail.com> wrote:
>
> > > > Starting httpd: Syntax error on line 1 of /etc/httpd/conf.d/
> > > > python.conf:
> > > > Invalid command 'xxx', perhaps misspelled or defined by a module not
> > > > included in the server configuration
>
> > > > it doesn't appear that anything in the <VirtualHost> is being read,
> > > > but there are no errors popping up related to it. i've change the *:80
> > > > to other numbers and have received errors
>
> > > > On Jan 4, 4:47 pm, Graham Dumpleton <graham.dumple...@gmail.com>
> > > > wrote:
>
> > > > > Where exactly is the snippet file containing the Apache configuration
> > > > > which you have added?
>
> > > > > How is this being included into the main Apache configuration?
>
> > > > > Try adding a syntax error into the snippet file, ie., add:
>
> > > > >   XXX
>
> > > > > Then try and restart Apache. If it doesn't complain with an error in
> > > > > Apache error logs, then the configuration file isn't even being read
> > > > > in.
>
> > > > > If neither site is showing anything, then all I can guess is that the
> > > > > configuration isn't even being used in the first place.
>
> > > The only other thing I can think of is that the order of stuff in main
> > > Apache configuration file, as dictated by where the python.conf
> > > snippet is included, is resulting in some residual configuration
> > > related to configuration of '/' for server taking precedence over the
> > > VirtualHost entries.
>
> > > In all, it is just too hard to tell at this point. Is this a managed
> > > server where you can only modify certain Apache files and then use a
> > > web panel to restart it, or do you have full root access?
>
> > > Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to