Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 945
  • Last Modified:

Exchange 2013 OWA

Hello,
Having a certificate issue with Exchange 2013 OWA

Time and date are correct on server
I get the following error:

Your connection is not private

Attackers might be trying to steal your information from mail.taeyangusa.com (for example, passwords, messages, or credit cards).

Back to safetyAdvanced
NET::ERR_CERT_AUTHORITY_INVALID

I have run the following commands in Exchange Power Shell
Any help is appreciated, Thanks !
$AutodiscoverHostName = "autodiscover.xxxxxx.com"

Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 15*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xml
0
jac1991
Asked:
jac1991
1 Solution
 
Muhammad MullaCommented:
1. Check from another client.
2. Check date and time on client.
3. Open Certificates plugin from mmc.exe for local computer on the client and check that it has the root certificate for the cert you are using.
0
 
Simon Butler (Sembee)ConsultantCommented:
Is this a trusted SSL certificate or are you still using the self signed one that Exchange generates?
If it is a trusted certificate, is it from a well known vendor?
If self signed, then you need to use a trusted certificate. The self signed certificate that Exchange creates is designed as a place holder only.

Simon.
0
 
BurundiLappCommented:
The certificate error: ERR_CERT_AUTHORITY_INVALID  suggest that the Certificate Authority that issued your Exchange certificate does not exist (i.e: it is a self signed certificate), was created by a Trusted Certificate Authority but you do not have that Certificate Authorities root certificate installed in your browser or in Windows if using IE, OR it is from a Certificate Authority that has had it's root certificates revoked or the root certificate has expired.

The most likely of these being it is a self signed certificate generated by Exchange itself.  If you intend to use OWA over the internet then you need to get a certificate from a trusted certificate authority such as Thawte, Verisign, Globalsign, etc..., ensure you get a certificate suitable for Exchange use, a certificate just for website would not be sufficient I think.

Also try this in different browsers.  Chrome is not giving somewhat misleading errors about certificates that signed using SHA1, another browser will not give the same error.

HTH
0
 
sly-kyorinCommented:
Or if you don't want to pay for one (which really you should) get a free certificate from somewhere like StartSSL, I've never had an issue using certs from them for SBS/Exchange.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now