Hi Jore,

Thanks for taking time to look into this.

I am not able to understand what you mean.
If you are asking about, if ipv4/6 addresses of the machines changed
recently, then the answer is "no".

The servers are deployed on AWS and have an elastic IP address assigned to
them.

Another thing is, the issue disappeared for unknown reasons.
While troubleshooting the issue, I did many changes to the system to see if
it worked. Nothing had any effect.
I could observe the same issue after those changes.

I do not know what went wrong & what went right later.
I only know that I had to spend hours to attempt to solve the problem :-)
Anyway, thanks again!


On Sat, Jun 11, 2022 at 5:31 AM <nginx-request@nginx.org> wrote:

> Send nginx mailing list submissions to
> nginx@nginx.org
>
> To subscribe or unsubscribe via email, send a message with subject or
> body 'help' to
> nginx-request@nginx.org
>
> You can reach the person managing the list at
> nginx-owner@nginx.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of nginx digest..."Today's Topics:
>
> 1. Nginx response times got increased for unknown reasons
> (Tamil Vendhan Kanagarasu)
> 2. Re: Nginx response times got increased for unknown reasons (Jore)
>
>
>
> ---------- Forwarded message ----------
> From: Tamil Vendhan Kanagarasu <tamil@helptap.com>
> To: nginx@nginx.org
> Cc:
> Bcc:
> Date: Fri, 10 Jun 2022 22:09:42 +0530
> Subject: Nginx response times got increased for unknown reasons
> Hello everyone,
>
> We have been using Nginx for a few months now.
> It was great until this week. For unknown reasons, response times got
> higher.
> Like 2 minutes, 3 minutes higher from what was < 300ms before.
>
> No change on nginx configuration side.
> Mostly, I use the configuration unchanged from apt install.
> Only the following settings are added
>
> ```
>
> # Max size of request
> client_max_body_size 100M;
>
> # Max request headers size
> client_header_buffer_size 5120k;
>
> #
> large_client_header_buffers 16 5120k;
>
> # Server name size
> server_names_hash_bucket_size 128;
>
> server_tokens off; # removed pound sign
> more_set_headers 'Server: helptap.com';
> ```
>
> The setup is as follows:
> 1. Nginx is configured to deliver some static files.
> 2. Nginx is configured to work as reverse proxy. Upstream
> communications are done over websocket.
> 3. SSL is used for all communications. SSL is done using letsencrypt.
>
> I timed the upstream & able to confirm that they respond with in < 50ms in
> all the cases.
> In the browser, I receive them many seconds and in many cases minutes
> later.
> This issue is observed with both static file serving, http requests &
> websocket messages.
> So, I am sure that, it is not upstream issue, as static files also takes >
> 2 minutes to receive in one case.
>
> Any help to understand and resolve the problem would be greatly helpful to
> me.
>
> Good day!
>
> Best,
> Tamil Vendhan Kanagarasu
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Jore <community@thoughtmaybe.com>
> To: nginx@nginx.org
> Cc:
> Bcc:
> Date: Sat, 11 Jun 2022 08:04:11 +1000
> Subject: Re: Nginx response times got increased for unknown reasons
>
> Is an IPv4 or IPv6 change a factor?
>
>
> On 11/6/22 2:39 am, Tamil Vendhan Kanagarasu wrote:
>
> Hello everyone,
>
> We have been using Nginx for a few months now.
> It was great until this week. For unknown reasons, response times got
> higher.
> Like 2 minutes, 3 minutes higher from what was < 300ms before.
>
> No change on nginx configuration side.
> Mostly, I use the configuration unchanged from apt install.
> Only the following settings are added
>
> ```
>
> # Max size of request
> client_max_body_size 100M;
>
> # Max request headers size
> client_header_buffer_size 5120k;
>
> #
> large_client_header_buffers 16 5120k;
>
> # Server name size
> server_names_hash_bucket_size 128;
>
> server_tokens off; # removed pound sign
> more_set_headers 'Server: helptap.com';
> ```
>
> The setup is as follows:
> 1. Nginx is configured to deliver some static files.
> 2. Nginx is configured to work as reverse proxy. Upstream
> communications are done over websocket.
> 3. SSL is used for all communications. SSL is done using letsencrypt.
>
> I timed the upstream & able to confirm that they respond with in < 50ms in
> all the cases.
> In the browser, I receive them many seconds and in many cases minutes
> later.
> This issue is observed with both static file serving, http requests &
> websocket messages.
> So, I am sure that, it is not upstream issue, as static files also takes >
> 2 minutes to receive in one case.
>
> Any help to understand and resolve the problem would be greatly helpful to
> me.
>
> Good day!
>
> Best,
> Tamil Vendhan Kanagarasu
>
>
>
> _______________________________________________
> nginx mailing list -- nginx@nginx.org
> To unsubscribe send an email to nginx-leave@nginx.org
>
> _______________________________________________
> nginx mailing list -- nginx@nginx.org
> To unsubscribe send an email to nginx-leave@nginx.org
>
_______________________________________________
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-leave@nginx.org