Primary script unknown error - can't figure out how to fix

Steve Holdoway steve at
Tue Jan 8 21:44:42 UTC 2013

In my experience, that's usually caused by access to parent dirs...
ie /home is made unreadable by nginx user when changed to 750 root:root.



On Tue, 2013-01-08 at 22:39 +0100, Patrick Lists wrote:
> On 01/08/2013 09:09 PM, Francis Daly wrote:
> [snip]
> > Set "root" correctly in the nginx config. (Which is more or less the
> > same as "set the directory name correctly in the filesystem".)
> Thanks Francis. Another sharp pair of eyes and mine not so much. The 
> error was introduced when redacting the configs to protect the innocent.
> The root in piwik.conf points correctly to the actual location of the 
> site in /usr/share/nginx. I also tried turning off SELinux but that did 
> not make a difference.
> I can make it work when I chmod all files to 644 and all directories to 
> 755. But I do not understand why that is. If nginx and php-fpm are 
> running as nginx/ningx shouldn't both be able to handle files & dirs 
> owned by nginx/nginx with mode 640 and mode 750?
> Regards,
> Patrick
> _______________________________________________
> nginx mailing list
> nginx at

Steve Holdoway BSc(Hons) MIITP
Skype: sholdowa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6189 bytes
Desc: not available
URL: <>

More information about the nginx mailing list