Page 1 of 1

Issue with Meeting unique links [BUG]

Posted: Wed Nov 11, 2020 12:30 am
by edavrio
We are running some tests with Zimbra 9 and we believe there is a bug related to Connect Meeting links.
Currently our setup is running behind a proxy and we are running HTTPS.
For some reason the Video meeting links generated have 8443 port something like

Code: Select all

https://domain.com:8443/zx/team/instant-meeting/GIZDGMBWHFSDKLJRMFSTELJUHA3GCLLBGU3GMLJWGBTGKNBVG42DQMTEMNAGS2DPON2C43LE


It works both with and without port 8443 but there is no way to change that, so basically you need to keep the port open in Firewall.
There is nothing covered in Wiki about this or in Documentation.
Could somebody make some light in this question?

The output for zmprov gs

Code: Select all

zimbraAdminPort: 7071
zimbraAdminProxyPort: 9071
zimbraImapBindPort: 7143
zimbraImapCleartextLoginEnabled: TRUE
zimbraImapProxyBindPort: 143
zimbraImapSSLBindPort: 7993
zimbraImapSSLProxyBindPort: 993
zimbraMailMode: https
zimbraMailPort: 8080
zimbraMailProxyPort: 80
zimbraMailReferMode: reverse-proxied
zimbraMailSSLPort: 8443
zimbraMailSSLProxyPort: 443
zimbraPop3BindPort: 7110
zimbraPop3CleartextLoginEnabled: TRUE
zimbraPop3ProxyBindPort: 110
zimbraPop3SSLBindPort: 7995
zimbraPop3SSLProxyBindPort: 995
zimbraReverseProxyAdminEnabled: FALSE
zimbraReverseProxyHttpEnabled: TRUE
zimbraReverseProxyLookupTarget: TRUE
zimbraReverseProxyMailEnabled: TRUE
zimbraReverseProxyMailMode: redirect
zimbraReverseProxySSLToUpstreamEnabled: TRUE

Re: Issue with Meeting unique links [BUG]

Posted: Wed Nov 11, 2020 2:13 pm
by L. Mark Stone
Welcome to the Forums!

This is not a bug.

You'll just need to set the PublicService* variables on the domain, so that Zimbra's proxy rewrites the URLs to reference the Zimbra or end-user-facing proxy and not use the actual URL the mailbox server (or service, if you have a single unified server) uses.

For example:

Code: Select all

zimbra@mailbox8:~$ zmprov gd missioncriticalemail.com | grep -i publicservice
zimbraPublicServiceHostname: mail.missioncriticalemail.com
zimbraPublicServicePort: 443
zimbraPublicServiceProtocol: https
zimbra@mailbox8:~$


In the above case, I host on AWS and mail.missioncriticalemail.com is an AWS Layer 4 Network Load Balancer.

For background, 443 is the public-facing port the Zimbra proxy uses. 8443 is the port the proxy service uses to communicate with the mailbox service. If you don't set the PublicService* variables, Zimbra uses the actual URL to talk to the mailbox service directly. This is a vestige from the days when it was prohibited to install Zimbra Proxy on a single Zimbra server. In a multi-server environment, the mailbox servers are typically not reachable from the public Internet directly.

Hope that helps,
Mark

Re: Issue with Meeting unique links [BUG]

Posted: Tue Nov 17, 2020 12:54 am
by edavrio
Yep. That solved the issue.
Strange this is not covered in the documentation.
Thank you for clarification.