Our octopus server was set up by someone who has since left the company.
We have a certificate issued for our own domain " octopus.defriesland.nl " and that works when using octopus web interface, however, in the Octopus manager bindings page I can only see “localhost” .
The certificate is installed on the machine but I can’t see how they are configured with octopus anywhere.
Because I have to change the current certificate to a new one, I need to know how I can resolve this issue.
OD Version: V2018.3.2
Used URL: https://octopus.defriesland.nl/
No IIS installed
No Loadbalancer
Hello,
Thanks for getting in touch! I’m sorry to hear you are seeing issues changing the SSL Certificate bindings in Octopus.
Specifying localhost as the binding will cause this to bind to the local Ip address of 0.0.0.0/0 on the Octopus Server which is the equivalent of accepting connections from anywhere.
If you have already imported your renewed certificate in the Octopus Servers’ personal or web hosting local certificate store (at the local computer scope) You can update the certificate used here by first deleting the existing https://localhost/ entry and adding a new one by following the documentation on changing the web portal bindings manually
I hope this has been informative, please let me know if you have any further questions.
Hello Lawrence,
Thus if a make a new binding and attach the new certificate, ODS will pick this up and the binding, which was made bij a former employe and is not visible to me, will be updated with the new certificate.
Hello,
Thanks for keeping in touch! You are absolutely correct, if you add a more specific binding and attach your new certificate, Octopus will pick it up.
