Welcome! Log In Create A New Profile

Advanced

10054: An existing connection was forcibly closed by the remote host

Posted by madvas 
8712#14268: *2060 WSARecv() failed (10054: An existing connection was
forcibly closed by the remote host) while reading response header from
upstream, client:0.xx.xx.0

Can any one help me on this please.
I have site A , site B.
Site B is front end with nginx...
I am getting this error 10/3 times of request.

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,267564,267564#msg-267564

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Tue, Jun 14, 2016 at 09:24:59AM -0400, madvas wrote:

Hi there,

> 8712#14268: *2060 WSARecv() failed (10054: An existing connection was
> forcibly closed by the remote host) while reading response header from
> upstream, client:0.xx.xx.0

If that error message is in nginx's error log, it suggests that nginx
thinks that something else closed the connection.

What is "upstream", in your case? Does it have any logs to indicate
a problem?

An old reply to the other thread you mailed this to indicated that it
may have been using a php server with not enough php children available.

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
apply these settings to the proxy:
keepalive_requests 500;
proxy_http_version 1.1;
context: http, server, location
Version 1.1 is recommended for use with keepalive connections

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,267564,280683#msg-280683

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Sorry, only registered users may post in this forum.

Click here to login