netstat
> command,
> > it shows CLOSE_WAIT for the terminated session, it seems like close_wait
> is
> > the symbol that the closing is from external ( in this case client app is
> > connect to nginx proxy), is this right?
>
> close_wait on client would indicate th
connect to nginx proxy), is this right?
close_wait on client would indicate that the other party initated
connection close (sent the first FIN) - again, firewall makes me more
skeptical, as it can have it's own timers for closing tcp connection /
it's own logic.
___
ut
> > > that
> > > > > the nginx is sending out the RST to the public server and then
> send
> > > FIN/ACK
> > > > > (refer attached pcap picture) to client application.
> > > > >
> > > > > I have tried to enable kee
c server and then send
> > FIN/ACK
> > > > (refer attached pcap picture) to client application.
> > > >
> > > > I have tried to enable keepalive related parameters as per the nginx
> > > > config above and also check on the
ck on the OS's TCP tunable and i could not
> find
> > > any related settings which make NGINX to kill the TCP connection.
> > >
> > > Anyone encountering the same issues?
> > >
>
> The screenshot shows only 1 segment with FIN flag set too which is
>
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 aft
the RST to the public server and then send FIN/ACK
> > (refer attached pcap picture) to client application.
> >
> > I have tried to enable keepalive related parameters as per the nginx
> > config above and also check on the OS's TCP tunable and i could not find
> &g
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 b
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
> t
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
ooking for when a client establishes a TCP connection to an IP and
port, that NGINX is listening on, that NGINX, without waiting on data being
transmitted from the client to NGINX, would establish a TCP connection to
the upstream.
What happened when you tried it?
A quick test here of "nc
On Fri, Mar 20, 2020 at 09:57:40AM -0400, Phillip Odam wrote:
Hi there,
> I'm looking for when a client establishes a TCP connection to an IP and
> port, that NGINX is listening on, that NGINX, without waiting on data being
> transmitted from the client to NGINX, would establish a
Hi
I'm looking for when a client establishes a TCP connection to an IP and
port, that NGINX is listening on, that NGINX, without waiting on data
being transmitted from the client to NGINX, would establish a TCP
connection to the upstream.
If such a capability were to exist I'd ha
server {
listen 8080 http2 reuseport;
server_name dev-status-service-svc-protocol-50051;
access_log off;
http2_max_requests 1000;
http2_max_concurrent_streams 512;
grpc_socket_keepalive on;
location / {
Thanks for your quick response.
Is there a way to delay the execution of limit_conn. Please suggest if there's
a way forward on this.
thanks,
raj
-Original Message-
From: nginx On Behalf Of Roman Arutyunyan
Sent: Tuesday, March 26, 2019 4:59 PM
To: nginx@nginx.org
Subject: Re
Hi,
On Tue, Mar 26, 2019 at 09:13:44AM +, R, Rajkumar (Raj) wrote:
> Hi,
>
> Using nginx in TCP/Stream mode and would like to limit the number of active
> connection to my backend server whereas the backend is resolved dynamically
> based on the SNI header ($ssl_preread_server_name). But t
Hi,
Using nginx in TCP/Stream mode and would like to limit the number of active
connection to my backend server whereas the backend is resolved dynamically
based on the SNI header ($ssl_preread_server_name). But this does not allow
any connections to the backend with below config. I see examp
Thanks! Indeed, `http2_max_requests` does close the tcp connection;
BTW, I've confirmed that it is a bug of grpc-go. Thanks again!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,283297,283304#msg-283304
___
nginx mailing list
after 1000 requests been processed,
> nginx will close the tcp connection, because I can find `TIME_WAIT` on the
> nginx side.
> - then gRPC client will report tens of thousands of `TransientFailure` at
> same time
>
See http://ng
ith gRPC client, after 1000 requests been processed,
nginx will close the tcp connection, because I can find `TIME_WAIT` on the
nginx side.
- then gRPC client will report tens of thousands of `TransientFailure` at
same time
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,283297,28
Hello!
On Wed, Sep 19, 2018 at 02:19:53AM -0400, winger7 wrote:
> I've been trying to identify the last HTTP request from a buffer of 10
> requests sent on a TCP connection in nginx. I've tried to use the header_in
> field in the ngx_http_request_t by checking if th
I've been trying to identify the last HTTP request from a buffer of 10
requests sent on a TCP connection in nginx. I've tried to use the header_in
field in the ngx_http_request_t by checking if the pos field for the
header_in is equal to the last field. This condition holds true twice, o
Hello!
On Thu, Mar 30, 2017 at 08:27:15AM +, Kilian Ries wrote:
> Hi,
>
> i configured my nginx with proxy_protocol, ssl and http2:
>
> server {
> listen 443 ssl http2 proxy_protocol;
>
> …
> }
>
> Now nginx is accepting proxy_protocol connections but not normal
> TCP connections
Hi,
i configured my nginx with proxy_protocol, ssl and http2:
server {
listen 443 ssl http2 proxy_protocol;
…
}
Now nginx is accepting proxy_protocol connections but not normal TCP
connections. Is there any change to let nginx accept both connection types? I
have a situation where are
Giulio,
On 3/5/16 1:25 AM, Giulio Loffreda wrote:
> Here is my nginx.conf and site config. After calling tcp
> connection and getting http 400, no log is generated.
>
> I’m following
>
Let me re-phrase: this is not your _full_ nginx config. There are
probably other files i
On Friday 04 March 2016 23:25:27 Giulio Loffreda wrote:
> Here is my nginx.conf and site config.
> After calling tcp connection and getting http 400, no log is generated.
>
> I’m following
>
> Thanks
>
> server {
> listen 80;
>
Here is my nginx.conf and site config.
After calling tcp connection and getting http 400, no log is generated.
I’m following
Thanks
server {
listen 80;
server_name apidvc.sparkgo.cc;
access_log /var/log/nginx/myhost.com.access.log combined;
root /home/spark
On Friday 04 March 2016 19:12:56 Giulio Loffreda wrote:
> Still having no luck.
> No log is generated.
>
> TCP connection has any relation to web socket support configuration ?
>
> this is my site config.
>
> server {
> listen 80;
> server_name my
does /var/log/nginx exist, and it is writeable by the web server user?
On 03/05/2016 07:12 AM, Giulio Loffreda wrote:
Still having no luck.
No log is generated.
TCP connection has any relation to web socket support configuration ?
this is my site config.
server {
listen 80
You have been told to use the info error_log level, which is not set
(defaults to error).
Make sure no other error_log directive might overwrite this one.
---
*B. R.*
On Fri, Mar 4, 2016 at 7:12 PM, Giulio Loffreda
wrote:
> Still having no luck.
> No log is generated.
>
> TCP co
Still having no luck.
No log is generated.
TCP connection has any relation to web socket support configuration ?
this is my site config.
server {
listen 80;
server_name myhost.com;
access_log /var/log/nginx/myhost.com.log combined;
error_log /var/log/nginx
On Friday 04 March 2016 17:41:42 Giulio Loffreda wrote:
> Thank you for your answer.
>
> Here is my log after the request, my request, my response and my nginx.conf
>
> root@vps190138:~# cat /var/log/nginx-error.log
> 2016/03/04 15:49:02 [notice] 8990#0: using the "epoll" event method
> 2016/03/0
Thank you for your answer.
Here is my log after the request, my request, my response and my nginx.conf
root@vps190138:~# cat /var/log/nginx-error.log
2016/03/04 15:49:02 [notice] 8990#0: using the "epoll" event method
2016/03/04 15:49:02 [notice] 8990#0: nginx/1.8.1
2016/03/04 15:49:02 [notice] 8
On Friday 04 March 2016 17:20:18 Giulio Loffreda wrote:
> Hi All,
>
> If I’m sending this email to wrong list, apologies and give me the good one.
>
> I have one embedded application which needs to connect via TCP and send an
> HTTP request.
> We run Nginx on Ubuntu 14.04.
>
> I can connect and
Hi All,
If I’m sending this email to wrong list, apologies and give me the good one.
I have one embedded application which needs to connect via TCP and send an HTTP
request.
We run Nginx on Ubuntu 14.04.
I can connect and persist, but once the packet is sent, I get HTTP 400 without
any log and
Anyone knows about this? I feel it is very important to know the network
delay between LB and the US servers
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,258958,259412#msg-259412
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.o
I am using the Nginx as a reverse proxy and I want to find out the TCP
connection information on both east and west bound connections.
With the following params on the access log, I am able to get the info about
the client TCP connection. Now, I want to find the RTT between Nginx and the
backend
37 matches
Mail list logo
