When the Octopus UI is hosted in an HTTPS domain, it attempts to load some resources with HTTP:
This results in a warning/error in the browser. Note that this is most likely due to the fact that we are running behind a load balancer with SSL termination on the balancer.
Thanks for getting in touch! You’re right on the money - we are busily working on a patch to make these authentication provider resources work with relative URLs like everything else. This will make Octopus resilient to reverse proxies and SSL termination.
Follow this GitHub Issue to keep track of the resolution: https://github.com/OctopusDeploy/Issues/issues/2913
Hope that helps!