Welcome! Log In Create A New Profile

Advanced

upstream prematurely closed connection

Posted by Thierry 
Thierry
upstream prematurely closed connection
January 06, 2017 04:30PM
Dear all,

The error message:
2017/01/05 18:28:49 [error] 32633#32633: *3 upstream prematurely closed connection while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: server_hostname.domain.ltd, request: "POST /SOGo/connect HTTP/2.0", upstream: "https://ip_server:port_number/SOGo/connect";, host: "server_hostname.domain.ltd:port_number", referrer: "https://server_hostname.domain.ltd:port_number/SOGo/";
2017/01/05 18:28:49 [error] 32633#32633: *3 upstream prematurely closed connection while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: server_hostname.domain.ltd, request: "GET /SOGo.woa/WebServerResources/busy.gif HTTP/2.0", upstream: "https://ip_server:port_number/SOGo.woa/WebServerResources/busy.gif";, host: "server_hostname.domain.ltd:port_number", referrer: "https://server_hostname.domain.ltd:port_number/SOGo/";

I have a front-end reverse proxy using Nginx for my web server and
for the web interface of my email server using Sogo.

From my firewall:
- If I NAT the "Sogo" port to my reverse-proxy I do
have these error and a 502 Bad Gateway message.
- If I bypass my reverse-proxy and NAT directly to my email server,
this is working.

On my reverse-proxy server, I am using Nginx version 1.9.10 (debian 8)
On my email server, I am using Nginx version 1.6.2 (debian 8)

If you need more information, please ask ... I do not understand
this error myself.

ps: it is the second time I am sending this email (?)


--
Cordialement,
Thierry e-mail : lenaigst@maelenn.org
PGP Key: 0xB7E3B9CD

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Thierry
Re: upstream prematurely closed connection
January 08, 2017 08:40AM
I have done some midification:

On my email server, I have upgrading my Nginx from 1.6 to 1.9.
I have add: http2

Both Nginx (email server and reverse proxy) have now the same Nginx
version.
But still have the same problem.

Thx for your support.

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

_______________________________________________
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