Re: input required on proxy_next_upstream

2017-02-17 Thread kaustubh
Thanks for reply. But I checked upstreams and second instance is working fine but does not receive retry request. I did small setup where one upstream instance responds early with 503 and other instance processes requests, and I observe that the request never comes to working upstream server on ea

Re: SSL Passthrough

2017-02-17 Thread agforte
Francis, thank you for your reply. It seems I have fixed the issue. However, I just wanted to say that in stream mode, you can use NGINX as a forward proxy as well. As you mention, in stream mode, NGINX behaves as a "TCP router" in the sense that it just relays segments or packets using the correc

Re: SSL Passthrough

2017-02-17 Thread agforte
up vote 0 down vote accept I have found the problem. It was actually a code issue. I am using Golang. The problem was that I was configuring the Proxy as: *httpsCl = http.Client{ Transport: &http.Transport{ Proxy: http.ProxyURL(proxyUrl), TLSClientConfig: tlsConfig

Re: SSL Passthrough

2017-02-17 Thread Francis Daly
On Fri, Feb 17, 2017 at 02:52:53PM -0500, agforte wrote: Hi there, > I have the following setup: > > PRIVATE SERVER <--> NGINX <--> PUBLIC SERVER > > I need the NGINX server to work as both reverse and forward proxy with SSL > passthrough. That's not going to work without a lot of patching o

Re: input required on proxy_next_upstream

2017-02-17 Thread Igor A. Ippolitov
Could it happen, that all servers reply with HTTP 503? I suggest you could extend your logs with upstream_status variable and if there is only one upstream reply status - try looking through error logs. On 15.02.2017 20:17, Kaustubh Deorukhkar wrote: Hi, We are using nginx as reverse proxy a

SSL Passthrough

2017-02-17 Thread agforte
Hi all, I have the following setup: PRIVATE SERVER <--> NGINX <--> PUBLIC SERVER I need the NGINX server to work as both reverse and forward proxy with SSL passthrough. I have found online the following configuration for achieving this (note that for the forward proxy, I send packets always to

Re: input required on proxy_next_upstream

2017-02-17 Thread Kaustubh Deorukhkar
Hello, Any inputs on this? Is is supported to retry next upstream, if upstream server responds early rejecting request for any valid reason? Thanks, Kaustubh On Wed, Feb 15, 2017 at 10:47 PM, Kaustubh Deorukhkar < kaustubh@gmail.com> wrote: > Hi, > > We are using nginx as reverse proxy and

Re: swapiness value to be set for high load nginx server

2017-02-17 Thread Igor A. Ippolitov
I would suggest disabling swap at all. With 1.5Tb of RAM I doubt you need any. You can try finding out what is swapped by `smem` utility. May be you can live we those files swapped out of memory. Anyway, I doubt swappiness tuning will help you. Look through: https://www.kernel.org/doc/Documen