Re: Nginx serving self-signed cert instead of the one defined in conf

For the record: problem solved. SHAME on me !! The problem was simply that I copied the wrong certificates from my old installation (nginx 1.6.2) to the new one (nginx 1.8.0). As often, the problem lies in front of the keyboard :-) Thanks Maxim for your assistance in any case, I learnt a few th

Re: Nginx serving self-signed cert instead of the one defined in conf

Hi Maxim, Thanks for your answer. Alas ! I check all config files in my /etc/nginx directory, there's only one containing the server{} directive (for the sake of it, I added the default_server to the listen directive, but it doesn't change anything) : -

Nginx serving self-signed cert instead of the one defined in conf

Hello, I'm facing a strange issue since I upgraded from Nginx 1.6.2 to 1.8.0. My configuration files have been kept identicals, as well as my official SSL certificates. The problem is Nginx keeps on serving a self-signed certificate (dunno where it takes it from) instead of my proper certificates

Re: Satistfy any not working as expected

Thank you ! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,258955,259026#msg-259026 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Satistfy any not working as expected

Hi Maxim, Thanks again for your explanations, they make sense. So I've put back the "deny all;" statement. I get the 403 unauthorized message back. And there's indeed some good indication in the error log, showing that my auth_request script does the job, and then the login page returns the 403 st

Re: Satistfy any not working as expected

Hi Maxim, Thanks for your answer. I'm actually using a proper URI in the auth_request parameter and the PHP script works fine (https://github.com/Arno0x/TwoFactorAuth), my example was dumb. For the records, here's what I did to make it work exactly as I expect: simply remove the "deny all;" state

Satistfy any not working as expected

Hi, I'm facing an issue using the "satisfy any" directive. What I'm trying to achieve is quite simple: - have an auth_request directive protecting the entire website (hence set at the server level in the config file) - have no such authentication for the local network I've put the following lines

Re: auth_request + php-fpm + POST request

ve up. Regards, Arno0x0x Posted at Nginx Forum: http://forum.nginx.org/read.php?2,257968,257996#msg-257996 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

auth_request + php-fpm + POST request

- See the trick ? The auth.php script is being forced a "GET" method even when the client used a POST request. By the way, I didn't manage to get the whole auth_request config working using all the "proxy_pass" stuff. So I used a straight call to the auth.p