Zimbra Installation – 502 Error due to Mailbox Server

Asked By 0 points N/A Posted on -

Hello everyone! My acquaintances and I have tried setting up Zimbra 5.0.9 through a multi server installation (2 x Proxy, 1 MTA In, 1 MTA Out, 2 x Mailbox and 1 master LDAP and 1 replica LDAP). While working on the installation, we found out that if we closed one mailbox server, we would receive a 502 Error when we try to open our page. We think that the probable cause of this error is the request that we received from nginx to close down the mailbox while we were trying to download Zimbra. To sort this error out, we need to get a way of getting the mailbox server out from the nginx configuration and allow the nginx server to send all requests to the running mailbox server. Although the solution seems to be too easy to say, executing it is our real problem. If anybody out here knows how to help us run our solution, kindly give us some tips. Thanks a lot, everyone!

Answered By 0 points N/A #99288

Zimbra Installation – 502 Error due to Mailbox Server



error 502 it's a bad gateway meaning that the status code/error indicates that the server was acting as a gateway or proxy and received an invalid response from the upstream server.  (typically , it is not supported on this particular server)

you have to re configure your /opt/zimbra/conf/nginx/template/nginx.conf.web.template the section upstream and {web.upstream.name}


index of /


# & {web.upstream.:servers}



and restart nginx before you stop mailbox server. you can do it in LDAP as well, but remember your mailboxes on the hashed out boxes will be gone.



Login/Register to Answer

Related Questions