Issue with tentacle setup

I am just setting up Octopus now, I was able to get tentacle installed on one server successfully and is shows green on the Octopus dashboard. The second however seems to be timing out. I note that the rule is in place to open the default firewall port;

Version:1.0 StartHTML:000000204 EndHTML:000577872 StartFragment:000576145 EndFragment:000577767 StartSelection:000576145 EndSelection:000577767 SourceURL:

Octopus v2018.4.10

The client was unable to establish the initial connection within 00:01:00 Halibut.HalibutClientException at Halibut.Transport.DiscoveryClient.Discover(ServiceEndPoint serviceEndpoint) at Octopus.Server.Web.Api.Actions.MachineDiscovery.TentacleDiscovery.Discover(String host, Int32 port, ProxyDetails proxy) at Octopus.Server.Web.Api.Actions.DiscoverMachineResponder.Discover(String host, Int32 port, Nullable1 discoverableEndpointType, ProxyDetails proxyDetails) at Octopus.Server.Web.Api.Actions.DiscoverMachineResponder.ExecuteRegistered() at Octopus.Server.Web.Infrastructure.Api.Responder1.Respond(TDescriptor options, NancyContext context) 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.Infrastructure.OctopusNancyModule.<>c__DisplayClass14_0.<get_Routes>b__1(Object x) at CallSite.Target(Closure , CallSite , Func`2 , Object ) at Nancy.Routing.Route.<>c__DisplayClass4.<Wrap>b__3(Object parameters, CancellationToken context) --Inner Exception-- The client was unable to establish the initial connection within 00:01:00 Halibut.HalibutClientException at Halibut.Transport.TcpClientExtensions.ConnectWithTimeout(TcpClient client, String host, Int32 port, TimeSpan timeout) at Halibut.Transport.DiscoveryClient.CreateConnectedTcpClient(ServiceEndPoint endPoint) at Halibut.Transport.DiscoveryClient.Discover(ServiceEndPoint serviceEndpoint)


Thanks for contacting us. The only suggestion I can give at the moment is to go through our tentacle troubleshooting guide here -

Specific things to try would be to check if you can access https://:10933/ to see if the tentacle is running, and can be accessed from an external machine.

Good luck, and let me know how it goes.

Thanks I will be checking those troubleshooting tips out. The server in question is in the PCI zone so I am sure that is where the problem lies. I’ll struggle with it today and see if I can get it connected. Thanks

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.