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 things on the way. Regards, Arnoby Arno0x0x - Nginx Mailing List - English
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) : --------------------------------------------------------------------------------------------- pi@rpi /etc/nginx $ grep -r server * fastcgi.cby Arno0x0x - Nginx Mailing List - English
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 that I defined in the config file. Here's the server section SSL config bits : --------------by Arno0x0x - Nginx Mailing List - English
Thank you !by Arno0x0x - Nginx Mailing List - English
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 status code. So I added an "allow all;" statement just on the login page whichby Arno0x0x - Nginx Mailing List - English
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;" statement. As a result : - Any local network IP gets a straight access - Any other IP hby Arno0x0x - Nginx Mailing List - English
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 in my nginx config file, under the 'server' directive: --------------------------by Arno0x0x - Nginx Mailing List - English
Hi Maxim, Thanks for your answer. I'll rather do as you said rather than changing the method from POST to GET. As per your recommended example, I never managed to make it work (proxy_pass stuff): I went into some resolver issue, and then into some infinite loop on internal requests. So I gave up. Regards, Arno0x0xby Arno0x0x - Nginx Mailing List - English
Hi, I'm using the auth_request module to enable custom (2fa) authentication to protect my whole website, no matter the various applications I host on this website. So the auth_request directive is set at the "server" level. The authentication subrequest works fine, except for client POST requests where the php auth script holds forever until I get a timeout in the nginx error.log :by Arno0x0x - Nginx Mailing List - English