HTTP AUTH (auth_pam module) Can't initialize threads: error 11

2015-04-09 Thread E.B.
Hello, Using the auth_pam module to implement HTTP AUTH: https://github.com/stogh/ngx_http_auth_pam_module/ Once in a while authentication seems to stop working across all browsers and users. The error that shows in the Nginx error log file when a browser tries to authenticate is: Can't initial

Re: Site should not be accessed through IP

2015-04-09 Thread Daniel Mostertman
If you're using a 1-config-per-site setup, then yes, you could. It completely depends on your setup as to where you need to place it. You can put it in any existing file that already has a server directive in there. Just make sure none of the other server configs/files have the default_server in t

Re: Site should not be accessed through IP

2015-04-09 Thread blason
Hi Finalx, you mean shall I create the .conf file by name default_server and add up this there? Or would you please tell me where shoudl I add the above stanza? Sorry I am being novice in nginx just would like to know more information about this. Posted at Nginx Forum: http://forum.nginx.org/rea

Re: Site should not be accessed through IP

2015-04-09 Thread FinalX
You could use an extra host config with a default_server, like so: server { listen 80 default_server; server_name _; return 444; } You can find this example on http://nginx.org/en/docs/http/server_names.html Posted at Nginx Forum: http://forum.nginx.org/read.php?2,2579

Re: Site should not be accessed through IP

2015-04-09 Thread Sebastian Stabbert
configure a site first, which does the „default“ handling and has no content? Cheers, Sebastian Am 09.04.2015 um 20:09 schrieb blason : > Hi Guys, > > I have my nginx box deployed as a reverse proxy serving almost more than 10 > sites. But when I browse through 1 IP the first site configured

Site should not be accessed through IP

2015-04-09 Thread blason
Hi Guys, I have my nginx box deployed as a reverse proxy serving almost more than 10 sites. But when I browse through 1 IP the first site configured gets accessed. I dont want anyone to access the sites through IP, by using only FQDN sites should be accesible. So anyone trying to access the site

Linux package for Debian "jessie" (8.x)

2015-04-09 Thread Daniël Mostertman
Hi, I've been using the mainline packages with the instructions on http://nginx.org/en/linux_packages.html for a while now, and the Debian section mentions to replace "codename" with the actual codename. On April 25th 2015, Debian will release their new version, codename "jessie". I've been runn

Linux package for Debian "jessie" (8.x)

2015-04-09 Thread Daniël Mostertman
Hi, I've been using the mainline packages with the instructions on http://nginx.org/en/linux_packages.html for a while now, and the Debian section mentions to replace "codename" with the actual codename. On April 25th 2015, Debian will release their new version, codename "jessie". I've been runn

combine basic auth and ip whitelisting load ip dynamicly

2015-04-09 Thread basti
Hello I have config to combine basic auth and ip whitelisting like that: # combine basic auth and ip whitelisting # http://serverfault.com/questions/242218/how-to-disable-http-basic-auth-in-nginx-for-a-specific-ip-range satisfy any; include /etc/nginx/myips; deny all; auth_basic "Re