How can I having polling tentacles communicate with Octopus Deploy over another port?

tentacles
octopus-config
(Bob Walker) #1

Due to various security requirements, I cannot use port 10943 for polling tentacles. All I can use is port 80 and port 443. How can I accomplish this with Octopus Deploy?

(Bob Walker) #3

I should point out that in order to do this, you will need to leverage the command line interface for both the Octopus Server and the Tentacle.

On the server, you will need to run the configure octopus.server.exe command and set the --commsListenPort to the port you wish to have polling tentacles communicate with.

On the tentacle, you will need to run the register-with and set the --server-comms-port to the same port as above.

The register-with command uses the Octopus API to make queries and complete the registration. As such, if you are using https:// on your octopus server, then you should set the tentacle communication port to 80. If you are using http:// on your octopus server, then you should set the tentacle communication port to 443. Essentially you will want to have a separate port for polling communications.

If you want to use the same port, you will need to configure Polling Tentacles over Web Sockets.

Because you will be leveraging the CLI to configure your tentacle, please look at this documentation for some examples.