Forum Discussion
is the Microsoft Remote Connectivity Analyzer broken?
I am having issues configuring my autodiscover configuration after an exchange server rebuild (Single exchange server which failed and had to be rebuilt using the setup.exe /m:recover option) and it'...
bradhugh
Microsoft
Microsoftmohsan466 - yes, sorry for the delay. We released a new deployment which seems to have resolved the issue. If you are still having problems, send mail using the feedback link in the footer of the site with your specific issue and someone can take a look.
bradhugh I can't agree with BasL86 the Remote Connectivity Analyzer shows with Sectico Certificate still the Same result and issue that
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.- bradhughgabrielsix - Our telemetry has shown a drastic drop of this error after our latest deployment. Can you send me a private message with your URL (assuming it's accessible from the internet)? I can try to see if I can figure out what's going wrong.
- This is still an issue for me. Since the error message suggests that the cert could not be obtained (as opposed to: could not be validated), the issuing CA should be irrelevant, but as others mentioned theirs: We are using LetsEncrypt certs. The server is also behind a reverse proxy, but that should not play a role either until a specific URL is requested (hence *after* TLS negotiation)
