Tentacle is configured on my windows nodes and then the nodes are shut off for a few days. During the instance requirement the nodes are turned on and an API call is made to register the node as a deployment target in Octopus. I am facing this failure while doing the registration:
Performing TLS handshake
March 30th 2022 04:24:12Info
Secure connection established. Server at [::ffff:172.29.40.171]:10933 identified by thumbprint: A5AF3690E316FC6713585770A2A085F23751BAF7, using protocol Tls12
March 30th 2022 04:24:12Info
Identifying as a client
March 30th 2022 04:24:12Error
Connection initialization failed while connecting to https://172-29-40-171.core.cvent.org:10933/ Halibut.Transport.Protocol.ConnectionInitializationFailedException: Unable to receive the remote identity; the identity line was empty.
—> Halibut.Transport.Protocol.ProtocolException: Unable to receive the remote identity; the identity line was empty.
— End of inner exception stack trace —
at Halibut.Transport.Protocol.MessageExchangeProtocol.ExchangeAsClient(RequestMessage request)
at Halibut.HalibutRuntime.<>c__DisplayClass41_0.b__0(MessageExchangeProtocol protocol)
at Halibut.Transport.SecureListeningClient.ExecuteTransaction(ExchangeAction protocolHandler, CancellationToken cancellationToken)
I tried following the workaround #2 mentioned in this article:
by running the commands:
C:\Program Files\Octopus Deploy\Tentacle>tentacle new-certificate
A new certificate has been generated and installed. Thumbprint:
These changes require a restart of the Tentacle.
C:\Program Files\Octopus Deploy\Tentacle>tentacle service --restart
Restarting service OctopusDeploy Tentacle
Waiting for service to become Stopped. Current status: StopPending
Waiting for service to become Stopped. Current status: Stopped
Waiting for service to become Running. Current status: StartPending
Waiting for service to become Running. Current status: Running
On retrying registration it still failed with this error:
An error occurred when sending a request to ‘https://172-29-40-171.core.cvent.org:10933/’, after the request began: The server at https://172-29-40-171.core.cvent.org:10933/ presented an unexpected security certificate. We expected the server to present a certificate with the thumbprint ‘A5AF3690E316FC6713585770A2A085F23751BAF7’. Instead, it presented a certificate with a thumbprint of ‘FCEE0BABE421A80F30537FA46E5509022C3FEF7A’ and subject ‘CN=Octopus Tentacle’. This usually happens when the client has been configured to expect the server to have the wrong certificate, or when the certificate on the server has been regenerated and the client has not been updated.
One weird observation:
After updating the thumbprint on the server, removing the deployment target and attempting registration again, i could notice that the thumbprint got updated to the current one but the underlined reference is still the old one.
Can someone please help?