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.
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.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.
Was this mentioned in the Release Notes?jorgedlcruz wrote: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.
jorgedlcruz wrote: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.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.
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
Hello Duddy,DuddiZetor wrote:Upgrade from 8.7.5 on ubuntu 16 went smoothly
However, I now get the following error when logging into the web client: ???account.INVALID_ATTR_NAME???
Any ideas?
You can get around this restriction, but it's a bit of a process. Here's how we did it...jorgedlcruz wrote: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.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.
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
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
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:~$
Umm... wasn't this supposed to be fixed in 8.8 and the "security feature" only enabled on request? I mean we saw the fallout of this change in September (I think it was one of the most discussed beta issues) and the change was merged last month or so and it still wasn't included in the GA? Seriously?jorgedlcruz wrote: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.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.
Uhm guys i know it soudns stupid and maybe it doesnt mean anything but i though its wierd that all files (at least in the ubuntu package) have the date of oct 26msquadrat wrote:Umm... wasn't this supposed to be fixed in 8.8 and the "security feature" only enabled on request? I mean we saw the fallout of this change in September (I think it was one of the most discussed beta issues) and the change was merged last month or so and it still wasn't included in the GA? Seriously?jorgedlcruz wrote: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.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
You're right, I didn't look at the build date before but this release was obviously built in October: zcs-NETWORK-8.8.5_GA_1894.UBUNTU16_64.20171026035615. I'm sure this must have been a mistake.10424bofh wrote:Uhm guys i know it soudns stupid and maybe it doesnt mean anything but i though its wierd that all files (at least in the ubuntu package) have the date of oct 26msquadrat wrote:Umm... wasn't this supposed to be fixed in 8.8 and the "security feature" only enabled on request? I mean we saw the fallout of this change in September (I think it was one of the most discussed beta issues) and the change was merged last month or so and it still wasn't included in the GA? Seriously?jorgedlcruz wrote:
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.
i wonder why this is and if maybe, jsut maybe we have here an older build as an release