SOLVED Firewall ISSUE.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276607,276608#msg-276608
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello, I have nginx v 1.1.19 Im trying to configure one revese proxy with an
outside ip, I had many problems who its being registered in the log
showing:
connect() failed (110: Connection timed out) while connecting to upstream
and
SSL_do_handshake() failed (SSL: error:140770FC:SSL
routines:SSL23_
Hello!
On Wed, Sep 27, 2017 at 01:17:35PM -0700, Alder Netw wrote:
> We came across a case where kill -USR1 doesn't cause nginx reopen the
> access.log. And we need to run nginx with "daemon off" and "master-process
> off". Is that a known issue and is there any workaround?
Works fine here, just
Hello!
On Thu, Sep 28, 2017 at 04:54:41PM +0300, Maxim Dounin wrote:
> Hello!
>
> On Wed, Sep 27, 2017 at 10:38:45PM -0400, fengx wrote:
>
> > The config is rather simple as following. My test version is 1.7.2, a bit
> > old. I can't upgrade to the latest one in our production for now. Anyway I
Hello!
On Wed, Sep 27, 2017 at 10:38:45PM -0400, fengx wrote:
> The config is rather simple as following. My test version is 1.7.2, a bit
> old. I can't upgrade to the latest one in our production for now. Anyway I
> think it should work in 1.7.2 because the document says proxy_protocol was
> int
Thanks for the warning! I have to admit i was a little surprised to learn
that, arguably, the two major browsers don't implement 100-continue and have
no plan to do so. I know our scenario is far from typical but POST uploads
are surely widespread.
Thanks to all for your help on this, the support
