Polling tentacle behind a proxy is failing to reach the server

Legacy Uncategorised
1

Hi there,

I’m trying to setup a polling tentacle behind a transparent squid proxy to communicate with the Octopus server. The polling tentacle is able to verify the given credentials and even register itself in the Octopus server but as soon as the wizard finishes, the Tentacle logs shows errors like this:

System.Net.Sockets.SocketException (0x80004005): No such host is known

Here are the steps performed in the Tentacle box:

  1. Install Octopus Tentacle 3.4.9
  2. In the wizard, set the Communication style to Polling Tentacle
  3. Check the option Use the proxy server configured in Internet Explorer
  4. Set the Octopus Credentials and click to verify credentials (as image 01.png)
  5. Assign environment and roles to register the new Tentacle. At this point I was able to see all the existing environments and roles from the server.
  6. Install the Tentacle as the image 02.png.

The wizard finishes successfully (it is possible to see the new tentacle registered in the Octopus Server) but from this point the Tentacle is not able to reach the Octopus server. Analysing the OctopusTentacle.log it shows multiple errors like the following one:

2016-09-19 05:22:18.3758      7  INFO  Agent will trust Octopus servers with the thumbprint: 5EAC769061E79FDB69xxxxxxxxxxxxxxxx
2016-09-19 05:22:18.3758      7  INFO  Agent will poll Octopus server at https://oc.inside.xxxxxxxxxxx:10943/ for subscription poll://9x2mcx4823yxxxxxxwl/ expecting thumbprint 5EAC769061E79FDB69xxxxxxxxxxxxxxxx
2016-09-19 05:22:18.3758      7  INFO  Agent configured to use the system proxy, but no system proxy is configured for https://oc.inside.xxxxxxxxxxx:10943/
2016-09-19 05:22:18.3758      7  INFO  Agent will not listen on any TCP ports
2016-09-19 05:22:18.3758      7  INFO  The Windows Service has started
2016-09-19 05:22:18.3913      8  INFO  https://oc.inside.xxxxxxxxxxx:10943/    8  Opening a new connection
2016-09-19 05:22:18.4070      8  INFO  https://oc.inside.xxxxxxxxxxx:10943/    8  No such host is known
System.Net.Sockets.SocketException (0x80004005): No such host is known
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
   at Halibut.Transport.TcpClientExtensions.ConnectWithTimeout(TcpClient client, String host, Int32 port, TimeSpan timeout) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\TcpClientExtensions.cs:line 34
   at Halibut.Transport.TcpClientExtensions.ConnectWithTimeout(TcpClient client, Uri remoteUri, TimeSpan timeout) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\TcpClientExtensions.cs:line 12
   at Halibut.Transport.SecureClient.CreateConnectedTcpClient(ServiceEndPoint endPoint) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureClient.cs:line 138
   at Halibut.Transport.SecureClient.EstablishNewConnection() in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureClient.cs:line 118
   at Halibut.Transport.SecureClient.ExecuteTransaction(Action`1 protocolHandler) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureClient.cs:line 54
2016-09-19 05:22:23.4226      8  INFO  https://oc.inside.xxxxxxxxxxx:10943/    8  Opening a new connection
2016-09-19 05:22:23.4226      8  INFO  https://oc.inside.xxxxxxxxxxx:10943/    8  No such host is known
System.Net.Sockets.SocketException (0x80004005): No such host is known
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
   at Halibut.Transport.TcpClientExtensions.ConnectWithTimeout(TcpClient client, String host, Int32 port, TimeSpan timeout) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\TcpClientExtensions.cs:line 34
   at Halibut.Transport.TcpClientExtensions.ConnectWithTimeout(TcpClient client, Uri remoteUri, TimeSpan timeout) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\TcpClientExtensions.cs:line 12
   at Halibut.Transport.SecureClient.CreateConnectedTcpClient(ServiceEndPoint endPoint) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureClient.cs:line 138
   at Halibut.Transport.SecureClient.EstablishNewConnection() in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureClient.cs:line 118
   at Halibut.Transport.SecureClient.ExecuteTransaction(Action`1 protocolHandler) in Z:\BuildAgent\work\e1bda71fea4b4831\source\Halibut\Transport\SecureClient.cs:line 54

From the Tentacle box I’m able to reach the Octopus server on port 10943 (https://oc.inside.xxxxxxxxxxx:10943) and also the login page.
Seems that the proxy configuration the Tentacle is using to poll the Server is different from what was previously configured in the wizard setup.

Thank you,
Bruno Rubin.

01.png
01.png889×608 24.6 KB

02.png
02.png890×610 29.3 KB

2

Hi Bruno,
​ I’m sorry to hear that you have been having problems the the proxy support for Tentacles.
​I have run into problems myself trying to use a proxy in between a Polling Tentacle and the Server. During the installation process, the credentials test takes place over a standard .net HTTPWebRequest however the Tentacle->Server communications uses a custom library which appears to be having some problems with proxies.
​I have created GitHub ticket 2774 and marked it with a high importance so that it gets further investigated as soon as possible. Please keep an eye on this ticket for further notifications as to its progress.
​Once again our apologies for these issues that you hit trying to set up your Tentacles.
​Cheers,
​Rob

3

Hi Rob,
glad you could reproduce the issue. I’ll keep on eye on the GitHub ticket.
Thanks for your update, really appreciate your help.

Cheers,
Bruno.

4

The issue was fixed in 3.4.10.
Thanks Rob for your help.

Cheers,
Bruno.