Currently, https://odo.pydata.org/ serves an invalid certificate (valid only for readthedocs.org), but SSL on custom domains in Read the Docs should work more or less out-of-the-box. According to the documentation:
By default, when you setup a custom domain to host documentation at Read the Docs, we will attempt to provision a domain validated SSL certificate for the domain. This service is generously provided by Cloudflare.
From that same page, it would seem that one needs to use readthedocs.io (note the io instead of org) in the CNAME record to make use of this functionality though:
Some older setups configured a CNAME record pointing to readthedocs.org or another variation. While these continue to resolve, they do not yet allow us to acquire SSL certificates for those domains.
So presumably, if this functionality is something you would want to make use of (which would be nifty), it seems that all it takes is an update to the CNAME record and a bit of clicking around in the Read the Docs control panel:
Point the CNAME to readthedocs.io, with no subdomain, and re-request a certificate by saving the domain in the project admin
Currently, https://odo.pydata.org/ serves an invalid certificate (valid only for readthedocs.org), but SSL on custom domains in Read the Docs should work more or less out-of-the-box. According to the documentation:
From that same page, it would seem that one needs to use readthedocs.io (note the io instead of org) in the CNAME record to make use of this functionality though:
And this is probably the reason it fails for odo:
So presumably, if this functionality is something you would want to make use of (which would be nifty), it seems that all it takes is an update to the CNAME record and a bit of clicking around in the Read the Docs control panel: