This was a certificate fail on the CloudFlare side on the Imgur account hosted on our behalf. We're still awaiting info on what exactly happened, but since it's not directly our account we may not get this information.
The fix should be rolling out shortly around the world - we prodded both sides to have new certs issues ASAP and we are now seeing valid certificates in most locations (our New York sysamins aren't seeing it yet).
New cert details
- Valid From: Tuesday, October 27, 2015 at 8:00:00 PM EDT
- Valid To: Thursday, October 27, 2016 at 7:59:59 PM EDT
- SHA1:
96 BD DF 71 49 F8 C6 D9 A8 6E 2D E1 D3 5D 2F 00 6A 90 0C ED
- MD5:
90 13 A3 FD B5 61 F4 B5 E9 8D DC 8B D7 9D BE C5
- SAN entries:
i.stack.imgur.com
imgur.cloudflaressl.com
i.stack.imgur.com
(issued only tossl330558.cloudflaressl.com
, no alternate names) and both image URLs and thattrace
thing result in 403.fl=48f8 h=i.stack.imgur.com ts=1446070144.771 visit_scheme=http uag=Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 colo=DUS spdy=off loc=DE
fl=21f130 h=i.stack.imgur.com ts=1446070560.828 visit_scheme=https uag=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36 colo=LHR spdy=3.1 loc=GB
And can see the image he linked...fl=63f12 h=i.stack.imgur.com ts=1446071939.274 visit_scheme=http uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2547.0 Safari/537.36 colo=MAN spdy=off loc=GB
i.stack.imgur.com
and has incorrect certificates in some colos. It's not directly our account, but hosted in behalf of imgur for us so resolving takes a bit more time. We'll get them to correct the cert issue ASAP.