On May 10, 10:42 pm, Ivan Uemlianin <i...@llaisdy.com> wrote:
> Dear All
>
> The nginx/fastcgi set up is now working (there's an easy-to-follow
> howto on the django advent site [1]).
>
> Embarrasingly I may have stumbled upon what was getting me 403s with
> mod_wsgi, and it's nothing to do with apache or mod_wsgi.  After
> setting up nginx with fastcgi I got the same 403.  Although the
> "mysite" directory and everything under it had permissive permissions,
> the user's home directory was 700:
>
> /home/siteuser/mysite/    775
> /home/siteuser/           700
>
> I changed the latter to 775 to and everything went smoothly.  I didn't
> test it but apache/mod_wsgi will probably work too now.  Doh!

Which is exactly what you were told to check on the mod_wsgi list back
on the 3rd May. :-(

I will quote again exactly what you were told:

"""
But are all the directories from that point all the way back up to
root file system also readable/searchable to Apache user.

If for example you had this stuff somewhere under your home directory
and your home directory was rwxr-x--- you will have issues, albeit
different error to what you are seeing.
"""

So, was wrong that may have shown as different error, but you were
told to check it all the same.

Graham

> @Tom thanks for your suggestion.  When I used to use apache (LOL) I
> would generally have the django app outside of DocumentRoot.  I think
> changing permissions as above would fix things.  Otherwise I don't see
> why an apache config set up that works on ubuntu would raise 403s on
> centos (just checked: on the ubuntu machine /home/siteuser/ was 775).
>
> Best wishes
>
> Ivan
>
> [1]  http://djangoadvent.com/1.2/deploying-django-site-using-fastcgi/
>
> On May 10, 10:25 am, Tom Evans <tevans...@gmail.com> wrote:
>
>
>
>
>
> > On Mon, May 10, 2010 at 9:39 AM, Ivan Uemlianin <i...@llaisdy.com> wrote:
> > > Dear Kenneth
>
> > > Thanks for your suggestion.
>
> > > I tried
>
> > >    $ chmod -R a+x mysite
>
> > > (where mysite is the django site directory)
>
> > > and stopped and started apache, but no effect.
>
> > > I'm finding nginx a lot easier to work with than apache, especially
> > > CentOS' apache.  My plan now is to get rid of apache altogether and
> > > have nginx talk to django directly via fastcgi (e.g., [1]) (will also
> > > give me an excuse to try out git instead of svn).  If you don't hear
> > > back from me in a day or two, it worked.
>
> > > With thanks and best wishes
>
> > > Ivan
>
> > > [1]  http://code.djangoproject.com/wiki/ServerArrangements#nginx
>
> > Good luck with setting up your pure nginx configuration. Your apache
> > configuration did not work because you had not granted apache access
> > to the required on disk folders.
>
> > You didn't mention this in your configuration, but you must allow
> > access to your DocumentRoot in your vhost:
>
> > <VirtualHost *:80>
> >   ServerName foo
> >   DocumentRoot /path/to/foo/htdocs
> >   <Directory /path/to/foo/htdocs>
> >     Order allow,deny
> >     Allow from all
> >   </Directory>
> >   WSGIScriptAlias /app/ /path/to/foo/run/app.wsgi
> > </VirtualHost>
>
> > Cheers
>
> > Tom
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Django users" group.
> > To post to this group, send email to django-us...@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > django-users+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://groups.google.com/group/django-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@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