Hi J Carter,
Thank you so much for your suggestions, I did tcpdump concurrently on both
nginx and client app host as well and able to find out that F5 device in
between is sending out RST to both side. Now i am able to exclude Nginx's
configuration as part of the investigation.
On Thu, Feb 22,
Hello,
On Tue, 20 Feb 2024 11:57:27 +0800
Kin Seng wrote:
> 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.
I see, I assumed you had run tcpdump on the nginx
host. I'd reccomend doing
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 :
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
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,
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
> >
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
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
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
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
10 matches
Mail list logo
