bootstrapcdn: bootstrapCDN certificates are not valid

All https downloads are disabled due to

The server presented a certificate that was not publicly disclosed using the Certificate Transparency policy. This is a requirement for some certificates, to ensure that they are trustworthy and protect against attackers.

in Chromium Version 53.0.2785.143

Your connection is not private

Attackers might be trying to steal your information from maxcdn.bootstrapcdn.com (for example, passwords, messages, or credit cards). NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
Subject: *.bootstrapcdn.com
Issuer: RapidSSL SHA256 CA
Expires on: Oct 13, 2017
Current date: Nov 14, 2016

from https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 44 (17 by maintainers)

Most upvoted comments

It makes me feel a little better that they are having issues as well. I am just appalled of how many careless mistakes have been made by Browser and SSL vendors this year.

I personally did not see the problem resolve itself by restarting, however it does appear to be a bug in Chromium (and, by extension, Chrome) and not bootstrap-cdn. I’ve also found a bunch more ssl sites with the same “issue”.

TL;DR: use Firefox.

FYI, I just got home and there’s no sertificate issues here (StackPath AMS1 datacenter).

@b264 && @EdgeCaseBerg – Mind checking your datacenters as well… http://debug-17.netdna-cdn.com/

@kek91 sounds good thanks so much

@jdorfman Sorry, my post has been updated.

Browser: Chromium, v 53.0.2785 OS: Linux elementary 0.4 (Loki) 64-bit

@b264 @EdgeCaseBerg we believe it might have something to do with this: https://sslmate.com/blog/post/ct_redaction_in_chrome_53 (we use GeoTrust)

cc: @jmervine

I’m seeing this issue as well.

Google Chrome   53.0.2785.101 (Official Build) (64-bit)
Revision    d68319683072a27031ebac6ac151e59f4190cab7-refs/branch-heads/2785@{#838}
OS  Mac OS X 

screen shot 2016-11-15 at 10 26 46 am

I don’t believe this is a bootstrap-cdn issue any more, but I’m not 100% certain