Skip to content
This repository has been archived by the owner on May 11, 2022. It is now read-only.

Your SSL certificate is broken #105

Open
joshua-m-david opened this issue Aug 13, 2014 · 2 comments
Open

Your SSL certificate is broken #105

joshua-m-david opened this issue Aug 13, 2014 · 2 comments

Comments

@joshua-m-david
Copy link

Whenever I visit the site I get a big warning come up:

This Connection is Untrusted

You have asked to connect securely to scramble.io, but we can't confirm that your connection is secure.

Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified.
What Should I Do?

If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue.

@joshua-m-david
Copy link
Author

It only seems to happen in the Tor browser.

scramble.io uses an invalid security certificate. The certificate is not trusted because no issuer chain was provided. (Error code: sec_error_unknown_issuer)

When you received the files from the CA, they give you a whole heap of certs. I had to do this a few weeks ago. From memory, you make up a trust chain of the public certificates e.g. CA root -> intermediary cert -> your public cert just by copying the public keys all into one text file and rename the file to .pem I think it is, then set it to use that file in your webserver. There'll be a guide around somewhere.

@AndrewTheLott
Copy link

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants