Hello! This sounds like it's probably a problem with the site's configuration. If you're able to reproduce this, could you please attach a net-internals log as described in https://dev.chromium.org/for-testers/providing-network-details?

Removing security labels since the site is failing closed.

FWIW I've just checked the site, the certificate used seems to have two embedded  SCTs and is valid for less than 2 years, so should be CT-compliant.

added network log as requested - from incognito window with no other activity.

Note, this is 100% reproduceable for me.  Its not clear from the last two comments whether it's loading correctly for either commenter.

Deleted: net-internals-log.json 182 KB

net-internals-log.json 182 KB View Download

The reporter is running an out of date Chrome version - 53.0.2785.80, when current stable is 54.0.2840.90

If you update your Chromium, does that resolve the issue?

re: Comment 2: It's likely failing because it's outside the 10 week build period to have the logs recognized, and since no logs are recognized, it's not CT compliant.

interesting. not sure why my chrome isn't auto-updating. This makes sense. Go ahead and close the ticket. I'll report again if it occurs after updating.

Ryan, do you think we should indicate a different error if the build is not timely? The CT error is a bit of a red herring in this case.

fyi, updated to current chrome beta build (55.0.2883.35) and all is well.  

rsleevi was correct.  My bad for not realising that the beta version isn't auto-updated automatically on ubuntu (and perhaps other os), and not looking for that before reporting the issue.