Client health check fails

Legacy Uncategorised
1

Hi,

The client machine stopped responding to the server. It used to work before.

I have checked the port and it seems to be listening. And the thumbprint are matching between the server and client.

https://localhost:10933 doesn’t seem to work in the client machine. And I am not able to figure out why.

The client log files have - The client and server cannot communicate, because they do not possess a common algorithm
The diagnostics page says - An error (1301) occurred while enumerating the groups. The group’s SID could not be resolved.

I have attached the log files for your reference. AN

Octopus.zip (632 KB)

2

Hi Sthangavelu,

Thanks for getting in touch. This error:

The client and server cannot communicate, because they do not possess a common algorithm

Happens when Octopus and Tentacle try to communicate and need to decide whether to use TLS 1.0, 1.1 or 1.2.

Tentacle versions prior to 3.1 only supported TLS 1.0.

Octopus 3.1 and above speak TLS 1.0, 1.1 and 1.2.

Now, the versions of TLS can also be restricted by Windows, and apply to the whole machine. So a common problem is:

  1. Tentacle only speaks TLS 1, but it’s OK and everything works
  2. A company adopts PCI DSS 3.1 which says TLS 1.0 is not to be used
  3. They disable TLS 1.0 on their web servers, so that IIS no longer uses it
  4. Now suddenly Tentacle can’t speak TLS 1.0 anymore.

Solutions are: upgrade to a newer Tentacle (requires .NET 4.5) or re-enable TLS 1.0.

Running a tool like IISCrypto on the Tentacle server might tell you if TLS 1.0 has been disabled:

https://www.nartac.com/Products/IISCrypto

Hope this helps!

Paul Stovell