Unable to register a polling tentacle with Octopus Cloud


I’m getting a certificate error when trying to register my polling tentacle with my new Octopus Cloud instance. The client platform is fully updated Ubuntu 18.04.4 and I’m following instructions from https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle#setting-up-a-tentacle-instance

Name of Tentacle instance (default Tentacle):
Invalid characters will be ignored, the instance name will be: 'Tentacle'

What kind of Tentacle would you like to configure: 1) Listening or 2) Polling (default 1): 2
Where would you like Tentacle to store log files? (/etc/octopus):
Where would you like Tentacle to install appications to? (/home/Octopus/Applications):
Octopus Server URL (eg. https://octopus-server): https://nirs.octopus.app
Select auth method: 1) API-Key or 2) Username and Password (default 1): 1
API-Key: <redacted>
Select type of Tentacle do you want to setup: 1) Deployment Target or 2) Worker (default 1): 1
What Space would you like to register this Tentacle in? (Default):
What name would you like to register this Tentacle with? (vm-as482): nirs.hse.ru
Enter the environments for this Tentacle (comma seperated): Production
Enter the roles for this Tentacle (comma seperated): server
The following configuration commands will be run to configure Tentacle:
sudo /opt/octopus/tentacle/Tentacle create-instance --instance "Tentacle" --config "/etc/octopus/Tentacle/tentacle-Tentacle.config"
sudo /opt/octopus/tentacle/Tentacle new-certificate --instance "Tentacle" --if-blank
sudo /opt/octopus/tentacle/Tentacle configure --instance "Tentacle" --app "/home/Octopus/Applications" --noListen "True" --reset-trust
sudo /opt/octopus/tentacle/Tentacle register-with --instance "Tentacle" --server "https://nirs.octopus.app" --name "nirs.hse.ru" --comms-style "TentacleActive" --server-comms-port "10943" --apiKey "API-XXXXXXXXXXXXXXXXXXXXXXXXXX" --space "Default" --environment "Production"  --role "server"
sudo /opt/octopus/tentacle/Tentacle service --install --start --instance "Tentacle"
Press enter to continue...
Saving instance: Tentacle
Setting home directory to: /etc/octopus/Tentacle
A certificate already exists, no changes will be applied.
Removing all trusted Octopus Servers...
Application directory set to: /home/Octopus/Applications
Tentacle will not listen on a port
These changes require a restart of the Tentacle.
Checking connectivity on the server communications port 10943...
Connected sucessfully
Registering the tentacle with the server at https://nirs.octopus.app/
Detected automation environment: NoneOrUnknown
The following certificate errors were encountered when establishing the HTTPS connection to the server: RemoteCertificateChainErrors
Certificate subject name: CN=*.octopus.app
Certificate thumbprint:   7F8897DDF3E4AB07B7F2E027EA7D233E99A3FD1A

Then it just repeats the last 3 lines over and over again.

Now, I’m just starting with Octopus so I might’ve missed something obvious, but I couldn’t find anything related anywhere in the docs. I noticed that the certificate thumbprint at https://nirs.octopus.app/app#/Spaces-1/configuration/thumbprint is not the same as the one in the error but I don’t know what to make of it.

Can you help me diagnose this further please?

Hi kojo,

Thanks for reaching out - sadly we had an issue over the weekend where one of the CA-supplied intermediate certificates in our chain expired. We do have a new certificate, but we will need to re-provision your instance to apply it. Are you happy with us going ahead with this now, outside your maintenance window, to get this resolved?

Look forward to hearing from you soon.


@jeremy.miller sure, go ahead with the re-provisioning, it’s an empty instance.

Hi @kojo,

The process is complete. Can you please retry and let me know if it resolved the issue?


This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.