Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    Instead of the grep you could also use getent group nginx and id nginx. Commented Nov 10, 2014 at 18:20
  • @goldilocks what i will explain now will sound too moronic of me. I had tried what you have suggested before (friday). Developers had complained that nginx was giving forbidden error. Apparently, I had to restart nginx after editing user and group permissions. I just don't know what to say at this point. Speechless. I could never think of that one... Microsoft moment for a while... Commented Nov 10, 2014 at 21:04
  • Whoops, yeah -- forgot to mention you need to log in again for changes like that to take affect. If it is a non-login account, try su nginx and then test permissions. You would then have to restart any processes running as that user (I've added a couple of sentences about this). Commented Nov 10, 2014 at 21:18
  • yeap nginx is a user without shell and home dir so since Friday I have been dealing with its permissions and forgetting to restart the service and flushing privileges (a huge facepalm)... Commented Nov 10, 2014 at 21:57