Re: Issues building Nginx using boringssl

On Tue, Feb 20, 2024 at 12:23 AM 杨金泽 wrote: > > I encountered the following error when using boringssl to build Nginx: > checking for OpenSSL library ... not found > checking for OpenSSL library in /usr/local/ ... not found > checking for OpenSSL library in /usr/pkg/ ... not found > checking for O

Issues building Nginx using boringssl

Hello, I encountered the following error when using boringssl to build Nginx: checking for OpenSSL library ... not found checking for OpenSSL library in /usr/local/ ... not found checking for OpenSSL library in /usr/pkg/ ... not found checking for OpenSSL library in /opt/local/ ... not found ./auto

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Hi J Carter, Thank you for your reply. I am capturing the packet from firewall, and the filtering is as per below for the previously attached pcap. Source : client app -- Dest : nginx proxy , any port to any port Source : public server -- Dest : nginx proxy , any port to any port Source : nginx

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Hello, On Tue, 20 Feb 2024 09:40:13 +0800 Kin Seng wrote: > Hi J Carter, > > This is the only results from the whole 5 minutes session (intentionally > without any transaction to create inactivity). Is there any symptoms which > can prove that other parties are the one who Initiate the closing?

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Hi J Carter, This is the only results from the whole 5 minutes session (intentionally without any transaction to create inactivity). Is there any symptoms which can prove that other parties are the one who Initiate the closing? On Tue, Feb 20, 2024, 9:33 AM J Carter wrote: > Hello, > > On Mon,

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Hi Roman, Thanks for the suggestion. Let me get the debugging log up and retest again. On Tue, Feb 20, 2024, 1:02 AM Roman Arutyunyan wrote: > Hi, > > On Mon, Feb 19, 2024 at 04:24:04PM +0800, Kin Seng wrote: > > My current nginx setup always kill the TCP connection after 5 minutes of > > inacti

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Hello, On Mon, 19 Feb 2024 16:24:48 +0800 Kin Seng wrote: [...] > Please refer to the attachments for reference. > > On Mon, Feb 19, 2024 at 4:24 PM Kin Seng wrote: > > After capturing the tcp packet and check via wireshark, I found out that > > the nginx is sending out the RST to the public s

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Hi, On Mon, Feb 19, 2024 at 04:24:04PM +0800, Kin Seng wrote: > My current nginx setup always kill the TCP connection after 5 minutes of > inactivity, i.e no transaction. > [From wireshark, nginx send RST to upstream server and then send FIN,ACK to > downstream client] This could be the normal be

Re: NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

Please refer to the attachments for reference. On Mon, Feb 19, 2024 at 4:24 PM Kin Seng wrote: > My current nginx setup always kill the TCP connection after 5 minutes of > inactivity, i.e no transaction. > [From wireshark, nginx send RST to upstream server and then send FIN,ACK > to downstream c

NGINX Reverse Proxy terminate TCP connection after 5 minutes of inactivity

My current nginx setup always kill the TCP connection after 5 minutes of inactivity, i.e no transaction. [From wireshark, nginx send RST to upstream server and then send FIN,ACK to downstream client] I have this setup which requires TLS1.2 connection connecting from my internal network [client app