SSL_write() failed (SSL:) (32: Broken pipe) while sending request to upstream

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Post Reply
vuducanha2
Posts: 8
Joined: Wed Nov 07, 2018 9:18 am

SSL_write() failed (SSL:) (32: Broken pipe) while sending request to upstream

Post by vuducanha2 »

Hi evevryone,

I had a multiserver zimbra 8.8.6 FOSS, recently I had this error when login : "SSL_write() failed (SSL:) (32: Broken pipe) while sending request to upstream" in log file /opt/zimbra/log/nginx.log on proxy server

Code: Select all

2021/05/06 09:25:03 [error] 12386#0: *1797 SSL_write() failed (SSL:) (32: Broken pipe) while sending request to upstream, client: 54.169.132.*, server: mail.domain, request: "POST //;jsessionid=1l2kptg3d0yu36oncd3zod5di HTTP/1.1", upstream: "https://ipmailbox:8443//;jsessionid=1l2kptg3d0yu36oncd3zod5di", host: "125.*.*.*"
I check proxy and mailbox status is all running, I can login from mailbox va https://mailbox_private_ip:8443 but when I login from proxy it show : HTTP ERROR 502 .

I tried restart proxy but it not helping

pls hepl me to fix this bug. thanks
eliast
Posts: 3
Joined: Sat May 15, 2021 8:37 pm

Re: SSL_write() failed (SSL:) (32: Broken pipe) while sending request to upstream

Post by eliast »

I have pretty much the same problem, but with 9.0.0P14. We are using TLS1.3 and since then we have this phenomenon. I tried official support but they were unable to respond for months, so my problem still exists.

If you have upgraded anything on your server, it might be possible that there are some library incompatibilities, and also the new browsers does not like to support TLS1.1, and similar... As well as new SSH and nginx has dropped old SSL and TLS support by default.

Also it worth a look of the cyphers being in use. I cannot give you commands to check sorry, I started - and finished - my life with Zimbra 9.0.
Post Reply