Exchange: An error occurred while using SSL configuration for endpoint 0.0.0.0:444

After changing the certificate on Exchange 2013+2016 (AND you have rebooted it – or it will happen eventually if you forget!), you may experience this when logging into ECP, you get the username and password prompt, you press login and – BAM:

You look in the event logs, and you see this:

EventID: 15021
An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data.

No need to be scared, this is not difficult to use, what happens is that the IIS websites are not having the new certificate set, and the certificate window under the binding in IIS is just empty:

Just click the dropdown menu, and select the correct certificate you have imported and run a IISRESET on the command prompt afterwards or even better reboot the server if possible.

This issue occurs if the SSL binding on 0.0.0.0:444 has one of more of the following issues:

The binding is installed incorrectly
The binding doesn’t have a certificate assigned.
The binding contains incorrect information.

For example, this issue occurs if the certificate hash of the binding is different from that of other bindings for application ID 4dc3e181-e14b-4a21-b022-59fc669b0914.

You can also fix via command prompt:

Type “netsh http show sslcert”:

Remove and replace the wrong certificate hash for 0.0.0.0:444 by running this:

“netsh http delete sslcert ipport=0.0.0.0:444”

“netsh http add sslcert ipport=0.0.0.0:444 certhash=a1d2a8d3275634xxxxxxxxxxxxxxxxx appid=”{4dc3e181-e14b-4a21-b022-59fc669b0914}”

Note: replace certhash with the full hash of your cert!

Reboot the server or do IISRESET command 🙂

Source:

You get a blank page after logging in EAC or OWA in Exchange 2013 or Exchange 2016 (microsoft.com)

Microsoft Exchange 2013 shows blank ECP & OWA after changes to SSL certificates | vcloudnine.de

53 Comments

Gal Cohen 18/06/2021 at 17:14

I found this article 5 minutes after figuring it out. Leaving a comment for others that might see this. Try it, it fixed my issue!

Reply ↓
1. Martin (Post author)29/06/2021 at 16:32
  
  Thnaks a lot 🙂
  
  best regards
  Martin
  
  Reply ↓
Dominic 28/06/2021 at 19:37

This worked great. I am an IT intern at a midsized medical production company in the states. Mail Exchange server went down when the Senior Sys Admin was out of town. Executives had Microsoft on the phone going down a rabbithole of troubleshooting database logs that had been delete. I saw the server pushing out SSL cert errors and then found a link to this page. Had it back up and running in about 10 minutes. Definitely got some brownie points from the team, so I thought I’d give you a thanks!

Have a good one and hello from Minnesota USA!

Reply ↓
1. Martin (Post author)29/06/2021 at 16:32
  
  Wow thanks a lot for the kind words!
  Glad it helped and good luck with the brownies 🙂
  
  Best regards
  Martin
  
  Reply ↓
Mortimer 03/07/2021 at 17:27

Thank you, thank you, THANK YOU!!
Had to reboot a server this holiday weekend to swap out a failed UPS and for a while I thought I was going to be spending the rest of the day trying to figure out why Outlook, OWA and even EAC would not work. Second Google result for the error and I found this page.

Reply ↓
1. Martin (Post author)07/07/2021 at 10:44
  
  Glad to hear! thanks 🙂
  
  Best regards
  Martin
  
  Reply ↓
Alistair Vernon 09/07/2021 at 11:56

Thank you, your are a life saver.

Reply ↓
1. Martin (Post author)14/07/2021 at 07:51
  
  Thanks 🙂 – Glad to hear 🙂
  
  Best regards
  Martin
  
  Reply ↓
Gela 24/09/2021 at 11:51

Thank you bro!

Reply ↓
1. Martin (Post author)02/10/2021 at 09:01
  
  You are welcome 🙂
  
  Reply ↓
Robert Barnes 22/10/2021 at 16:21

Any Idea what it could be limiting o365 to on-prem when the on-prem cert expired before i could replace?

I have imported a new rekeyed cert and all my info from the commands above match the new hash/thumbprint. Pulling my hair out on this!! 🙂

Reply ↓
1. Martin (Post author)27/10/2021 at 11:39
  
  Only mailflow / freebusy, but if all mailboxes are moved to the Cloud, you should not feel anything 🙂
  
  Reply ↓
Ali 25/10/2021 at 10:24

Saved my day..
Thank you very much Martin

Reply ↓
1. Martin (Post author)27/10/2021 at 11:38
  
  Thanks Ali 🙂
  
  Regards Martin
  
  Reply ↓
Evghenii 12/11/2021 at 03:13

worked for me, thanks!

Reply ↓
1. Martin (Post author)29/11/2021 at 11:16
  
  Glad to hear 🙂
  
  Reply ↓
Josh 18/01/2022 at 17:56

This is interesting. I use Let’s Encrypt certificates on my Exchange servers, bound to :443 for OWA etc. Those certs renew every three months, so I have automation in place to reassign Exchange services to the new certificate at renewal. I’ve (so far) gotten away with :444 bound to a self-signed internal cert that only renews every five or ten years.

Any idea why my experience differs?

Reply ↓
1. Martin (Post author)27/01/2022 at 09:26
  
  I think it’s because when you change the cert normally on Exchange, both 443 and 444 are replaced, and the way you do it, only replaces 443 🙂
  
  Reply ↓
