This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 28.000000000000004%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi
When signing into https://mail.domain.com/owa it returns:
:-(
Something went wrong
We can't get that information right now. Please try again later.
X-FEServer SERVERNAME
Date: DATE
When entering the incorrect auth details, OWA advises the wrong details were entered.
https://mail.domain.com/ecp works correctly.
We've tried:
Checked the certs are valid and bindings are correct
Deleted and recreated owa and ecp virtual directories
Recreated SharedWebConfig.config in ClientAccess and Frontend/httpproxy.
No owa errors in the event logs.
Doubt it's any of the above due to ECP working, suspect it's in the OWA redirect process.
All mailboxes are hosted in O365, OWA simply used to display a link to access the O356 mailbox.
The TargetOwaURL is correct in Get-OrganizationRelationship.
Same 'something went wrong' error when browsing owa in the Default Web Site in IIS to https://127.0.0.1:443 and https://localhost
When browsing owa in Exchange Back End on https://localhost:444 - "this page can't be displayed" https://localhost:444/owa/auth/errorFE.aspx?httpCode=404
This issue was noticed after the upgrade from CU21 to CU22 + the November SU, although it may have been an issue previously and not noticed.
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 92%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB3%3C/text%3E%3C/svg%3E)
We have the same issue with our Exchange 2016 although are still on CU21 and also noticed it after November SU. On-prem mailboxes work fine but mailboxes in O365 get the same error. So I agree with the suspicion of the OWA redirect process being impacted.
Looks like it's listed as a known issue on the Exchange blog which I didn't see first time
https://techcommunity.microsoft.com/t5/exchange-team-blog/released-november-2021-exchange-server-security-updates/ba-p/2933169/highlight/true/page/3"
"11/11: Added a known issue with OWA redirect for hybrid customers"
Didn't notice that either! Great stuff, thanks!
You can also tell user use the TargetOwaURL to login OWA directly: http://cloudowa.contoso.com/owa.
Due to there exist CNAME to point the "cloudowa.contoso.com" to "mail.office365.com". So, they could login with the link directly.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 98%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
This issue occurs if the Exchange Server Auth Certificate used for OAuth signing is missing from the Exchange Server. You can run the following command to check whether the certificate is missing:
Get-ExchangeCertificate (Get-AuthConfig).CurrentCertificateThumbprint
For Exchange Server 2016, install Cumulative Update 9 or a later cumulative update for Exchange Server 2016.
Also, you can check out How to Fix HTTP ERROR 500 in ECP/EAC after Login article for help.