Bugzilla – Bug 26
Verify Zimbra's hostname and IP address during installation
Last modified: 2012-10-05 20:25:19 CEST
Installing ZeXtras zimlet on Zimbra server that is NOT binding to localhost fails with java network connection error.
Many users have customized their Zimbra to bind to a specific hostname/IP-address. This way we can use zimbra with apache side-by-side on the same port 80. This is only valid on the server with multiple IP addresses.
ZeXtras zimlet installation always assumes that the hostname is localhost. However in the above instance the zimbra server is running under different hostname/IP-address.
To replicate the problem and in this example I am using hostname.com as a zimbra's hostname:
1. Assign an available static IP address to the network interface (Debian 5):
iface eth0 inet static
up ip addr add 192.168.10.20/32 dev eth0
down ip addr del 192.168.10.20/32 dev eth0
2. Update DNS record for hostname.com:
@ A 192.168.10.20
mail A 192.168.10.20
3. Update hosts file
4. Restart network interface
zmprov ms hostname.com zimbraMailPort 80
zmprov ms hostname.com zimbraMailSSLPort 443
zmprov ms hostname.com zimbraMtaAuthHost hostname.com
Open jetty.xml.in located in /opt/zimbra/jetty*****/etc folder
add a line <Set name="host">22.214.171.124</Set> so it gets like this:
<!-- user services connector, no SSL -->
<!-- HTTPBEGIN -->
<New id="http" class="org.mortbay.jetty.nio.SelectChannelConnecto r">
<Set name="port"><SystemProperty name="jetty.port" default="%%zimbraMailPort%%"/></Set>
Now in the zimbra.web.xml.in and zimbraAdim.web.xml.in located in /opt/zimbra/jetty*****/etc folder UNCOMMENT anb make this change:
Try installing ZeXtras.
Error on ZeXtras zimlet install.
The temp fix:
Open hosts file and update it so that localhost points to above IP. Example:
Hopefully I have provided enough info to replicate the problem. I think this is an easy fix.
I'm checking this bug right now, I'll post additional informations as soon as they are available.
Have a nice day,
Update on this bug:
I checked the situation, and seems that your problem is caused by a Zimbra configuration issue. The ZeXtras Installer uses the standard 'zmzimletctl' command to deploy the ZeXtras Zimlet, so the request is managed directly by Zimbra.
Can you please try to manually install a different Zimlet on the server and give me the outcome of the operation?
Have a nice day,
Copyright © 2017 ZeXtras, All rights reserved.
Zimbra is a trademark of Zimbra Software, LLC.
ActiveSync is a registered Trademark of Microsoft Corporation