Hi All,
I am getting below error can anyone let me know how to resolve it
2017/09/02 23:26:05 [crit] 28974#0: *2333672 SSL_do_handshake() failed (SSL:
error:1408A0D7:SSL routines:SSL3_GET_CLIENT_HELLO:required cipher missing)
while SSL handshaking, client: 10.210.128.122, server: 0.0.0.0:443
2
Wonder any has experimented with expanding an existing process by spawning
a thread running a thin layer of nginx
code so the process can process http and support rest interface? Thanks,
- Alder
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx
Dear Folks,
On 19/09/17 10:46 +1000, Nick Urbanik wrote:
We have this message repeatedly, despite increasing keys_zone size by
a factor of three to:
proxy_cache_path/srv/mycache levels=1:2 keys_zone=myzone:150m
inactive=15d;
This caused the errors to stop for three or four hours a
Dear Folks,
We have this message repeatedly, despite increasing keys_zone size by
a factor of three to:
proxy_cache_path/srv/mycache levels=1:2 keys_zone=myzone:150m
inactive=15d;
This caused the errors to stop for three or four hours and then back
again.
The cache itself is quite
On Mon, Sep 18, 2017 at 11:26:37PM +0200, Ph. Gras wrote:
Hi there,
> :/etc/nginx/sites-available# curl -I
> http://poste.enpret.com/pipermail/rs-idf-discuter/index.html
> HTTP/1.1 403 Forbidden
> location /pipermail {
> alias /var/lib/mailman/archives/public;
What do eac
Hello there,
unfortunately I'm not able to access to archives (pipermail) of my mailman
lists.
I'm using Nginx with a fcgiwrap gateway interface :
:/etc/nginx/sites-available# curl -I
http://poste.enpret.com/pipermail/rs-idf-discuter/index.html
HTTP/1.1 403 Forbidden
Server: nginx
Date: Sun, 17
On Mon, Sep 18, 2017 at 02:43:37AM -0400, sandyman wrote:
Hi there,
> I am trying to deploy my project to a production environment
It looks like you have been trying lots of different things, and changing
some things each time.
It will probably be simpler for you if you find one tutorial on ho
Hi PetrHolik,
Did you find a solution to forcibly releasing memory after Ngin reload?
We are now experiencing the same problem. After Nginx reload, the memory
consumption of Nginx processes grows to 10Gb
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,248163,276430#msg-276430
___