Bad certificate for

Both Chrome and Firefox are complaining that is not who they say they are. Either there is a bad cert somewhere out there, or I have screwed up in some weird way, or paranoid me is subject to a MITM attack. My nameserver and Google’s each resolve to

1 Like

I get the same IP for, so you’re clear there.

Chrome doesn’t seem to complain about the cert, but Firefox gets upset: uses an invalid security certificate.

The certificate is not trusted because it was issued by an invalid CA certificate.

(Error code: sec_error_inadequate_key_usage)```

I’m getting the same error on My ruby app that connects to it is failing now as well:

OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

Using shows an “Unkown error”, and Firefox claims:

The certificate is not trusted because it was issued by an invalid CA certificate.
(Error code: sec_error_inadequate_key_usage)

Chrome ignores CRLs (certificate revokation lists) and other mechanisms to revoke certs, so I wonder if that’s what happened.

@zachary pushed a new SSL certificate few hours ago. Thanks for sharing so they can fix it! :slight_smile:

ok thanks, i see where is the probleme, i still receveid cert issued on 13/01/14
and probably this one is revoked. So probably some cache somewhere that is not yet updated
with new cert.

The forum works on my Win 7 Chrome, my KitKat 4.4 Chrome but NOT on my IOS 7 Chrome (!!!). Anyone else with is problem?

Firefox (Win 7 & Precise) says that the AD:6D:28:18:E7:E1:D3:4F:6A:68:79:F2:8D:EA:B6:CE:72:AD:3D:2B certificate is not trusted, but Chrome (same Win 7) is okay with the same one.

The acknowledgement of the error on the status page …

Update - We’ve submitted a support ticket to Comodo and are awaiting their response.
Apr 19, 15:03 CDT
Identified - We’ve identified an issue with some versions of Firefox that don’t appear to trust COMODO’s ECC root certificate authority, trying to identify a fix for this issue.
Apr 19, 11:05 CDT

… does not fully describe the extent of the problem. For me, on Ubuntu 12.04 (up to date, and rebooted 5 mins ago to check all this again, and I’ve also completely cleared Chrome’s cache) both Firefox and Chrome complain about the site. On Firefox I have to create an exception to the certificate checking. On Chrome I cannot get access at all. Naming @zachary purposefully. I’ve also sent e-mail to the general spark address.

Thanks all. Still working on it with Comodo. No idea what’s causing the problems. Also, FYI, none of the old certificates have been revoked yet. is still using the old certificate. API & community are using the new one. As I find out more, I’ll post to status page.


Hey guys, not sure if it is related, but on Linux (Ubuntu 12.04) using either chromium or firefox, I still get the cert error and any use of the IDE to compile or flash gets a 404. Even trying to flash from another box that doesn’t get the SSL warning results in the UI saying the device is flashed, but my spark core doesn’t even blink. Is this all related? Is the core erroring out the cert?

NSA ? :slight_smile: Got to Love those Guys.

Status has been updated:

Update - Comodo says “there may be a problem with Firefox and our EC certificates”. They are investigating the issue.
Apr 21, 09:04 CDT

In Firefox, I get a

(Error code: sec_error_inadequate_key_usage

Both the status page here and Comodo seem not to reflect the full picture. As already reported (and not only by me, and there is another forum topic on this certificate issue) Chome (on Ubuntu 12.04) will not allow access to - Chrome says the certificate is improperly formatted. Considering that the status page has been updated but the status only acknowledges a Firefox problem can someone [@zachary ?] please ensure Comodo are told about this too? Thanks

I see the same issue using curl


  • Initializing NSS with certpath: sql:/etc/pki/nssdb
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • Bad certificate received. Subject = ‘CN=*,OU=PremiumSSL Wildcard,O=Spark Devices,STREET=1010 W Lake St Suite 100-105,L=Minneapolis,ST=Minnesota,postalCode=55408,C=US’, Issuer = ‘CN=COMODO ECC Organization Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB’
  • NSS error -8102
  • Closing connection #0
  • Peer certificate cannot be authenticated with known CA certificates

It sounds like the latest Firefox nightly v31a1 fixes the problem. It’s set to release next week, and Comodo is pushing Mozilla to release faster.

@psb777 Thank you—please post the exact version number of Chrome that fails on Ubuntu 12.04. I’d love it if someone else could reproduce.

@jShaf Is there an update available for your CA certificate bundle? If not, what operating system are you on?

Comodo’s going to get us a re-issued certificate that’s more broadly accepted.

1 Like

google-chrome-stable/stable uptodate 34.0.1847.116-1
firefox/precise-security uptodate 28.0+build2-0ubuntu0.12.04.1
both the above fail on an up to date Ubuntu 12.04 as I described: Firefox requires the setting up of a certificate exception, and Chrome does not allow access at all.
I believe @lemouchon has long since reported the same problem also in Ubuntu in the topic

It seems to me that Comodo wrongly blames Firefox for their error.

All fixed everyone. Comodo issued us a fully functional certificate, and it’s been installed on the community and the API. Thanks for your patience and your help debugging!


i confirm works now. Many thanks for your work and great support.

1 Like