Re: Upstream server error

2016-10-26 Thread Valentin V. Bartenev
On Wednesday 26 October 2016 09:28:59 Michiel wrote: > Hi > > I'm having issues with Google Endpoints and NGINX. > I keep on getting the following error message: > > 2016/10/26 13:02:09 [error] 15802#0: *1 connect() failed (111: Connection > refused) while connecting to upstream, client: 78.20.2

Re: Encrypting TLS client certificates`

2016-10-26 Thread Maxim Dounin
Hello! On Tue, Oct 25, 2016 at 07:20:00PM -0400, WGH wrote: > When nginx requests a client certificate with ssl_verify_client option, > and client complies, the latter sends its certificate in plain text. > > Although it's just a public part of the certificate, one can consider it > a kind of in

Upstream server error

2016-10-26 Thread Michiel
Hi I'm having issues with Google Endpoints and NGINX. I keep on getting the following error message: 2016/10/26 13:02:09 [error] 15802#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 78.20.209.87, server: , request: "GET /v1 HTTP/1.1", upstream: "http://127

Re: Bug? Chown of all default *_temp_path directories at startup?

2016-10-26 Thread Daniel Aubry
On Tue, 25 Oct 2016 18:10:09 +0300 Maxim Dounin wrote: Hi Maxim > Make sure to define temp paths in all servers, or, better yet, at > http{} level. If you don't redefine them in some context, nginx > will use the default paths compiled in, resulting in the behaviour > you've observed. Many