Avatar of j_rameses
j_rameses
Flag for United States of America asked on

Exchange ECP log-in loops back to log-in after entering credentials.

Greetings.
I recently updated our SSl certificate on Exchange 2016.
Upon ding so, I lost connectivity to my ECP portal.
All I get when I login in is a reloop back to login again.
I have tried checking the certificate and settings but they look good as per my understanding.
I am not an Exchange Guru and this is the first time I encountered this issue.
I do need this resolved so I can add new users to our environment.
I could do it from our other Exchange Server in the DAg, but I do not want to go that route.
Reason being is that the issue will still be there: relooping after attempting to login.
I do can use OWA but not ECP.
I am running windows 2012 R2 as the OS for Exchange 2016.

I checked the settings in "default website" the bindings and they are correct pointing to the correct certificate.
I restarted the service on IIS in application pools called "MSExchangeECPAppPool", but to no avail.

Thank you for your attention.
ExchangeWindows Server 2012Golang

Avatar of undefined
Last Comment
Saif Shaikh

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Saif Shaikh

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
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.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
j_rameses

ASKER
Saif, thank you for your response.
So I should confirm that the settings from binding from my "exchange backend website" settings should match the "Default website"?
Saif Shaikh

yes even if you have a valid self-signed cert binded to exchange backend then its fine, but you can keep the same third party doesn't matter.
j_rameses

ASKER
Therefore both should match identically?
defaultwebsiteBindings1.JPG
ExchangeWebsiteBindings1.JPG
Your help has saved me hundreds of hours of internet surfing.
fblack61
Saif Shaikh

NONNONONO

Click on edit 443 on default website and you should see a view tab and there you will be able to see the cert.

Also click on edit 444 on backend website and you should see a view tab and there you will be able to see the cert.
j_rameses

ASKER
when I attempt to change the port from 444 to 443 on "https" on "exchange backend" I get the below error message.
error-message-uon-changing-port-numb.JPG
j_rameses

ASKER
I see the certificate since I changed it.
bindings-of-exchange-backend.JPG
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Saif Shaikh

Do not attempt to change any ports, just see if port 443 on default website and port 444 on exchange backend has the correct cert.
j_rameses

ASKER
Saif, thank you.
I added the correct cert on the ports for exchange backend server.
Afterwards I restarted the IIS services/server.
Once that completed, I know have access to my ecp.

I will have to put this in my notes for when I have to update the cert again in years time from now.

Thank you for your assistance.
Saif Shaikh

Good to see the issue is resolved. You are welcome.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23