<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">>><span style="color: rgb(33, 33, 33); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif, serif, EmojiFont; font-size: 14.666666984558105px;">For details it's better to look into error.log.</span></p>
<br style="color: rgb(33, 33, 33); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif, serif, EmojiFont; font-size: 14.666666984558105px;">
<div>Error log says "Broker header [some garbage chars] while reading PROXY protocol, client: IPADDRESS, server:0.0.0.8443</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> nginx <nginx-bounces@nginx.org> on behalf of Roman Arutyunyan <arut@nginx.com><br>
<b>Sent:</b> Monday, May 7, 2018 3:55:59 PM<br>
<b>To:</b> nginx@nginx.org<br>
<b>Subject:</b> [EXT] Re: Connect to NGINX reverse proxy through proxy</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hello,<br>
<br>
On Mon, May 07, 2018 at 05:15:34AM +0000, Ajay Sonawane wrote:<br>
> I am using NGINX as a HTTPS reverse proxy and load balancer. My clients are able to connect to reverse proxy using SSL and reverse proxy is able to terminate SSL connection and establish a new connection with backend server, data exchange is also happening.<br>
> <br>
> <br>
> Now I am trying to setup a proxy between a client and NGINX. I am using SQUID proxy in between. I have enabled proxy protocol on nginx using<br>
> <br>
> <br>
> listen 443 ssl proxy_protocol;<br>
<br>
This line instructs nginx to expect PROXY protocol header from SQUID.<br>
Are you sure SQUID sends it? It looks like SQUID didn't support sending PROXY<br>
protocol header up until recently.<br>
<br>
> proxy_protocol on;<br>
> <br>
> <br>
> <br>
> <br>
> Still my client is not able to connect to NGINX through proxy. Is there anything else I need to do.<br>
<br>
For details it's better to look into error.log.<br>
<br>
-- <br>
Roman Arutyunyan<br>
_______________________________________________<br>
nginx mailing list<br>
nginx@nginx.org<br>
<a href="https://clicktime.symantec.com/a/1/-T9P8fTQru19QtJ92SY81cK1kgruSCyqw2a3i7ct9uA=?d=6I_E5mOuE_JiHm4QhzDePIEnOq_IvGHWcHWAQhy-J4UZqqAmz64BtlAUxaKeJ_QUeJlstY5j28Te7x5BUPJmBb7m6We9GzVL-5L0HAk8nw5PEVbXWoK8dlsjU1x4BITL4J3OeGFrdRvQR2wkGd5zLcFgsskyU4BCbuzKn8V5bKCmxB1DpG8cQVok5PkZ6Qg7YthetOt87ogtudPBDs_PJbaFVREIFlzqZKx96xuvYbT5uWM1w_ZYymY83doc7FsBvMyEFL2ozigFAfQT3usyvOndD3N6RIZxARXwdst7NOabaJMq1_Wofqujl-IAJ3M5MqakCUcNqdCC1EjAlA_YICSnnQ6daqQgPbBISB2mdbmdwAjRzNyu8eLvEue2CCe1_oSfgf7r3F4edwaTYA%3D%3D&u=http%3A%2F%2Fmailman.nginx.org%2Fmailman%2Flistinfo%2Fnginx">https://clicktime.symantec.com/a/1/-T9P8fTQru19QtJ92SY81cK1kgruSCyqw2a3i7ct9uA=?d=6I_E5mOuE_JiHm4QhzDePIEnOq_IvGHWcHWAQhy-J4UZqqAmz64BtlAUxaKeJ_QUeJlstY5j28Te7x5BUPJmBb7m6We9GzVL-5L0HAk8nw5PEVbXWoK8dlsjU1x4BITL4J3OeGFrdRvQR2wkGd5zLcFgsskyU4BCbuzKn8V5bKCmxB1DpG8cQVok5PkZ6Qg7YthetOt87ogtudPBDs_PJbaFVREIFlzqZKx96xuvYbT5uWM1w_ZYymY83doc7FsBvMyEFL2ozigFAfQT3usyvOndD3N6RIZxARXwdst7NOabaJMq1_Wofqujl-IAJ3M5MqakCUcNqdCC1EjAlA_YICSnnQ6daqQgPbBISB2mdbmdwAjRzNyu8eLvEue2CCe1_oSfgf7r3F4edwaTYA%3D%3D&u=http%3A%2F%2Fmailman.nginx.org%2Fmailman%2Flistinfo%2Fnginx</a><br>
</div>
</span></font></div>
</body>
</html>