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(6.4, 84%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH3%3C/text%3E%3C/svg%3E)
The Windows Server Essentials Setup Wizard fails when setting up a new Anywhere Domain name, displaying a message to retry later. This issue has persisted for over a week.
The Console.log file indicates an error related to an invalid remote certificate.
Is there a way to resolve this error? Below is the relevant error detail from the Console.log:
RetrievedWholeOfferingList:True
[14076] 241230.154858.6181: DomainConfigWizard: Next Page: progressPage
[9732] 241230.154901.9764: DomainManagerObjectModel: InvokeAsync: action resulted in exception: System.ServiceModel.FaultException`1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. **This error has been logged. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.**
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.Check...).
[9732] 241230.154901.9774: DomainManagerObjectModel: InvokeAsync: handling exception by transferring to eventArgs
[14076] 241230.154901.9824: DomainConfigWizard: Error occurred in Domain Manager Object Model operations: System.ServiceModel.FaultException`1[Microsoft.WindowsServerSolutions.RemoteAccess.Domains.DomainManagerFault]: The creator of this fault did not specify a Reason. (Fault Detail is equal to DomainManagerFault:[Reason:CommunicationFailure, Message:SubmitCertificateRequest failed, Detail:System.Web.Services.Protocols.SoapException: Live Dynamic DNS has encountered an internal error. **This error has been logged. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.**
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.Check...).
[14076] 241230.154901.9824: DomainConfigWizard: FailReason from Domain Manager Object Model operations: CommunicationFailure
![](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(179.20000000000002, 35%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
It's now end of January and I am still having the same issue. It's impossible to renew an expired certificate on remotewebaccess.com.
I did re-try to renew the certificate after installing 2025-02 update. On one server it suprisingly worked on first attempt. Excited by the success I tried on additional servers and on most of them it failed. But the process did not fail immediately as it was the case before so it looks like somehow it ended up in timeout. So I continued re-trying and eventually succeeded after 10+ retries. So bottom line is it seems to work again somehow.
Well for me just another wakeup call to continue the migration of said customers away from all Microsoft services. I've got better things to do with my time than explaining my business customers over and over again that Microsoft screwed us over, discontinued services and pushing for cloud integration, forcing to share my password with the Microsoft cloud just to use an Outlook with much worse usability than before etc... I stop here as I better use the time to help my customers to operate stable services. Somehow I am sad as a 30+ years partnership is ending. Happy though that given this Microsoft strategy I am getting more consumer requests for help than ever before in history.
Good luck if you stay with Microsoft services though. The huge involvement and response from Microsoft on threads like these will sure help you on your path forward.
I have given up on using the Microsoft promoted domain name (remotewebaccess.com).
Found on internet a method to use a custom domain name on a free DNS service and I am using a "Let's Encrypt" certificate from early January.
Used for the search := How To Manually Set Up A Custom Domain Name Windows Server Essentials
