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 correct network interface as per routing tables. In other words, NGINX is not aware if it is prby agforte - Nginx Mailing List - English
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 }, } and in doing so the private server was expecting to talk to the Proxy whicby agforte - Nginx Mailing List - English
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 the same destination, the public server, hardcoded in proxy_pass): stream {by agforte - Nginx Mailing List - English