How do you access mail server from multi domain?

[yohoho]

Object:
1. mail.x.com (We follow Zimbra Installation guideline and use mail.x.com as the primary domain)
2. mail.y.com

Problem:
SSL-related, everytime we try to access mail.y.com

It always says

Your connection is not private
Attackers might be trying to steal your information from mail.y.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID

Help improve Safe Browsing by sending some system information and page content to Google. Privacy policy

Additional notes
We do still able to access the mail server from mail.y.com but it is a bit scary to see "Not secure" next to the domain.

[phoenix]

Object:
1. mail.x.com (We follow Zimbra Installation guideline and use mail.x.com as the primary domain)

That is not 'Zimbra guidelines' and that is the FQDN of your server and your primary domain would be "y.com", you need to fix your installation before going any further.

[yohoho]

Object:
1. mail.x.com (We follow Zimbra Installation guideline and use mail.x.com as the primary domain)

That is not 'Zimbra guidelines' and that is the FQDN of your server and your primary domain would be "y.com", you need to fix your installation before going any further.

I am sorry, what I mean is to access Zimbra you need to access https://mail.x.com/
and, if you wish to send a mail to, for example to Andre, the mail address would be andre@x.com

What I wish to do is to access Zimbra from https://mail.y.com and https://mail.x.com without SSL warning.
As of right now, anyone who try to access https://mail.y.com will receive a SSL warning because the SSL was supposed to be for mail.x.com

[JDunphy]

What I wish to do is to access Zimbra from https://mail.y.com and https://mail.x.com without SSL warning.
As of right now, anyone who try to access https://mail.y.com will receive a SSL warning because the SSL was supposed to be for mail.x.com

Add extra names to your certs as alternative names. The browser is complaining because it wants to connect with a TLS connection to your web server which is nginx (proxy) here. It is more like a web server for those web client connections is a simplified way to think of it.

Note: if this is letsencrypt... just use another -d to get that extra name on your cert. Here is how I do it with acme.sh bash script but they all pretty much work the same way. Google SAN - Certificate Subject Alternative Name.

Code: Select all

./acme.sh --issue --force --dns dns_cf -d  mail.x.com -d mail.y.com