Install Let's Encrypt module on Octopus Cloud to enable a CNAME for ODC instances
With Octopus Cloud 2012.5.9 we can’t assign our own CNAME to the server instance due to the Let’s Encrypt module being missing.
It is ok for internal use, but if we want Tenants to have access to see what we’ve deployed for them, then we would want to use octopus.mycompany.com not mycompany123.octopus.app.
It might seem minor, but does Octopus use firstname.lastname@example.org as your public email address for customers? Nope, and we don’t want to either :-)
Please add back the excellent Let’s Encrypt module in Octopus Cloud and route port 80 or just .well-known/acme-challenge/ to the relevant instance. Octopus Cloud customers can create their own CNAME record, and we are back in our happy place / domain.
Aaron Roydhouse commented