Polling tentacle not registering

I’m trying to use polling tentacle and they are not setting up correctly. Our Octopus server is an Azure VM and we’ve opened port 10943 to it, I’ve checked the VM can connect to the server as I can telnet from it on that port to the Octopus server. I’m using an API key to connect and verifying the credentials works fine but the moment I try and install the following error appears.

2017-03-28 10:35:53.4681 1 INFO A certificate already exists, no changes will be applied.
2017-03-28 10:35:56.8193 1 INFO Home directory set to: C:\Octopus
2017-03-28 10:35:56.9353 1 INFO Application directory set to: C:\Octopus\Applications
2017-03-28 10:35:57.1873 1 INFO Services listen port: 10933
2017-03-28 10:35:57.4503 1 INFO Tentacle will not listen on a port
2017-03-28 10:35:59.9073 1 INFO Proxy username cleared
2017-03-28 10:36:00.0163 1 INFO Proxy password cleared
2017-03-28 10:36:00.3013 1 INFO Proxy use is disabled
2017-03-28 10:36:03.0382 1 INFO Checking connectivity on the server communications port 10943…
2017-03-28 10:36:05.7788 1 ERROR ===============================================================================
2017-03-28 10:36:06.9134 1 FATAL The request was aborted: Could not create SSL/TLS secure channel.
at System.Net.HttpWebRequest.GetResponse()
at Octopus.Tentacle.Communications.OctopusServerChecker.<>c__DisplayClass2_0.b__1() in OctopusServerChecker.cs:line 54
at Octopus.Tentacle.Communications.OctopusServerChecker.Retry(Action action, Int32 retryCount, TimeSpan initalDelay, Double backOffFactor) in OctopusServerChecker.cs:line 73
at Octopus.Tentacle.Communications.OctopusServerChecker.CheckServerCommunicationsPortIsOpen(Uri serverAddress, Int32 commsPort, IWebProxy proxyOverride) in OctopusServerChecker.cs:line 57
at Octopus.Tentacle.Commands.RegisterMachineCommand.StartAsync in RegisterMachineCommand.cs:line 91
at Octopus.Tentacle.Commands.RegisterMachineCommand.Start() in RegisterMachineCommand.cs:line 69
at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String[] commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions, String displayName, String version, String informationalVersion, String[] environmentInformation, String instanceName) in AbstractCommand.cs:line 78
at Octopus.Shared.Startup.OctopusProgram.Start(ICommandRuntime commandRuntime) in OctopusProgram.cs:line 252
at Octopus.Shared.Startup.ConsoleHost.Run(Action`1 start, Action shutdown) in ConsoleHost.cs:line 77
at Octopus.Shared.Startup.OctopusProgram.Run() in OctopusProgram.cs:line 101
2017-03-28 10:36:08.2774 1 INFO Deleted instance: Tentacle

When I try and browse https://localhost:10943/ on the Octopus Server it fails, even disabling the windows firewall on the VM doesn’t work.

Is there any other configuration on the server that I need to do for this to work?


Hi Richard,

Thank you got getting in touch. What error do you get browsing to https://localhost:10943/? A certificate error is expected and can be bypassed.

Please try restarting your server and checking the logs. It should output whether it successfully listened on the port. Also see our troubleshooting page.

Let me know if you still cannot resolve the problem,

Robert W

It would seem this problem is down to the OS of the connecting machine. As you seem to be able to get to the polling page from a Win 8.1 machine and it’s possible to register the agent.

When you connect from a Win 10 , 2012, 2012 R2 it doesn’t connect correctly. It could be down to the way I’ve locked down IIS on the Octopus Server. We use IISCrypto40 to set the server to FIPS 140-2 and also locked down the cipher list. I’m going to set the Octopus server back to default setting and see if that changes the behaviour.

Hi Richard,

Let me know how you go. This might help: https://octopus.com/docs/reference/octopus-tentacle-communication/troubleshooting-schannel-and-tls

Also we restrict protocols to TLS 1.0, 1.1 or 1.2.

For ease of testing, Tentacle Ping might help as well.


Robert W