Polling Tentacle problems after 3 upgrade

Hi

Server 3.2.1
Tentacle 3.2.1

Having some issues getting a polling tentacle setup after upgrading to 3.2.1. The upgrade worked fine on 2 of our 3 environments, the third is causing some problems though.

I got to the point where I am trying a clean install of the tentacle and I get the following

2015-11-11 18:24:56.0581      1  INFO  Saving instance: Tentacle
2015-11-11 18:24:58.1050      1  INFO  A certificate already exists, no changes will be applied.
2015-11-11 18:24:59.8862      1  INFO  Removing all trusted Octopus servers...
2015-11-11 18:25:02.3706      1  INFO  Home directory set to: C:\Octopus
2015-11-11 18:25:02.8394      1  INFO  Application directory set to: C:\Octopus\Applications
2015-11-11 18:25:02.9956      1  INFO  Services listen port: 10933
2015-11-11 18:25:03.0113      1  INFO  Tentacle will not listen on a port
2015-11-11 18:25:05.1050      1  INFO  Checking connectivity on the server communications port 10943...
2015-11-11 18:25:09.7144      1 ERROR  ===============================================================================
2015-11-11 18:25:09.7301      1 FATAL  The service listening on https://deploy.drivesoftware.co.nz:10943/ does not appear to be an Octopus server. The response was: 
<!doctype html>
<html>
<head>
    <meta charset='utf8'>
    <meta http-equiv='x-ua-compatible' content='ie=edge'>
    <title>Octopus Server</title>
    <style type='text/css'>
        body {
            font-family: 'Segoe UI', 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif;
            font-size: 10pt;
        }

        h1 {
            font-size: 15pt;
            font-weight: 400;
            margin-top: 7pt;
            margin-bottom: 7pt;
        }
    </style>
</head>
<body>
    <h1>Octopus Server configured successfully</h1>
    <p>If you can view this page, your Octopus Server is configured and ready to accept requests from Polling Tentacles.</p>
    <p>This landing page is displayed when no X509 certificate is provided. Only Octopus Tentacles with a trusted certificate can connect to this Octopus Server.</p>
</body>
</html>
System.Exception: The service listening on https://deploy.drivesoftware.co.nz:10943/ does not appear to be an Octopus server. The response was: 
<!doctype html>
<html>
<head>
    <meta charset='utf8'>
    <meta http-equiv='x-ua-compatible' content='ie=edge'>
    <title>Octopus Server</title>
    <style type='text/css'>
        body {
            font-family: 'Segoe UI', 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif;
            font-size: 10pt;
        }

        h1 {
            font-size: 15pt;
            font-weight: 400;
            margin-top: 7pt;
            margin-bottom: 7pt;
        }
    </style>
</head>
<body>
    <h1>Octopus Server configured successfully</h1>
    <p>If you can view this page, your Octopus Server is configured and ready to accept requests from Polling Tentacles.</p>
    <p>This landing page is displayed when no X509 certificate is provided. Only Octopus Tentacles with a trusted certificate can connect to this Octopus Server.</p>
</body>
</html>
   at Octopus.Tentacle.Commands.RegisterMachineCommand.<>c__DisplayClass14_0.<CheckServerCommunicationsPortIsOpen>b__1() in Y:\work\refs\tags\3.2.1\source\Octopus.Tentacle\Commands\RegisterMachineCommand.cs:line 149
   at Octopus.Tentacle.Commands.RegisterMachineCommand.Retry(Action action, Int32 retryCount, TimeSpan initalDelay, Double backOffFactor) in Y:\work\refs\tags\3.2.1\source\Octopus.Tentacle\Commands\RegisterMachineCommand.cs:line 124
   at Octopus.Tentacle.Commands.RegisterMachineCommand.CheckServerCommunicationsPortIsOpen(Uri serverAddress) in Y:\work\refs\tags\3.2.1\source\Octopus.Tentacle\Commands\RegisterMachineCommand.cs:line 137
   at Octopus.Tentacle.Commands.RegisterMachineCommand.Start() in Y:\work\refs\tags\3.2.1\source\Octopus.Tentacle\Commands\RegisterMachineCommand.cs:line 73
   at Octopus.Shared.Startup.AbstractCommand.Octopus.Shared.Startup.ICommand.Start(String[] commandLineArguments, ICommandRuntime commandRuntime, OptionSet commonOptions) in Y:\work\refs\tags\3.2.1\source\Octopus.Shared\Startup\AbstractCommand.cs:line 57
   at Octopus.Shared.Startup.ConsoleHost.Run(Action`1 start, Action shutdown) in Y:\work\refs\tags\3.2.1\source\Octopus.Shared\Startup\ConsoleHost.cs:line 72
   at Octopus.Shared.Startup.OctopusProgram.Run() in Y:\work\refs\tags\3.2.1\source\Octopus.Shared\Startup\OctopusProgram.cs:line 87
2015-11-11 18:25:11.5582      1  INFO  Deleted instance: Tentacle

So the response from the server is the landing page for a successful configuration, but the Tentacle doesn’t like it.

Thanks
Simon

Hi Simon,

Thanks for reaching out. From which version of Octopus did you upgrade to 3.2.1? Please take a look at out Polling Tentacle troubleshooting guide and let us know if that helps http://docs.octopusdeploy.com/display/OD/Polling+Tentacles

Regards,

Dalmiro

Hi Dalmiro

This is my issue https://github.com/OctopusDeploy/Issues/issues/2134. I have worked around it by installing 3.1.7 tentacles to do the registration then letting the self update process do its thing.

Thanks
Simon

Hi Simon,

I’m glad to hear you found a workaround. That was a nasty bug and we’ll ship a fix for it in 3.2.2.

Thanks and sorry for the inconveniences caused by this issue.

Dalmiro