4 ms·

HTTPS does work for my site now, but I get this warning: Your connection is not secure / Your connection is not private Error code: SSL_ERROR_BAD_CERT_DOMAIN

HTTPS does work for my site now, but I get this warning: Your connection is not secure / Your connection is not private Error code: SSL_ERROR_BAD_CERT_DOMAIN (Firefox) NET::ERR_CERT_COMMON_NAME_INVALID (Chrome) Trying adding the A records as described here: https://help.github.com/articles/setting-up-an-apex-domain/ https://help.github.com/articles/setting-up-an-apex-domain/ Will update if that works..

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 ago
  It is the same for my domain. Seems to be a bug.
- epberry 9y ago
  Same here. Redirect from http -> https works fine tho.
- Philipp__ 9y ago
  Same here.
- fladd 9y ago
  I contacted GitHub support about this already. I hope this gets resolved soon.
  - fladd 8y ago
    It 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 ago
    So, 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.
bad_user 9y ago
This is because they have to check your A records and generate the certificate and from my observations that happens when you add the custom domain. After I've set the A records, I removed the custom domain from GitHub's Settings and then re-added it. It started working afterwards.
- Philipp__ 9y ago
  I did that, and still not working. After setting A records, re-entering custom domain and waiting for few minutes, I get this message in Settings of GH-pages `Domain's DNS record could not be retrieved`. Bummer. Maybe I was to eager to remove Cloudflare from the equation.

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 ago
It is the same for my domain. Seems to be a bug.
epberry 9y ago
Same here. Redirect from http -> https works fine tho.
Philipp__ 9y ago
Same here.
fladd 9y ago
I contacted GitHub support about this already. I hope this gets resolved soon.
- fladd 8y ago
  It 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 ago
  So, 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.

bad_user 9y ago

This is because they have to check your A records and generate the certificate and from my observations that happens when you add the custom domain. After I've set the A records, I removed the custom domain from GitHub's Settings and then re-added it. It started working afterwards.

Philipp__ 9y ago
I did that, and still not working. After setting A records, re-entering custom domain and waiting for few minutes, I get this message in Settings of GH-pages `Domain's DNS record could not be retrieved`. Bummer. Maybe I was to eager to remove Cloudflare from the equation.