Nginx fails to start

Revision as of 08:26, 27 May 2018 by Raunaq (talk | contribs) (Nginx fails to start)

Nginx fails to start


Nginx fails to start.

Running zmproxyctl start giving the following error :

"Starting nginx...failed.  /opt/zimbra/conf/nginx.conf is missing."

Configuring proxy by command -


prompting the following error :

Exception in thread "main" java.lang.NullPointerException
        at com.zimbra.cs.util.ProxyConfVar.isValidUpstream(
        at com.zimbra.cs.util.WebEwsSSLUpstreamServersVar.update(
        at com.zimbra.cs.util.ProxyConfGen.updateDefaultVars(
        at com.zimbra.cs.util.ProxyConfGen.createConf(
        at com.zimbra.cs.util.ProxyConfGen.main(


The error prompts when the proxy configuration has non-existing servers or non-mailbox servers listed with the following attributes -

Note: Please check the value of zimbraReverseProxyAvailableLookupTargets at the server level as well as global level configuration :

su - zimbra
zmprov -l gs `zmhostname` zimbraReverseProxyAvailableLookupTargets
zmprov -l gcf zimbraReverseProxyAvailableLookupTargets
zmprov -l gs `zmhostname` zimbraReverseProxyAvailableLookupTargets
zmprov -l gs `zmhostname` zimbraReverseProxyUpstreamEwsServers
zmprov -l gs `zmhostname` zimbraReverseProxyUpstreamLoginServers
zmprov -l gcf zimbraReverseProxyAvailableLookupTargets
zmprov -l gcf zimbraReverseProxyUpstreamEwsServers
zmprov -l gcf zimbraReverseProxyUpstreamLoginServers

Check the above attributes and put only valid mailbox server name in these attributes. If there are non-existing mailbox servers then we can change the attribute value by using below commands -

zmprov ms server_name zimbraReverseProxyUpstreamEwsServers <mailbox_server_name>
zmprov mcf zimbraReverseProxyUpstreamEwsServers <mailbox_server_name>

Then try again to configure zimbra-proxy

zmproxyconfgen -s `zmhostname` -w /tmp/
/opt/zimbra/libexec/zmproxyconfig -m -w -e -x redirect -H `zmhostname`

Submitted by: Sourabh Bhushan

Jump to: navigation, search