Unable to setup a new Octopus Tentacle

I have a Windows Server 2012 R2 VM with IIS, URLReWrite, and Octopus Tentacle 3.2.7 x64 installed.
I can get to Tentacle locally (https://localhost:10933) and from the deployment server https://LAN-IP:10933

Using the Tentacle manager I went through the setup. Careful to copy and paste the thumbprint from Octopus. On the deployment side I added the machine by it’s LAN IP, gave it roles and an environment, and copied over the Tentacle’s thumbprint. However it doesn’t discover it and error when checking it’s health.

Here is the log from Octopus deploy:

Not connected. The machine has not completed a post-configuration handshake, so communication is not yet established.

Squid: Unknown

The last recorded failure on the connection was:

Error 10:23:47
Pipefish.Errors.PipefishCommunicationException: An existing connection was forcibly closed by the remote host
at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
at Octopus.Server.Communications.Handshaking.NewPassiveTentacleSquidFinder.d__5.MoveNext() in y:\work\refs\heads\master\source\Octopus.Server\Communications\Handshaking\NewPassiveTentacleSquidFinder.cs:line 45
Pipefish.PipefishException: The remote host aborted the connection. This can happen when the remote server does not trust the certificate that we provided. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
— End of inner exception stack trace —
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security._SslStream.StartFrameBody(Int32 readBytes, Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Stream.ReadByte()
at Pipefish.Transport.SecureTcp.ProtocolParser.ReadPrelude(Stream clientStream) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\ProtocolParser.cs:line 106
at Pipefish.Transport.SecureTcp.ProtocolParser.ParseResponse(SslStream responseStream, StatusCode& statusCode, String& statusText, ResponseHeaders& headers, String& protocol) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\ProtocolParser.cs:line 165
at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request, Action1 response) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 85 --- End of inner exception stack trace --- at Pipefish.Transport.SecureTcp.Client.SecureTcpClient.Send(SecureTcpRequest request, Action1 response) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\Client\SecureTcpClient.cs:line 105
at Octopus.Server.Communications.Handshaking.PassiveTentacleHandshaker.Receive(PassiveTentacleHandshakeRequest message) in y:\work\refs\heads\master\source\Octopus.Server\Communications\Handshaking\PassiveTentacleHandshaker.cs:line 56
at Pipefish.Actor.OnReceivingTyped[TBody](Message message) in y:\work\3cbe05672d69a231\source\Pipefish\Actor.cs:line 113

And from Tentacle log:

2015-12-01 15:24:57.6831 5 INFO Stopping the Windows Service
2015-12-01 15:24:57.7012 5 INFO listen://[::]:10933/ 5 Listener stopped
2015-12-01 15:24:57.7012 5 INFO The Windows Service has stopped
2015-12-01 15:24:59.8482 7 INFO Agent will trust Octopus servers with the thumbprint: 1CA96A701C4A80335EE2B7A939A8C2220248A740
2015-12-01 15:24:59.8802 7 INFO listen://[::]:10933/ 7 Listener started
2015-12-01 15:24:59.9112 7 INFO Agent listening on: [::]:10933
2015-12-01 15:24:59.9122 7 INFO The Windows Service has started
2015-12-01 15:25:06.1962 3 INFO listen://[::]:10933/ 3 Accepted TCP client: [::ffff:192.168.3.13]:22452
2015-12-01 15:25:06.1962 5 INFO listen://[::]:10933/ 5 Performing TLS server handshake
2015-12-01 15:25:06.2582 5 INFO listen://[::]:10933/ 5 Secure connection established, client is not yet authenticated, client connected with Tls
2015-12-01 15:25:18.2994 3 INFO listen://[::]:10933/ 3 Accepted TCP client: [::ffff:192.168.3.13]:22468
2015-12-01 15:25:18.2994 11 INFO listen://[::]:10933/ 11 Performing TLS server handshake
2015-12-01 15:25:18.2994 11 INFO listen://[::]:10933/ 11 Secure connection established, client is not yet authenticated, client connected with Tls
2015-12-01 15:25:36.2681 3 INFO listen://[::]:10933/ 3 Accepted TCP client: [::ffff:192.168.3.13]:22483
2015-12-01 15:25:36.2681 6 INFO listen://[::]:10933/ 6 Performing TLS server handshake
2015-12-01 15:25:36.2681 6 INFO listen://[::]:10933/ 6 Secure connection established, client is not yet authenticated, client connected with Tls
2015-12-01 15:26:06.2994 10 INFO listen://[::]:10933/ 10 Accepted TCP client: [::ffff:192.168.3.13]:22505
2015-12-01 15:26:06.2994 6 INFO listen://[::]:10933/ 6 Performing TLS server handshake
2015-12-01 15:26:06.2994 6 INFO listen://[::]:10933/ 6 Secure connection established, client is not yet authenticated, client connected with Tls
2015-12-01 15:26:36.3619 10 INFO listen://[::]:10933/ 10 Accepted TCP client: [::ffff:192.168.3.13]:22534
2015-12-01 15:26:36.3619 14 INFO listen://[::]:10933/ 14 Performing TLS server handshake
2015-12-01 15:26:36.3619 14 INFO listen://[::]:10933/ 14 Secure connection established, client is not yet authenticated, client connected with Tls

I’m stuck, can you help?

Hi Joshua,

Thanks for getting in touch! You say that you installed 3.2.7, however from your logs I am seeing Pipefish errors.
Pipefish was our connection layer in 2.x and Halibut is our connection layer in 3.x.
Can you confirm if an older version of Tentacle was installed on that server and is still active? Where is the Tentacle service pointing?
3.x Octopus cannot talk to 2.x Tentacles and vice versa.

If you let me know what version of Octopus you are using and if that machine has been used before maybe we can figure it out.

Thanks!
Vanessa

AHH. Didn’t realize that newer Tentacle didn’t work with our older deployment server. Found the right one, https://octopus.com/downloads/2.6.3 I’ll try it now.

Hi Joshua,

Here you go: https://octopus.com/downloads/2.6.3
On our downloads page there is a ‘previous releases’ link which allows you to grab any version you need.

Vanessa

Thank you!