# That certificate didn't load correctly, so it can't be validated

**URL:** <https://community.blockcerts.org/t/that-certificate-didnt-load-correctly-so-it-cant-be-validated/1267>\
**Category:** Technical\
**Created:** [August 14, 2018, 12:45pm UTC](https://community.blockcerts.org/t/that-certificate-didnt-load-correctly-so-it-cant-be-validated/1267 "2018-08-14T12:45:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ruth](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@ruth](https://community.blockcerts.org/u/ruth)\
**Post date:** [August 14, 2018, 12:45pm UTC](https://community.blockcerts.org/t/that-certificate-didnt-load-correctly-so-it-cant-be-validated/1267/1 "2018-08-14T12:45:54Z")

</div>

Hi

I am using the blockcerts standard to issue certificates on the bitcoin testnet. I followed the instructions from the cert-issuer page and successfully issued some certificates to this testnet.

I am however, getting the following error “_ **That certificate didn’t load correctly, so it can’t be validated** _” when I try to view these certificates from a browser, using the cert-web-components. The sample certificate “sample\_cert-valid-2.0.json” from the demo folder under cert-web-components was validated without issues.

Could you please give me some suggestions on why I might be getting this specific error? Any help is appreciated.

---

<div class="post-metadata">

**Author:** ![lparker](https://avatars.discourse-cdn.com/v4/letter/l/3bc359/32.png) [@lparker](https://community.blockcerts.org/u/lparker)\
**Post date:** [August 15, 2018, 3:34pm UTC](https://community.blockcerts.org/t/that-certificate-didnt-load-correctly-so-it-cant-be-validated/1267/2 "2018-08-15T15:34:13Z")

</div>

Hi Ruth,

I’d be curious to know what happens when you submit the certificate to the verifier on [https://blockcerts.org](https://blockcerts.org). Is there any difference in behavior?

---

<div class="post-metadata">

**Author:** ![ruth](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@ruth](https://community.blockcerts.org/u/ruth)\
**Post date:** [October 7, 2018, 2:49pm UTC](https://community.blockcerts.org/t/that-certificate-didnt-load-correctly-so-it-cant-be-validated/1267/3 "2018-10-07T14:49:46Z")

</div>

Hi, apologies for the late reply, I recently just got around to trying the fix but your suggestion was actually very useful. At the time I posted the question, my certificates turned out to be a mess because of my issuer profile not being set up properly. I have since fixed that and I can now issue certificates that are valid when I run them through blockcerts’ verifier. _I am however still getting the same error from the cert-web-component_. I have installed the cert-viewer flask application and validated the same certificates successfully from there as well.

So the same blockchain certificates that are valid from blockcerts’ verifier and the cert-viewer app still give the error “ **That certificate didn’t load correctly, so it cant be validated** ” with the cert-web-component. The sample certificate still displays without problems though. I’ve tried to identify the differences between the sample certificate json and one of mine, it seems the sample certificate is a blockcerts version 1 certificate. I do not know if I am correct but since I use the version 2 python module “create\_v2\_certificate\_template.py” to create the certificate templates, could it be possible that the cert-web-component expects some kind of structure/format that has since changed from the initial version 1 module?

Thank you again for the help, at the very least I can be sure the blockchain certificates are now valid.

---

<div class="post-metadata">

**Author:** ![lparker](https://avatars.discourse-cdn.com/v4/letter/l/3bc359/32.png) [@lparker](https://community.blockcerts.org/u/lparker)\
**Post date:** [October 8, 2018, 3:01pm UTC](https://community.blockcerts.org/t/that-certificate-didnt-load-correctly-so-it-cant-be-validated/1267/4 "2018-10-08T15:01:26Z")

</div>

Hmm… I wonder what’s going on there. The cert-web-component definitely should work with v2 Blockcerts, but if there’s a bug, I’d like to know more about it. You don’t happen to see a stack trace anywhere, by chance?
