The right way to do this seems to be tricky. We'd need to setup our on SSL on our machine and proxy it over to RTD. See actual instructions here: https://docs.readthedocs.io/en/latest/alternate_domains.html#cname-ssl Not urgent, but nice to have and something we should get around to at some point.
We already have a proxy, but I would rather first complete the work to have it in HA (which is not hard until you realize that letsencrypt is hard to set in cluster). I can however put it on the current proxy if we are ok with it being non HA.
Now that the proxy is HA, shall we think of having the HTTP bits done so we hit RTD via our proxy?
The HA proxies still requires some fixes in Ansible that I have added last week (they got merged, but now we have to wait on 2.5 to be released, then I will do a test reinstallation). I also would like to have at least 1 week of testing before switching stuff to it, and test the HA setup (aka "reboot during the day and see it switch").
*** Bug 1511263 has been marked as a duplicate of this bug. ***
So: - we are still waiting for fix to land in stable version of ansible (should be with 2.5, which is soon(tm). So any new deploy requires manual switch of ansible version. - docs.gluster.org got moved, and it work from here. It might take a while until that work fine everywhere due to DNS lag, but everything should go in SSL by default now. So closing.