SSL certificate error connecting to sync.zotero.org
I have read the old two topics,but it didn't work,please help me ,thank you.
http://www.zotero.org/support/kb/ssl_certificate_error
http://forums.zotero.org/discussion/7972/sync-ssl-certificate-error-connecting-to-synczoteroorg/
My debug errors:
sync.zotero.org:443 uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)
solution:
ESET setup -> advanced setup -> extend web and email tree -> SSL
SSL protocol: Do not scan SSL protocol
http://www.zotero.org/support/kb/ssl_certificate_error
http://forums.zotero.org/discussion/7972/sync-ssl-certificate-error-connecting-to-synczoteroorg/
My debug errors:
sync.zotero.org:443 uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)
solution:
ESET setup -> advanced setup -> extend web and email tree -> SSL
SSL protocol: Do not scan SSL protocol
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Upgrade Storage
http://forums.zotero.org/discussion/28752/zotero-standalone-will-not-sync/
If you don't have the program mentioned there (and can't figure out anything else that could be causing this), see the part about emailing a the certificate chain.
ESET setup -> advanced setup -> extend web and email tree -> SSL
SSL protocol: Do not scan SSL protocol
Zotero refuses to sync and says (I translate finnish to english so in english the message might be a bit different):
"[JavaScript Error: "Error: SSL-certificate error while connecting to sync.zotero.org
Watch http://zotero.org/support/kb/ssl_certificate_error, if you want to know more." {file: "chrome://zotero/content/xpcom/sync.js" line: 638}]"
I followed the manual zotero provided for this, but nothing there helped. (https://sync.zotero.org/ says nothing to see her) I have tried shutting down Norton Internet security and also reinstalling both firefox as well as Zotero standalone. Nothing has worked. Also, I tried to see if my computer has "E-Rewards Notify" malware, but I cannot find anything like that. I am pretty clueless as to how to proceed.
malware that causes these problems. Error seems similar as reported in the other discussion, but I cannot find "E-rewards notify" in my system. Perhaps there is something else. Is there a way to identify what program is causing the problems? If I followed your earlier advice: (https://sync.zotero.org-->click lock-->> finger print is OK-->> details)
I have (among other entries):
"CN = *.zotero.org
OU = Domain Control Validated - RapidSSL(R)
OU = See www.rapidssl.com/resources/cps (c)12
"
while the other discussions had something like "DIGITALMARKETRESEARCHAPPS PTY LTD". So my entry seems more legit.
"
...
(3)(+0000001): Session ID not available -- logging in
(3)(+0000000): HTTP POST version=9&username=jpjmarti&password=******** to https://sync.zotero.org/login
(1)(+0000004): SSL-sertifikaattivirhe yhdistettäessä kohteeseen sync.zotero.org
Katso http://zotero.org/support/kb/ssl_certificate_error, jos haluat tietää lisää.
(1)(+0000001): 'message' => "SSL-sertifikaattivirhe yhdistettäessä kohteeseen sync.zotero.org
Katso http://zotero.org/support/kb/ssl_certificate_error, jos haluat tietää lisää."
'errorMode' => "error"
'fileName' => "chrome://zotero/content/xpcom/sync.js"
'lineNumber' => 638
'columnNumber' => 0
@chrome://zotero/content/xpcom/sync.js:638
.onError@chrome://zotero/content/xpcom/sync.js:608
_error@chrome://zotero/content/xpcom/sync.js:2446
_checkResponse@chrome://zotero/content/xpcom/sync.js:1916
Zotero.Sync.Server</login/<@chrome://zotero/content/xpcom/sync.js:1372
_stateChange@chrome://zotero/content/xpcom/http.js:800
xmlhttp.onreadystatechange@chrome://zotero/content/xpcom/http.js:334
"
Some of the messages are in Finnish, but that is beside the point.
(For the problem discussed there I think submitting debug output should have worked regardless, though, so it's possible this is a different issue.)