Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Could anyone explain the meaning of this error message in plain English?

Should I add an exception or I should not continue on this website?

Technical details: the URL is here, the browser is Firefox 14.0.1 on Ubuntu 12.04 LTS.

Konqueror 4.8.2 says for the same link:
The certificate authority's certificate is invalid
The root certificate authority's certificate is not trusted for this purpose

UPDATE: I did not do anything with my browser and now it magically works, no error message. A mystery.

share|improve this question
If someone is looking at this from a sysadmin perspective:… contains useful info. – Kasper Souren Mar 28 '14 at 14:09
up vote 13 down vote accepted

It looks like you are missing an intermediate CA (Certificate Authority).

Certificates are only trusted because they are signed by a trusted certificate authority (the issuer), which is in turn signed by another trusted CA, up to those listed as explicitly trusted by whatever is verifying them (a root CA). Browsers (and OSes) come with a list of root CAs. See here for more details. Wikipedia also has a very nice explanation of just about every aspect.

The website certificate appears to specify AlphaSSL as its issuer, which in turn specifies GlobalSign Root CA. So that's the chain - the website's certificate does not mention GlobalSign Root CA anywhere so if either of the two in the chain is missing, Firefox will complain.

Screenshot of certificate

Could you verify GlobalSign/AlphaSSL exists in your Firefox certificate authorities list?

  1. Open the Certificate Manager (Tools => Options => Advanced => Encryption => View Certificates)

  2. Check on the Authorities tab for the AlphaSSL CA - G2. It should be under GlobalSign nv-sa.

    Also check for GlobalSign Root CA.

    Screenshot of certificate manager

  3. Select GlobalSign Root CA, click Edit Trust, and verify that it is allowed to identify websites. At least for me, AlphaSSL did not have that permission.

If the root CAs is missing, try resetting your certificate store. Basically, delete (or rename) cert8.db, secmode.db and cert_override.txt from your profile folder.

If the intermediate certificate is missing, well, it's the responsibility of the server operator to serve the intermediate certificate along with the root. You should contact them and let them know. If you want, you can grab the intermediate certificate elsewhere - these sites sometimes works for some people because they have a cached intermediate that's already trusted.

You might also want to try clearing your cache in Firefox.

This might also be an issue with the CA being missing from your system stores, which would explain why Konqueror is also affected. I know that, at least on Windows, Firefox ignores the system's certificate store. I'm not familiar with how Ubuntu (or Firefox on Ubuntu) manages certificates, but the issue is the same: you appear to be missing a CA. You'll need to add it.

Alternatively, you could add the site's certificate to the exceptions list. Since you are missing a CA, there's a chance other sites will display a similar error - the only reason not to add the CA is if you don't trust them. This site's certificate seems to be valid, at least according to my system (though CAs can revoke certificates). Of course, unless you can somehow verify a certificate as valid, do not add an exception.

share|improve this answer
Thanks, it seems to me we are close to a solution. "Check on the Authorities tab for the AlphaSSL CA - G2. It should be under GlobalSign nv-sa" It is not there. What should I do? – Ali Jul 22 '12 at 10:33
@Ali First, try resetting the certificate store. If that does not work, check to see if the GlobalSign Root CA is there. You can try installing the CA from the AlphaSSL site (specifically, this link, crt DER format). They say this should be installed on the webserver, and does not need to be manually installed on the client machine, so it's possible whoever runs that server forgot something. – Bob Jul 22 '12 at 12:11
Keep in mind that you must be sure you can trust a certificate/CA before adding it to your trusted list. Especially in the case of a CA, since you implicitly trust any certificate they issue. – Bob Jul 22 '12 at 12:13
Sorry I could not back to you in a timely manner, I have been moving, hence the new Internet connection order at UPC :) – Ali Aug 6 '12 at 19:08
@x-yuri Click the lock symbol in the address bar => More Information => View Certificate. If you were on the connection untrusted page, then click I Understand The Risks => Add Exception and click View in the popup. – Bob Apr 18 '14 at 14:11

Some secure web-sites with certificates from trusted authorities have incorrect configuration such that they don't include a chain of intermediate certificates of trust when serving their own certificate.

If you have a system/browser that has seen its share of valid certificates, such intermediaries may already be cached, and you won't be getting any error messages, even if their web-server configuration is still wrong as above.

However, if you're using a freshly installed browser on a fresh system, and such intermediaries weren't cached yet, and the certificate presented by the web-server is missing an appropriate chain of intermediaries, then you get an error message.

Here's an official explanation by a Mozilla developer in a mailing list:

Bottom line: it is the fault of the web-site, even if it only happens in your freshly installed browser, and works fine elsewhere.

How they've fixed it in plain English:

They bought their certificate from a reseller of trust, and their web-server must have only been serving one certificate — their own — which your browser doesn't trust directly, since they bought it from a reseller you've never heard of.

Now, instead of serving just one certificate, they serve two right at the same time — their own ("*") and that of some certificate reseller ("AlphaSSL CA - G2"), and the certificate of such reseller completes the trust, since you now see that someone whom you trust ("GlobalSign Root CA") has vouched for such reseller of trust.

You can see more details about exact names involved here:

Some other web-sites buy their certificates directly from a trusted authority, and not from a reseller, so, they only need to serve their own certificate, and everything will still be tip-top.

For example, bought their certificate directly from Equifax, which Mozilla trusts directly, so there's no need for Linode to include any copies of any certificates other than their own.

share|improve this answer

Could anyone explain the meaning of this error message in plain English? wants you to type in personal details

To reassure you that is a website being run by UPC, has presented you with a certificate saying "you can trust, I vouch for them" signed Joe Smith.

You have no idea who Joe Smith is. You have a list of signatures of people that Microsoft The Mozilla project say you can probably trust to introduce you to other people who are probably who they say they are, Joe smith isn't in that list of signatures (Certifying Authorities).

The certificate is therefore worthless

You can test this by cutting your full URL and pasting it in to the certificate tester at - though that is aimed at people who set up certificates in sites like, not at people who access those sites.

Also, is a good read.

share|improve this answer
Microsoft isn't involved here ;) – Bob Jul 22 '12 at 10:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .