Forum Discussion
mark_fad
Jul 14, 2020Copper Contributor
Exchange Server 2013 on prem OWA blank screen after logging in
Hi,
I have an Exchange Server 2013 Standard running on prem and has been working great for a few years. Recently I updated the SSL certificate and everything seemed ok after the renewal. I only noticed when a user asked to login to their mailbox via the web client that OWA was not functioning. After entering the users credentials, the webpage turns white and nothing appears on the screen. I have tried the following:
1) Different web browsers. Tried Microsoft Edge and Google Chrome.
2) Different computers and accounts
3) Accessing from the LAN and from the WAN.
Same results from each test that there is a blank screen after logging in. I am able to log in successfully into ECP and can view the Exchange Admin Centre. I have tried researching the issue and there have been mentions that the SSL certificate is not installed correctly. I have revoked and renewed the certificate and still am getting the same result.
I would be grateful for any advice on what else to try and if anyone else has had a similar issue and has been able to resolve it.
Regards,
Mark
9 Replies
Sort By
- manuphilipCopper Contributor
Hello mark_fad ,
The issue you found is a common issue pops up after certificate renewal. The major root cause found was related to the certificate assignment to the exchange backend ssl bindings for port 443. So, check this at IIS console and make sure that certificate is not missing or assigned correctly. After the fix, just refresh owa and you should be fine there on
- mark_fadCopper Contributor
Hi manuphilip,
Thank you for your reply. I checked my certificates and they seem ok. I have attached some images of the Default Web Site bindings and the Exchange Back End bindings if you could please have a look to see if they are correct? The strange part is that ecp opens successfully but owa does not. This is what is confusing me.
Regards,
Mark
- manuphilipCopper Contributor
Hi mark_fad
Image Default_Site_Bindings.png shows a 443 binding for the local host also. Please check if certificate is assigned there too.