We had an issue last week with a deployment target in our Production environment during a release. The error was "An error occurred when sending a request to ‘https://xxx:10933/’, before the request could begin: No connection could be made because the target machine actively refused it. [::ffff:xx.xx.xxx.xxx]:10933 No connection could be made because the target machine actively refused it. [::ffff:xx.xx.xxx.xxx]:10933
The target was showing as unavailable. A health check on it seemed to make it available again.
Selected extracts from the log files are included below but it seems as though:
1 - The service was not running even though the service was set to automatic startup
2 - The health check seemed to start the service
3 - There is a certificate error. Not sure which certificate this relates to
From the logs:
Server
2021-03-18 08:42:43.4678 1604 499 ERROR https://xxx:10933/ 499 The remote host at https://xxx:10933/ refused the connection. This may mean that the expected listening service is not running.
Target
2021-03-18 08:57:59.7284 3052 7 INFO listen://[::]:10933/ 7 Listener started
2021-03-18 08:57:59.7284 3052 7 INFO The Windows Service has started
2021-03-18 08:59:39.3184 3052 9 INFO listen://[::]:10933/ 9 Client at [::ffff:xx.xx.xxx.xxx]:51258 authenticated as xxx
2021-03-18 09:03:06.0007 3052 3 INFO listen://[::]:10933/ 3 Client failed authentication: [::ffff:xx.xx.xxx.xxx]:52744
System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. —> System.ComponentModel.Win32Exception: An unknown error occurred while processing the certificate