Topic: btc-e.com uses an invalid security certificate (Read 2621 times)
Looks good to me. http://dl.dropbox.com/u/9542654/btc/Capapap.png
Maybe your browser is too old, also make sure you are loading the real website, not a clone (some trojans modify your nameserver records and point you to different websites)
I have used myself with Firefox 10, and Firefox 11, and all works fine.
Also, I have used with chrome, and chromium and everything is fine as well.
I have used myself with Firefox 10, and Firefox 11, and all works fine.
Also, I have used with chrome, and chromium and everything is fine as well.
Works fine using both convergence.io SSL checks and regular comodo issued cert in Iceweal 11.0 for debian which is basically firefox
I am using Firefox 8 and everything works fine.
Hmm, no, I didn't delete anything, but this might be related:
http://jimmyzimmerman.com/blog/2011/03/positivessl-untrusted-connection-in-firefox.html
http://jimmyzimmerman.com/blog/2011/03/positivessl-untrusted-connection-in-firefox.html
Have you deleted any of the root certs from your browser?
I get no such error using Chrome. Cert looks good.
Same here. Issued by PositiveSSL CA 
I get no such error using Chrome. Cert looks good.
Issuer:
Subject:
Alternate Name:
Either it is a bug in Firefox 10 or you got some url redirection going on.
Issuer:
Code:
CN = PositiveSSL CA
O = Comodo CA Limited
L = Salford
S = Greater Manchester
C = GB
Subject:
Code:
CN = btc-e.com
OU = PositiveSSL
OU = Domain Control Validated
Alternate Name:
Code:
DNS Name=btc-e.com
DNS Name=www.btc-e.com
Either it is a bug in Firefox 10 or you got some url redirection going on.
I am trying to access BTC-E with Firefox 10, and regardless of whether I go to https://btc-e.com or https://www.btc-e.com I get something like:
btc-e.com uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)
What are your experiences?
btc-e.com uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)
What are your experiences?
Jump to: