Link to home
Start Free TrialLog in
Avatar of Martijn Snel
Martijn SnelFlag for Netherlands

asked on

Exchange 2013 ECP SSL error

Hi all,

I've run into a bit of trouble with an Exchange 2013 installation. The server had issues with OWA which I thought where connected with certificates that might not be correctly configured. To fix this I used ECP to register a new, self-signed certificate from scratch. I somehow connected this to IIS (for ECP and OWA) and set it up to need SSL. Now I've run into the problem that whenever I try and open ECP I get an 403.4 error because the http-url forwards or is looking for the https version.

I didnt setup or install the environment so what I basically am looking for is a direction to reset certificates in Exchange back to defaults, so I can use ECP to try and fix everything again. Any suggestions are welcome :D.

Greetings
Martijn
Avatar of Todd Nelson
Todd Nelson
Flag of United States of America image

Do you get an error when you open EMS?  Is there a certificate bound to the Default Web Site in IIS?
Avatar of Martijn Snel

ASKER

Hi. Yes.. i get the same type of error (either its a 403.4 > when I go to ECP or a blanc page when I go to OWA or any other subpage). There is a binding in IIS to a certificate on the default website (Exchange Back End), I'm thinking that something went wrong (or I screwed up) and the wrong type of setting for SSL. I'm basically look for a way to bypass SSL / settings, or reset them completly so I can at least access ECP.
Use EMS and the command enable-exchangecertificate.
That will allow you to assign the correct certificate to the IIS role.

You can do everything through EMS, so lack of accept to ECP shouldn't be a problem to get the server fixed.
ASKER CERTIFIED SOLUTION
Avatar of Martijn Snel
Martijn Snel
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial