Re: a duplicate default server for 0.0.0.0:80 in /etc/nginx/nginx.conf:39

2020-11-25 Thread Kaushal Shriyan
On Tue, Nov 24, 2020 at 11:40 PM Kaushal Shriyan wrote: > Hi, > > I have two nginx.conf file /etc/nginx/conf.d/onetest.conf > and /etc/nginx/nginx.conf. Basically the first config file works without > any issue while redirecting from port 80 to 443. I want to enable the port > redirect from port

Re: client disconnects

2020-11-25 Thread Maxim Dounin
Hello! On Wed, Nov 25, 2020 at 11:43:59AM -0800, Frank Liu wrote: > Thanks for the clarification! > What would we see if the client disconnects in the middle of nginx sending > the response? Will there be a "while .." clause in the error log? Will the > http status code be reset to 499? As long

Re: client disconnects

2020-11-25 Thread Frank Liu
Hi, Thanks for the clarification! What would we see if the client disconnects in the middle of nginx sending the response? Will there be a "while .." clause in the error log? Will the http status code be reset to 499? Thanks! Frank On Wed, Nov 25, 2020 at 5:34 AM Maxim Dounin wrote: > Hello!

Re: one client "floods" nginx errorlog

2020-11-25 Thread Maxim Dounin
Hello! On Tue, Nov 24, 2020 at 05:46:43PM +0100, A. Schulze wrote: > I run a nginx instance handling only TLS1.2 and TLS1.3. > Now I noticed an remote client hammering (Ok, once per second) with an SSLv2 > connection an thus filling the log: > > 2020/11/24 17:37:08 [info] 383#0: *11 SSL_do_hand

Re: client disconnects

2020-11-25 Thread Maxim Dounin
Hello! On Tue, Nov 24, 2020 at 08:23:08PM -0800, Frank Liu wrote: > When a client disconnects (initiated tcp FIN), shouldn't we see 499 in > nginx logs? But sometimes I see 400, along with below in error log: > *2314539 client prematurely closed connection, client: x.x.x.x, > > Since I don't see

Problem while replacing a certificate by a new one, nains sees the old one.

2020-11-25 Thread Laurent Bois
Hi, I have a problem on a Windows 2012 server, with SSL certificate on nginx. We’ve replaced an old self signed certificate with a new one ready for production and we encounter a problem: even after restart, nains sees the old certificate. I think this problem is similar to renewing certificate