My company has an Octopus Server on-premise that has been in use for many years. Im now tasked with helping to move this to Octopus Cloud.
With the Octopus Server on-premise it has a use-case to deploy into an Azure VM that is private. It does this via proxy. That works fine.
I now have a brand new Octopus Cloud instance but I am unable to get it to talk to the same deployment target via the same proxy. The connectivity always times out after 1 minute.
I have confirmed that the proxy is publicly available over the internet and I can issue a curl request to the deployment targets tentacle via the proxy and that works fine.
I have also updated the trust on the deployment targets tentacle so it trusts both the old Octopus Server as well as the new Octopus Cloud instance. This was done via the following command and restarting the tentacle.
.\Tentacle.exe configure --instance “Listening Tentacle” --trust MYTHUMBPRINT
It is unclear to me why the Octopus Cloud instance can not communicate to the proxy, and I have no means to troubleshoot further. My assumption here is that the in-built worker has no outbound access to the Internet, but I’ve no means to verify that.
Using a custom worker doesn’t really solve any problems here because we wouldn’t be able to use a worker that is accessible over the Internet. Meaning we would need to use the same proxy that Octopus Cloud is already failing to connect to.
How is it that an Octopus Cloud instance is meant to connect to a proxy? How can I troubleshoot further why it can not connect?