Exchange Server mailbox database shows Content index state: NotApplicable. This only happens in Exchange Server…
Exchange OWA and ECP are showing that your connection is not secure. The administrators can’t sign in to ECP and users can’t sign in to OWA. It’s happening in all browsers. We tested it in Internet Explorer, Firefox and Google Chrome. We can confirm that it’s not working. How to fix Exchange 2016 OWA your connection is not secure?
Table of contents
What is happening?
The following message is showing in the browser Firefox. It will show a different error in other browsers.
In Google Chrome the message is showing:
Solution for Exchange 2016 OWA your connection is not secure
A message is showing that the best practices are set for the system. In our case, the Exchange Server 2016. Click OK.
Click Apply to save the changes.
Reboot is required for the settings to take effect. Click OK.
Restart the Exchange Server 2016.
Test Exchange 2016 OWA secure connection
After the restart of the system, start your favorite browser. Type the URL for OWA or ECP.
After entering the URL, we can see the screen that we are used to. Users can now sign in with their credentials. Exchange 2016 OWA your connection is not secure is fixed. It’s not only fixed for one browser but for all browsers. That’s great, did it work for you?
Articles that you may be interested in:
- Exchange namespace design and planning
- Configure Internal and External URL in Exchange
- Configure external DNS for Exchange
In this article, you learned why it’s showing Exchange 2016 OWA your connection is not secure. The solution to this problem is securing SSL and TLS on the Exchange Server. Download IIS Crypto and use the best practices option. Don’t forget to reboot after applying the settings! Did you enjoy this article? You may also like the article Configure internal DNS for Exchange. Don’t forget to follow us and share this article.