I've played with proxy timeout settings, no luck. And nothing was logged on
the backend-server.
Finally I've found something in the firewall log:
May 27 10:25:06 APZRP01 kernel: DROP: IN=APZRP01 OUT=
MAC=c4:34:6b:af:19:64:e8:65:49:28:08:77:08:00 SRC=10.59.55.245
DST=192.168.57.14 LEN=40 TOS=0x00
Check the logs of the apache server.
You might need to tweak the proxy_*_timeout settings in nginx , but
usually its the problem with the upstream server that is causing this.
try connecting to the upstream via http://domain:port directly and you
should face the error.
On Tue, Sep 13, 2016 at 3
I don't think there is an OS relation on the frontend, the same problem
occurs with an Centos Nginx as Reverse proxy in front of 3 Apache backends
on Centos - but it never occurs on windows based Apache backends...
But we´re on version 1.11.4.1 Lion (http://nginx-win.ecsds.eu)
Posted at Nginx For
hheiko Wrote:
---
> I've noticed the same problem between Nginx Proxy (Win) and CentOS
> based Apache 2.4 Backends. So I finally changed all backends to
> nginx+php-fpm...
What version of nginx are you running on Windows? (Asking because I am ju
I've noticed the same problem between Nginx Proxy (Win) and CentOS based
Apache 2.4 Backends. So I finally changed all backends to nginx+php-fpm...
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,268306,269500#msg-269500
___
nginx mailing lis
The problem still seems to persist. I am now trying to investigate this
myself. Any advise for debugging?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,268306,269498#msg-269498
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org
The error I am getting in the logs:
"upstream prematurely closed connection while reading response header from
upstream"
After the first request it works for 10-15 seconds without any problem.
According to tcpdump in the first request (the failing one) the upstream is
receiving one GET and nothi
