Unable to Add Tentacle in DMZ server

Legacy Uncategorised
1

Getting the following exception when trying to add a Deployment Target located in DMZ Server. I’ve also noticed that the certificate thumbprint changes after the tentacle is installed.

Octopus Tentacle 3.2.10 (Windows Server 2012 R2 )
Octopus Server 3.2.10 (Windows Server 2008 R2)

Halibut.HalibutClientException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [::ffff:xx.xx.xx.xxx]:10933 —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [::ffff:xx.xx.xx.xxx]:10933
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
at Halibut.Transport.TcpClientExtensions.ConnectWithTimeout(TcpClient client, Uri remoteUri, TimeSpan timeout) in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\TcpClientExtensions.cs:line 28
at Halibut.Transport.DiscoveryClient.Discover(Uri remoteUri) in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\DiscoveryClient.cs:line 22
— End of inner exception stack trace —
at Halibut.Transport.DiscoveryClient.Discover(Uri remoteUri) in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\DiscoveryClient.cs:line 42
at Octopus.Server.Web.Api.Actions.MachineDiscovery.TentacleDiscovery.Discover(String host, Int32 port) in Y:\work\refs\tags\3.2.10\source\Octopus.Server\Web\Api\Actions\MachineDiscovery\TentacleDiscovery.cs:line 26
at Octopus.Server.Web.Api.Actions.DiscoverMachineResponder.Discover(String host, Int32 port, Nullable1 discoverableEndpointType) in Y:\work\refs\tags\3.2.10\source\Octopus.Server\Web\Api\Actions\DiscoverMachineResponder.cs:line 69 at Octopus.Server.Web.Api.Actions.DiscoverMachineResponder.Execute() in Y:\work\refs\tags\3.2.10\source\Octopus.Server\Web\Api\Actions\DiscoverMachineResponder.cs:line 41 at Octopus.Server.Web.Infrastructure.Api.Responder1.Respond(TDescriptor options, NancyContext context) in Y:\work\refs\tags\3.2.10\source\Octopus.Server\Web\Infrastructure\Api\Responder.cs:line 162
at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2)
at CallSite.Target(Closure , CallSite , Object , Object , NancyContext )
at Octopus.Server.Web.Api.OctopusRestApiModule.<>c__DisplayClass0_0.<.ctor>b__0(Object o) in Y:\work\refs\tags\3.2.10\source\Octopus.Server\Web\Api\OctopusRestApiModule.cs:line 46
at CallSite.Target(Closure , CallSite , Func`2 , Object )
at Nancy.Routing.Route.<>c__DisplayClass4.b__3(Object parameters, CancellationToken context)

2

Hi Abhinand,

Thanks for getting in touch!

There are quite a few things that could be causing this issue, but ultimately it boils down to the Tentacle and Server not being able to talk to each other. Usually it’s caused by a network issue.

You mentioned that the Tentacle is located in a DMZ server. Can you confirm that the server is able to access this tentacle on port 10933? You should be able to do this by navigating to the Tentacle endpoint (e.g. https://yourtentacle:10933) in a browser and accepting the self-signed certificate. You should get an “Octopus Tentacle configured successfully” message.

Can you elaborate on “I’ve also noticed that the certificate thumbprint changes after the tentacle is installed.”? The Tentacle thumbprint is set when it gets installed. Until it’s installed, there shouldn’t be a thumbprint at all. What was it that changed and when?

Thanks,
Damo

3

This has to do with the firewall settings. I’m good now.
Thanks