We have ServiceControl running on a virtual machine and Service Pulse installed in IIS. ServicePulse reaches ServiceControl through a redirect in IIS. Also, we have a valid certificate set up in the IIS site.
This configuration works fine for ServicePulse. The problem is that when I try to access ServiceControl from ServiceInsight in url https://sp.mydomain.com/api, I get the error in the screenshot:
Any idea on how to resolve it? Note that the SSL certificate is valid.
I have the feeling that the problem is not the certificate itself. Note that I’m trying to access a remote url (hosted in IIS), not localhost, configured following Install ServicePulse in IIS • ServicePulse • Particular Docs and using Windows Authentication.
{"description":"The management backend for the Particular Service Platform",
"endpoints_error_url":"http://localhost:33320/api/endpoints/{name}/errors/{?page, ...
Note that the url is the internal localhost url, not the one with the domain name. I’m wondering if ServiceInsight is trying to access these localhost urls…
Right. I just tested the same thing… I got stuck on the message, which confused me. Is there anyway this can work with a (relatively) secured service control API?
@fcastells Is it correct that you have this working with only encryption but without any form of authentication?
What type of authentication did you test? You said you have Windows Authentication enabled in IIS but is the Windows client part of that same domain?
Workaround:
A workaround although not really friednly is to install ServiceInsight on the same box as ServiceControl and RDP into that machine. Alternatively, you could install it on its own VM and make that machine trusted to access the ServiceControl API directly via for example the IP address from that machine. Control access via your active directory users/groups to that RDP/VM.