jorgedlcruz wrote:scantec wrote:Not here. https is broken after upgrade on ubuntu 14.04 from a working 8.7.11, always getting "ERR_EMPTY_RESPONSE" on chrome i.e.
on logs: nginx.log: *26 client closed connection while waiting for request, client: x.x.x.x, server: 0.0.0.0:443
thedead106 wrote:Upgrade from 8.7 to 8.8 on Ubuntu smooth as silk. Good job guys. Now about my GAL issues.
Hello, starting ZCS 8.8 you will need to use a valid FQDN which your Zimbra server recognize, like if you have a Zimbra domain zimbra.io, you will be able to log in using mail.zimbra.io, etc, not by the IP.
If you want to use the IP just for a quick check please use the port
https://IP:8443, which is jetty, not proxy, that will allow logging in using only the IP.
Best regards
You can get around this restriction, but it's a bit of a process. Here's how we did it...
We wanted to build a new Zimbra multi-tenant hosting farm on the reliablenetworks.com domain, so customers could login via
https://proxy.reliablenetworks.com (not the real fqdn BTW...)
But, we didn't want to host email for the reliablenetworks.com domain on this hosting farm.
So what we did was build the new hosting farm's servers with reliablenetworks.com as the default domain, install our wildcard commercial SSL certificate and do much of the other initial deployment work.
Post install, what we did was as follows:
Code: Select all
zmprov rd reliablenetworks.com rnome.net
zmprov cd reliablenetworks.com
zmprov md reliablenetworks.com zimbraMailCatchAllAddress @reliablenetworks.com
zmprov md reliablenetworks.com zimbraMailCatchAllForwardingAddress @reliablenetworks.com
zmprov md reliablenetworks.com zimbraMailTransport smtp:cabernet.reliablenetworks.com
zmprov mcf zimbraVersionCheckNotificationEmailFrom zimbraadmin@rnome.net
zmprov mcf zimbraVersionCheckNotificationEmail zimbraadmin@rnome.net
zmprov mcf zimbraBackupReportEmailRecipients zimbraadmin@rnome.net
zmprov mcf zimbraBackupReportEmailSender zimbraadmin@rnome.net
*** On all servers we then ran: ***
zmlocalconfig -e av_notify_domain='rnome.net'
zmlocalconfig -e av_notify_user='zimbraadmin@rnome.net'
zmlocalconfig -e smtp_destination='zimbraadmin@rnome.net'
zmlocalconfig -e smtp_source='zimbraadmin@rnome.net'
zmprov ms `zmhostname` zimbraBackupReportEmailRecipients zimbraadmin@rnome.net
zmprov ms `zmhostname` zimbraBackupReportEmailSender zimbraadmin@rnome.net
*** And finally: ***
zmprov fc all
We noted that the Admin Console would not even load after we renamed the domain FWIW. We needed to create the reliablenetworks.com domain before things would work again.
*** UPDATE 1 *** I may have spoken too soon... The Admin Console works OK but not the regular web interface; still getting "client closed connection while waiting for request" errors. More work to do; will update this post when I have more info.
*** UPDATE 2 *** This looks promising:
https://bugzilla.zimbra.com/show_bug.cgi?id=108299#c7 Will try this tomorrow and update this post at that time.
*** UPDATE 3 :: ALL FIXED! *** Per Malte's suggestions in bugzilla 108299 (not in 8.8.5 BTW), we ran the following commands and then we were able to log in to both the end-user console and the Admin Console via the proxy, using an rnome.net account.
Code: Select all
zimbra@securemail:~$ zmprov md rnome.net zimbraVirtualHostname securemail.reliablenetworks.com
zimbra@securemail:~$ zmprov md rnome.net +zimbraVirtualHostname zmail.reliablenetworks.com
zimbra@securemail:~$ zmprov gd rnome.net | grep -i virtual
zimbraVirtualHostname: securemail.reliablenetworks.com
zimbraVirtualHostname: zmail.reliablenetworks.com
zimbra@securemail:~$ libexec/zmproxyconfgen
<snipped most output from zmproxyconfgen>
[] INFO: Proxy configuration files are generated successfully
zimbra@securemail:~$ zmproxyctl restart
Stopping proxy...done.
Starting proxy...done.
zimbra@securemail:~$
Hope that helps others,
Mark