Nginx didn't try the next available backend server

2019-04-09 Thread allenhe
Hi, My Nginx is configured with: proxy_next_upstream error timeout http_429 http_503; But I find it won't try the next available upstream server with the following error returned: 2019/04/05 20:11:41 [error] 85#85: *4903418 recv() failed (104: Connection reset by peer) while reading response hea

Worker other than the master is listening to the socket

2019-04-09 Thread allenhe
Hi, I understand it is the master process listen to the binding socket since that's what I see from the netstat output in most time: tcp0 0 0.0.0.0:28002 0.0.0.0:* LISTEN 12990/nginx: master while sometimes I found the worker process also doing the same t

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread George
yeah updated mercurial works https://forum.nginx.org/read.php?2,283686,283694#msg-283694 though centos 7 still will use non-SNI supported mercurial 2.6.2 so folks doing hg clone for njs repo will always have this issue. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,283686,283695#msg-2

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread George
okay part of the problem is centos 7 uses mercurial 2.6.2 and fix is to update to mercurial >2.7.9 for SNI support hg --version Mercurial Distributed SCM (version 2.6.2) (see http://mercurial.selenic.com for more information) Copyright (C) 2005-2012 Matt Mackall and others This is free software;

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread Maxim Dounin
Hello! On Tue, Apr 09, 2019 at 10:32:14AM -0400, George wrote: > for that i get > > echo -n | openssl s_client -connect hg.nginx.org:443 -servername > hg.nginx.org > CONNECTED(0003) > depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3 > verify return:1 > depth=1 C = US, O = Let's E

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread George
looks like hg clone is a non-SNI request so looked up pubserv.nginx.com's SSL cert *.nginx.com common name so maybe best to add *.nginx.org as well to pubserv.nginx.com server's SSL cert ? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,283686,283692#msg-283692

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread George
testssl 3.0rc4 output for testssl hg.nginx.org:443 Testing server defaults (Server Hello) TLS extensions (standard)"server name/#0" "renegotiation info/#65281" "EC point formats/#11" "session ticket/#35" "heartbeat/#15" "next protocol/#13172" "application layer protocol negotiation/#16"

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread George
for that i get echo -n | openssl s_client -connect hg.nginx.org:443 -servername hg.nginx.org CONNECTED(0003) depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 verify return:1 depth=0 CN = mailman.ngin

Re: https://hg.nginx.org certificate error ?

2019-04-09 Thread Maxim Dounin
Hello! On Tue, Apr 09, 2019 at 09:17:47AM -0400, George wrote: > Hi when I try to clone njs repo I am getting the error below > > hg clone https://hg.nginx.org/njs/ > abort: hg.nginx.org certificate error: certificate is for *.nginx.com, > nginx.com > (configure hostfingerprint > bd:90:5e:95:b4

https://hg.nginx.org certificate error ?

2019-04-09 Thread George
Hi when I try to clone njs repo I am getting the error below hg clone https://hg.nginx.org/njs/ abort: hg.nginx.org certificate error: certificate is for *.nginx.com, nginx.com (configure hostfingerprint bd:90:5e:95:b4:51:d8:0b:b0:36:41:6f:99:a7:80:01:4e:cf:ee:c2 or use --insecure to connect inse

nginx-1.15.11

2019-04-09 Thread Maxim Dounin
Changes with nginx 1.15.11 09 Apr 2019 *) Bugfix: in the "ssl_stapling_file" directive on Windows. -- Maxim Dounin http://nginx.org/ ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/list

nginx log : $upstream_response_time is larger than $request_time

2019-04-09 Thread mchtech
I use nginx(1.15.3) as a reverse-proxy, and encounter a problem that $upstream_response_time is larger than $request_time" in log files. According to nginx documentation, $upstream_response_time keeps time spent on receiving the response from the upstream server; the time is kept in seconds with