RWS.Proxy and ECP.Proxy health checks, localhost, and SSL

Question

RWS.Proxy and ECP.Proxy health sets are both failing. In both of the errors, I find the following:
[000.000] Starting HTTP request task
[000.000] Waiting 59000 ms
[000.000] Issuing GET against https://localhost/ecp/
[000.000] Awaiting GET response
[000.000] Performing SSL validation
[000.000] Performing SSL validation
[000.000] Failed with exception: The underlying connection was closed: An unexpected error occurred on a receive.
[000.000] Starting HTTP request task
[000.000] Waiting 59000 ms
[000.000] Issuing GET against https://localhost/ecp/ReportingWebService/
[000.000] Awaiting GET response
[000.000] Performing SSL validation
[000.000] Performing SSL validation
[000.000] Failed with exception: The underlying connection was closed: An unexpected error occurred on a receive.
We require SSL on all connections. We use a third party certificate with multiple SANs. Since the probe is trying to use https://localhost, it fails because the name doesn't match.
I figure I have a few options: first, is there a way to change the URL that the probe uses to check. This seems to me to be the 'rightest' way I could fix this. Second could I alter the binding of the site so that the localhost hostname uses a dedicated,
self signed, trusted cert? Last, is there any way to simply disable the specific probes? We're a single server low volume setup and I'm not convinced that I need the probes anyway.
IS this a common issue? Outside of the warnings that SCOM throws at me, it is also causing a large volume of logs to be generated.
Justin Cervero - MS Enterprise Admin - Appalachian State University

Answer 1

Hi,
I am afraid it’s hard coded. Just like the “Test-Outlookwebsiervices” command, it will also try the “localhost” and reports errors about certificate host name mismatch issue.
We can safely ignore this report.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support