Quick question - do we have to reconfigure all the existing tentacles after having added the new HTTPS binding? Currently we are using HTTP only. Note we will be bringing in our own certificate and using the Octopus Binding Wizard for adding the binding.
Thank you for contacting Octopus Support!
If you are just updating your certificate, there shouldn’t be any additional configuration for the tentacles.
Just in case, here is our documentation on adding an HTTPS binding: https://octopus.com/docs/security/exposing-octopus/expose-the-octopus-web-portal-over-https
If you have any other questions or run into any trouble let me know, we’re here to help.
Thanks for following up. I am enabling HTTPS first time on our Octopus setup. We have been using HTTP binding only. Besides the link you mentioned, here is another one - https://octopus.com/docs/security/octopus-tentacle-communication/custom-certificates-with-octopus-server-and-tentacle. Do I need to follow it?
Thanks for the quick reply.
If you are adding an HTTPS cert for the web UI, you won’t need to do anything with the tentacles. However, if you are wanting to use your own cert for server/tentacle communication, then that is guide you want to follow.
Hopefully that makes sense. Let me know if you have any more questions.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.