Obama 01/02/2022 at 21:04

Very useful tip. Thanks a lot.

Reply ↓
1. Martin (Post author)02/02/2022 at 08:55
  
  Thanks 🙂
  
  Reply ↓
DMann 10/02/2022 at 15:57

Saved me Brother! Thank you!

Reply ↓
David 13/02/2022 at 20:53

Thank so much for sharing this. Every time something breaks with Exchange I am filled with dread about how long it will take to fix it – fortunately your blog was the first hit on Google for me and you resolved the issue immediately!

Reply ↓
Mike 27/02/2022 at 18:27

Thank you so much, had this issue with Exchange 2013 this morning and quickly resolved it using your article!

Reply ↓
Hans 05/05/2022 at 10:34

Awesome, thank you for sharing, works

Reply ↓
Evan 11/06/2022 at 07:51

1am patching Exchange 2016, this just saved my bacon. Thank you!!

Reply ↓
Emmet 28/06/2022 at 11:08

Legend. Fixed my Ex2019 servers, post security update I had the same error. Would have taken me a while to find that 👍

Reply ↓
McCurtis Ashley Grayson 13/08/2022 at 17:10

Holy Cow!!!! You are a life saver!!!! Definitely worked for me!!!!! You just saved me a lot of stress this weekend!

Reply ↓
1. Martin (Post author)16/08/2022 at 08:27
  
  Thanks 🙂
  Br. Martin
  
  Reply ↓
José Martins 02/10/2022 at 15:18

Thanks, Martin, You save my day!!!

Reply ↓
David 24/10/2022 at 18:55

Just came across this exact issue and your blog was the first search result hit.
Problem solved.
Thanks Martin!

Reply ↓
1. Martin (Post author)26/10/2022 at 09:12
  
  Thanks 🙂
  
  Br. Martin
  
  Reply ↓
Sean 19/01/2023 at 07:27

Yes worked for me thanks a heap 🙂 My issue was created by deleting an old cert in the certlm.msc

Reply ↓
1. Martin (Post author)23/01/2023 at 14:05
  
  Thanks 🙂
  
  Best regards
  Martin
  
  Reply ↓
Leon 23/01/2023 at 11:05

thnx mate! this was so helpful!!! great article!! thnx again!

Reply ↓
1. Martin (Post author)23/01/2023 at 14:05
  
  Thanks 🙂
  
  Best regards
  Martin
  
  Reply ↓
Ray 26/01/2023 at 18:49

This was helpful. thanks. the real question is for our setup, the cert was no longer selected, just had to use the drop down and select it again. but what would cause it just out of the blue to become un-selected?

Reply ↓
1. Martin (Post author)16/02/2023 at 08:04
  
  Did you ever do a IISRESET or server restart?
  Have seen this before, when customer did not do any of the above, and then the problem happened, out of the blue 🙂
  
  Reply ↓
Amjad Ali 07/03/2023 at 23:54

Thanks Bro.. you save my night.. Love u 🙂

Reply ↓
Neo 27/03/2023 at 21:28

Thank you very much! Save me tons of time to troubleshooting.

Reply ↓
Robert Salasidis 03/05/2023 at 06:13

Fixed it for me – Thanks

Reply ↓
Luis L 18/07/2023 at 09:38

Still saving lives!!! Thank you!!!

Reply ↓
1. Martin (Post author)06/08/2023 at 09:00
  
  THANKS 😀
  
  Reply ↓
mark 17/08/2023 at 21:43

Looked everywhere for a solution and then found your post, fixed it in minutes. Thank You Martin!

Reply ↓
1. Martin (Post author)28/08/2023 at 15:14
  
  Thanks 🙂
  
  Reply ↓
Andy N 07/09/2023 at 10:45

Saved my bacon, Kudos to you in spades Martin.

Reply ↓
1. Martin (Post author)26/09/2023 at 08:23
  
  Thanks 🙂
  
  Br. Martin
  
  Reply ↓
Stefano 09/10/2023 at 09:08

Hey Martin got this error today and found your post. Worked perfectly. Thanks for sharing.

Reply ↓
1. Martin (Post author)28/10/2023 at 08:10
  
  Glad to hear 🙂
  
  Best regards
  Martin
  
  Reply ↓
Charlie 12/10/2023 at 05:15

Happened to me today. Exchange 2019 servers humming along nicely for about 3 months, then cannot access ECP or Exchange PowerShell.

Followed this guide and fixed.

Thank you.

Reply ↓
1. Martin (Post author)28/10/2023 at 08:10
  
  Glad to hear 🙂
  
  Best regards
  Martin
  
  Reply ↓
Jon 12/11/2023 at 06:43

Martin,

Happened to me in the middle of a migration to 365 pulling an all weekender. Came upon your page and wanted to send a virtual hug and or a coffee! 🙂

Thank you!

Reply ↓
1. Martin (Post author)20/11/2023 at 12:27
  
  Glad to hear 🙂
  
  Best regards
  Martin
  
  Reply ↓
Mihaly 31/01/2024 at 20:08

Thank you very much the solution.
If you go to Hungary, i pay a beer for you

Reply ↓

Exchange: An error occurred while using SSL configuration for endpoint 0.0.0.0:444

Related Posts

53 Comments

Leave a Reply to Neo Cancel reply