http2 ciphers question on correct order /availability

2018-01-23 Thread Sophie Loewenthal
Hi, Did I add or remove the wrong ciphers for http2, and are they in the correct order? I found plenty of different documents on the Internet. Since mine is now broken, I should ask here :) Any ideas? Error message from Chrome: ERR_SSL_VERSION_OR_CIPHER_MISMATCH My nginx.conf has,

Re: http2 ciphers question on correct order /availability

2018-01-23 Thread A. Schulze
Sophie Loewenthal: ssl_ecdh_curvesecp521r1; I never used that curve, If there's no specific reason for secp521r1, try secp384r1 or leave it empty. ans see what whill happen. Andreas ___ nginx mailing list nginx@nginx.org http:/

Re: http2 ciphers question on correct order /availability

2018-01-23 Thread Sophie Loewenthal
That solved the problem. Thank-you Andreas. > On 23 Jan 2018, at 15:52, A. Schulze wrote: > > > Sophie Loewenthal: > > >> ssl_ecdh_curvesecp521r1; > > I never used that curve, If there's no specific reason for secp521r1, try > secp384r1 or leave it empty. > ans see what whill

Nginx - Only handles exactly 500 request per second - How to increase the limit?

2018-01-23 Thread agriz
worker_processes auto; pid /run/nginx.pid; worker_rlimit_nofile 10; error_log /var/log/nginx/error.log crit; events { worker_connections 4000; multi_accept on; use epoll; } http { include /etc/nginx/mime.types; sendfile on; tcp_nopush on; tcp_nodelay on; directio 4m; types_hash_

Debugging Safari 11 unable to connect over SSL to a http2 web server

2018-01-23 Thread Sophie Loewenthal
Hi, Chrome and Firefox can connect to my webserver over https running http2. Safari 11 cannot, and gave no error messages other than "cannot connect". There is a certificate name mismatch, but I thought Safari would still let me know why it did not connect. The SSL cert is otherwise valid. I

Re: Debugging Safari 11 unable to connect over SSL to a http2 web server

2018-01-23 Thread Sophie Loewenthal
Hi all, Problem found. This really was caused by an SSL cert name mismatch. > On 23 Jan 2018, at 20:27, Sophie Loewenthal wrote: > > Hi, > > Chrome and Firefox can connect to my webserver over https running http2. > Safari 11 cannot, and gave no error messages other than "cannot connect

Re: failed (13: Permission denied) while reading upstream on rename()

2018-01-23 Thread Francis Daly
On Sat, Jan 20, 2018 at 10:34:21PM +, Friscia, Michael wrote: Hi there, > In the error I see that the rename() failure was to change: > eedd07f7aef45a5ed22f748a31724947.002528 > to > eedd07f7aef45a5ed22f748a31724947 > > This seems to happen on some pages and then continues to happen if I

Re: failed (13: Permission denied) while reading upstream on rename()

2018-01-23 Thread 方坤
# setenforce 0 On Sun, Jan 21, 2018 at 6:34 AM, Friscia, Michael wrote: > Earlier today I solved a chmod() problem in the cache and now I’m faced > with this one which happens much less frequently. I don’t think permission > is the problem, I think it’s an Nginx configuration I failed to set > c

Quick successive reload makes "bind () xxxx failed, Address already in use" error

2018-01-23 Thread he.hailong5
Hi, I have a script runs two successive reloads, the first one is to remove a listen port from the stream block, and the second one is to add the same port back to the stream block. It is observed that most time the script would run into "bind() failed, Address already in use" error. Aft

Re: Quick successive reload makes "bind () xxxx failed, Address already in use" error

2018-01-23 Thread 方坤
Kill old processes first, then start new processes. On Wed, Jan 24, 2018 at 11:13 AM, wrote: > Hi, > > I have a script runs two successive reloads, the first one is to remove a > listen port from the stream block, and the second one is to add the same > port back to the stream block. It is obser

Re: Nginx - Only handles exactly 500 request per second - How to increase the limit?

2018-01-23 Thread Pratyush Kumar
What's the load during incident ?Are the request for static files or PHP ?On 23-Jan-2018 11:04 PM, agriz wrote:worker_processes auto; pid /run/nginx.pid; worker_rlimit_nofile 10; error_log /var/log/nginx/error.log crit; events { worker_connections 4000; multi_accept on; use epoll

Re: Nginx - Only handles exactly 500 request per second - How to increase the limit?

2018-01-23 Thread agriz
Sir, I can see any message there. Additionally, There are the sysctl.conf file i modified net.ipv6.conf.all.accept_ra=2 net.core.rmem_max = 16777216 net.core.rmem_default = 31457280 net.ipv4.tcp_rmem = 4096 87380 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_wmem = 4096 16384 16777216 net.ip

Re: Nginx - Only handles exactly 500 request per second - How to increase the limit?

2018-01-23 Thread Payam Chychi
On Tue, Jan 23, 2018 at 9:22 PM agriz wrote: > Sir, > > I can see any message there. > Additionally, There are the sysctl.conf file i modified > > net.ipv6.conf.all.accept_ra=2 > net.core.rmem_max = 16777216 > net.core.rmem_default = 31457280 > net.ipv4.tcp_rmem = 4096 87380 16777216 > net.core.w

Re: Quick successive reload makes "bind () xxxx failed,    Address already in use" error

2018-01-23 Thread he.hailong5
The downtime is critical, we cannot take "Kill and Start process"___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Quick successive reload makes "bind () xxxx failed, Address already in use" error

2018-01-23 Thread tokers
Hello! > I have a script runs two successive reloads, the first one is to remove a listen port from the stream block, and the second one is to add the same port back to the stream block. It is observed that > most time the script would run into "bind() failed, Address already in use" error. A

Re: Quick successive reload makes "bind () xxxx failed, Address already in use" error

2018-01-23 Thread oscaretu .
If you search in Google detect a IP port is in use in linux you can find several ways to detect in the port is in use, for Windows and Unix - https://www.cyberciti.biz/faq/unix-linux-check-if-port-is-in-use-command/ - https://askubuntu.com/questions/278448/how-to-know-what-prog

Re: Quick successive reload makes "bind () xxxx failed, Address already in use" error

2018-01-23 Thread he.hailong5
This is the forever loop that it it running in the script for { nginx -s reload //without the port nginx -s reload //with the port } I found there was a transient that both the master process and the newly forked worker were listening the same port, I am not sure if this mgih