We changed the bindings of our Octopus Server install and added a https binding for a specific domain. After restarting the machine we were unable to bring up the Web Management portal as it was throwing a 503 Service Unavailable. Any help would be greatly appreciated!
Thanks for getting in touch. I’m sorry you’re hitting this error in your web portal! Could you provide the following information to help us troubleshoot what could be causing this error?
Screenshots of your certificate configuration
Your server logs (located in C:/Octopus/Logs in standard installations)
Can you access your web portal after changing it back to HTTP?
Can you confirm the HTTPS binding for your web portal was configured as shown in our documentation page?
I look forward to hearing back and getting to the bottom of this.
We finally realized that after using the Change Bindings feature in the
Octopus Manager that the ACL rule for our service account was removed we
ended up having to run a command to add back the permissions to the account
for the url to the octopus portal.