This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
Our 2013 Exchange server started an error recently, event 1003 MSExchange Front End HTTP Proxy, key certificate is not supported! As a result OWA and ECP are not working anymore.
I tried a different certificate, but the error remain. Which certificate is the error referring to? How to resolve?
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(281.6, 84%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
Hi @Dominic Russell ,
Welcome to our forum!
I tried a different certificate
What's the certificate that you have tried?
Event 1003 MSExchange Front End HTTP Proxy
This error may occur when your Exchange Server OAuth certificate is expired, if you haven't checked it, please first run the following command in EMS to check the status of your OAuth certificate, for more information, please refer to this document: Can't sign in to Outlook on the web or EAC if Exchange Server OAuth certificate is expired .
(Get-AuthConfig).CurrentCertificateThumbprint | Get-ExchangeCertificate | Format-List
If the command returns an error, or the certificate has expired, it's recommended to follow the document above to create and deploy a new OAuth certificate to the Exchange server.
If that's not your case or you still need further assistance, please feel free to post back.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sorry, I should have mentioned that I already tried that. There was an error on the first command, for which creating a new certificate fixed, but the 1003 event remained.
Hi @Dominic Russell ,
Thanks for your update and sorry for my misunderstandings.
In order to further confirm it, could you please provide us with more information and some relevant screenshots of your error(Notice: Please hide your personal information in the screenshot for security.)
Hi @Dominic Russell ,
Are you still researching for it? If you need further assistance, please feel free to post back.
Once logged in through OWA, here is what is shown :
:-(
Un problème est survenu
Désolé, nous n'avons actuellement pas accès à cette information. Réessayez ultérieurement. Si le problème persiste, contactez votre support technique.
X-ClientId: KVFT - KIEU - AFPT - VNTCGW
X-FEServer: XEN-SRV-2012-EX
Date: 2021-09-14 04:12:46
Moins de détails...
actualiser la page
Event 1003 shows this :
[Owa] An internal server error occurred. The unhandled exception was: System.NotSupportedException: L'algorithme de clé du certificat n'est pas pris en charge.
à System.Security.Cryptography.X509Certificates.PublicKey.get_Key()
à Microsoft.Exchange.HttpProxy.FbaModule.SetCadataCookies(HttpApplication httpApplication)
à Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.HandleFbaFormPost(BackEndServer backEndServer)
à Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.ShouldContinueProxy()
à Microsoft.Exchange.HttpProxy.ProxyRequestHandler.BeginProxyRequestOrRecalculate()
à Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)
à Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass3f.<OnCalculateTargetBackEndCompleted>b__3e()
à Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
Hi @Dominic Russell ,
Thanks for your update, due to the issue occurred only recently, have you performed any special operations on certificate or on your server before? And what's the version of your Exchange 2013?
I tried to understand your error by machine translation--System.NotSupportedException:The certificate key algorithm is not supported.
Based on my research, I found it may be related to the certificate that assign to IIS service, the issue may occur if you have assigned this service to a certificate that is not supported in Exchange, please kindly check it in your EAC(Server>certificate), if it's your case, please try to re-assign the IIS service to default certifiacte--"Microsoft Exchange" for testing.
If that's not your case, due to I found some similar threads that mentioned the error may be related to .NetFramework, please check your .Net Framwork version and ensure that the version of your framework is supported to your exchange. For more information, please refer to the Microsoft .NET Framework part of this document: Exchange Server supportability matrix.
If your issue has any update, please feel free to post back.
I tried .Net 4.8. I even tried removing last few updates that I installed in the last few months, the error remains. I tried many different certificates and different setup with IISCrypto, the behaviour does not change at all, after logging in, the algorithm is not supported error appears.