asked on

Exchange 2013 - ECP no longer available after Go Daddy SSL Certificate Replaced with new one. Mail flowing properly

Exchange 2013 Installed Go Daddy SSL Certifcate that was rekeyed after renewing. OWA and Email is working fine. Can no longer access ECP (internally from the server and externally - both worked properly before the new certificate was installed two days agao. In IIS Default Site has new Certificate listed under HTTPS correctly. Certificate names did not change. How to regain access?

J0rtIT

Yes. Go to iis. Default site. Backend. Binding and make sure is using the new cert on both sites backend and front-end. Reset iis and try again

Just like this:
https://messaging.faboit.com/2014/12/blank-screen-after-login-via-owa-in.html

timgreen7077

This same thing happened to me and I had to recreate the ECP virtual directory even though the names didn't change. Log onto the Exchange shell and run the following:

Remove the ECP Virtual Directory:
Remove-EcpVirtualDirectory -Identity "Server01\ecp (Default Web site)"

Recreate the ECP Virtual Directory:
New-EcpVirtualDirectory -Server SERVER01 -ExternalURL https://mail.contoso.com/ecp -InternalURL https://mail.contoso.com/ecp

Restart the IIS service:
iisreset /restart

Mahesh

How did you renewed certificate, through directly from GoDaddy?

OR

You have raised request from ECP?

I believe you have directly taken cert from GoDaddy, in that case what happened is quiet possible because I faced similar issue

in that case iis workaround would help, if that failed try ECP workaround

Deb Onderko

ASKER

Stopping and starting the MSExchangeECPAppPool did the trick and ECP is now available. Thanks for the helpful solutions!

This question needs an answer!

Become an EE member today

7 DAY FREE TRIAL

Members can start a 7-Day Free trial then enjoy unlimited access to the platform.

View membership options

Learn why we charge membership fees

We get it - no one likes a content blocker. Take one extra minute and find out why we block content.