I’ve installed Octopus on Azure via the ARM template.
The portal was available on port 80.
In the configuration I was able to configure LetsEncrypt, but was not able to access the portal via https. I did add an inbound rule on the Azure network security group.
The solution was to add an inbound firewall rule on the Octopus Virtual Machine for port 443.
Ideally this could either be set via the ARM template or via the LetsEncrypt configuration (better as this would work on non Azure environments as well).
Thanks for getting in touch! We have a documentation page relating to the configuration of Let’s Encrypt. On our documentation page we have a note under the Troubleshooting section that local firewall will need to be allowed access to the port you configured.
I do not believe this is something we can automate, so manually updating the firewall is required when configuring this as you have experienced.
If you have any further thoughts or questions on this, please don’t hesitate to let me know.
Sorry, I missed that part of the documentation.
I just wanted to let you know what could be improved.