As discussed here, was prompted to post it as a brand new question, so here it is :-).
Earlier today there was an issue with Stack Snippets, caused by the move to Denver. That issue was fixed, but however created/revealed a brand new issue; the Stack Snippets' domain has the incorrect SSL certificate installed, as confirmed by rene here:
when loading the Snippet as a full-page frame:
After clicking 'Advanced' and clicking 'Proceed', I can go back to the Snippet and see it perfectly. On Chrome 44.0.2403.130 (Official Build) m (32-bit), Windows 10 Pro x64.
This issue is confirmed by running an SSL test, where
stacksnippets.net achieves a fairly absymal 'M' (aka, FAIL):
Should be easily fixed by generating and installing the correct SSL certificate. Mind, I don't force SSL and apparently some users have no issues with the current SSL certificate.
I acknowledge that SSL isn't officially supported, but if so, why is an HTTPS connection being attempted instead of a normal standard HTTP connection? I see no reason to use HTTPS on Stack Snippets; content on the domain contains no private info and stores no sensitive data.
And no, I don't force-HTTPS on Stack Exchange or any other Stack Exchange site: