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

Legacy Execution
1

Unable to connect to a tentacle from OD server or local web browser. Confirmed TLS 1.0, 1.1 and 1.2 are all enabled by registry, IISCrypto and IE on the tentacle and the server. Get errors:

2017-10-09 12:50:50.6855 7584 8 INFO listen://[::]:10933/ 8 Unhandled error when handling request from client: [::ffff:30.200.128.15]:55536
System.ComponentModel.Win32Exception (0x80004005): The client and server cannot communicate, because they do not possess a common algorithm
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Halibut.Transport.SecureListener.d__15.MoveNext()
2017-10-09 12:51:55.8772 7584 8 INFO listen://[::]:10933/ 8 Accepted TCP client: [::1]:54136
2017-10-09 12:51:55.8772 7584 8 INFO listen://[::]:10933/ 8 Performing TLS server handshake
2017-10-09 12:51:55.8982 7584 9 INFO listen://[::]:10933/ 9 Unhandled error when handling request from client: [::1]:54136
System.IO.IOException: The handshake failed due to an unexpected packet format.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Halibut.Transport.SecureListener.d__15.MoveNext()

Octopus Deploy version 3.13.10
Octopus Deploy Tentacle: 3.16.0

OctopusTentacle.txt (45 KB)

2

Hi Chris,

Thanks for getting in touch.

I get the error The handshake failed due to an unexpected packet format. when attempting to browse locally via http instead of https. Does https work for you?

The client and server cannot communicate, because they do not possess a common algorithm usually indicates a TLS issue. I’m not sure what the problem might be if you have TLS 1.0, 1.1 and 1.2 enabled and running on Windows 2012. Would you mind sending a screenshot of your IISCrypto settings?

It looks like you have already found it, but we have a TLS troubleshooting page here: https://octopus.com/docs/reference/octopus-tentacle-communication/troubleshooting-schannel-and-tls

I’ve double checked that we haven’t broken compatibility between Octopus Server version 3.13.10 and Octopus Tentacle version 3.16.0. What OS is your Octopus Server running on?

Cheers,
Shane