Sharing some issues I had getting polling to work

I just spent a frustrating afternoon and I thought if I shared the problems I had it might help someone. Also perhaps a couple of documentation changes and interface improvements might help. I’ve got it all working great now.

On the Octopus Credentials page in the Tentacle Setup Wizard, it was not clear to me that I need to specify the Octopus Server URL for the normal web interface and nothing to do with port 10943. We run our server on port 8080 and so I have to put https://my.octopus.server:8080/ here. I was trying https://my.octopus.server:10943/ and assuming I had a firewall issue.

Also, the Troubleshooting section says to try connecting to https://your-octopus:10943/. What am I supposed to see there? I only ever get ‘There is a problem with this website’s security certificate.’ and then if I continue I get ‘The webpage cannot be found’.

I found it was not obvious where to modify settings for the tentacle. The best way seems to be to delete the existing (default) setup and go through the wizard again. Also, once you’ve completed the setup, where can you see what settings are being used in the tentacle manager? E.g., which environment? which roles? what is the application directory?

Also, it still not clear to me which username/password I should use. Is this user account ONLY to register the tentacle? Or is it stored and used every time a poll takes place? What happens if I change the password of the user? Does it require the tentacle to be set up again?

Anyway, hope these notes help someone and I’m happy it’s all working now.


Hi Rob,

Thanks for the questions/feedback!

The username/password that you use is only for initial registration. During registration we set up the two-way trust relationship between Octopus and Tentacle based on the X.509 certificates rather than passwords.

You’re right that there are some limits with what can be done in Tentacle Manager at the moment; we’ll fix these in a future version. And thanks for the feedback on knowing which URL to enter, we’ll address this too.