3 ms·
I get that warning if I go to https://mycustomdomain.com https://mycustomdomain.com but I don't if I go to https://www.mycustomdomain.com https://www.mycustomdo
by city41 9y ago
I get that warning if I go to https://mycustomdomain.com https://mycustomdomain.com but I don't if I go to https://www.mycustomdomain.com https://www.mycustomdomain.com
- fladd 9y agoIt is the same for my domain. Seems to be a bug.
- epberry 9y agoSame here. Redirect from http -> https works fine tho.
- Philipp__ 9y agoSame here.
- fladd 9y agoI contacted GitHub support about this already. I hope this gets resolved soon.
- fladd 9y agoIt turns out that the apex for me now works only by accident, because I temporarily changed my custom domain to the apex form. This certificate will not get renewed, however. Only the domain that is active gets a certificate. That means that with https enabled it is no longer pssible to have the apex and www form of a custom domain work simultaneously at a GitHub page! One needs to decide for one or the other. As a workaround it was suggested to me to create a CNAME record from www to apex at the domain hoster. This, however, will not work for those of us who want to have it the other way around, that is, the apex pointing to the www form of the domain. I was told that GitHub might consider other solutions in the future.
- fladd 9y agoSo, I received an answer from GitHub support, that they tested it, and that all forms of my domain are working now. And indeed, when I tested it again myself, also the apex version of my domain will bring me to the page, without any warnings. However, https://mydomain.com https://mydomain.com and https://www.mydomain.com https://www.mydomain.com have different SSL certificates. Is this supposed to happen? I assumed that the apex is just a forward to the www subdomain.