I’ve recently switched my website’s SSL setting from “Full” to “Full Strict”. However, I noticed that the CNAME Flattening no longer works and instead I get thrown the “Invalid SSL Certificate” error.
That is most likely not a CNAME issue but by switching to strict (which generally was a good idea) Cloudflare now requires a valid certificate from your server, which you apparently haven’t got configured though.
In that case your certificate might be issued only for www and not the naked domain. If you feel comfortable enough revealing the origin IP, please do so. I presume your origin IP address does not end in 21 any longer, right?
It appears there is no certificate at all configured at Github. Are you sure you configured www and the naked domain identically? Can you post a screenshot?
Also, ensure you did configure the domain and the certificate correctly at Github.
It appears that Github does not have any certificate configured for your domain. Can you double check that? The fact that www does load is a bit strange though, could it be you have a page rule in place?
well I checked crt.sh and for the goid.com.sg I only found Cloudflare certs so it looks like github cant get a cert for the domain (fairly obvious because the IP goes to Cloudflare and with strict ssl Cloudflare will block any attempt for classic HTTP validation).
with this my theory that CF checks for the name in the CNAME record seems as good as proved.