Nginx Password Protect 403 Forbidden -


i running centos 6 nginx. running perfectly, trying password protect admin directory.i can login. however, 403 forbbiden when try view main index page (index.php) in directory.

2013/04/18 02:10:17 [error] 17166#0: *24 directory index of "/usr/share/ngin/html /somedir/" forbidden, client: xxx, server: mysite.com, request: "get /somedir/ http/1.1",  host: "mysite.com"

i have double checked permissions on ".htpasswd" file. belongs "root:root" chmod 640. have tried setting owner ship "nginx:nginx" , error still persists.

this how getting htpasswd working:

location ~ ^/([^/]*)/(.*) {     if (-f $document_root/$1/.htpasswd) {             error_page 599 = @auth;             return 599;     } }  location @auth {     auth_basic "password-protected";     auth_basic_user_file $document_root/$1/.htpasswd; }

though question pretty old, must put solution here others. problem pain in somewhere.

i have read out (and implemented/tried) possible threads available online (till date) none solved "403 forbidden" nginx issue all-together:

i write down steps beginning: ( block site access ):

1> create hidden file called .htpasswd in /etc/nginx

sudo sh -c "echo -n 'usernamee:' >> /etc/nginx/.htpasswd"

2> add encrypted password given username

sudo sh -c "openssl passwd -apr1 >> /etc/nginx/.htpasswd"

this ask enter password , confirm it.

3> need setup nginx check our newly created .htpasswd before serving content.

location / {         try_files $uri $uri/ /index.php?$query_string; # per configuration          auth_basic "authorized access only";         auth_basic_user_file .htpasswd; }

4> restart server take effect

sudo service nginx restart

now browse url:

please note: didnt alteration in permissions. default file permission htpasswd set @ time of creation, this:

-rw-r--r-- 1 root root 42 feb 12 12:22 .htpasswd


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more