You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 11, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: