Upgrade Storagecharlie80
About
- Username
- charlie80
- Joined
- Roles
- Member
Comments
-
OK WAIT! I nailed it: the culprit is the Better Bib(La)TeX exporter! Disabling the "export by HTTP" option of this plugin kills all the communication on 127.0.0.1:23119, including obviously the Zotero Connector. Re-enabling the "export by HTTP"…
-
Ok, thanks aurimas. I suppose I should search the output of netstat a line like this TCP 127.0.0.1:23119 ... but, no, there is no such line (and there is no other line referring port 23119). What next...?
-
Thank you for replying adamsmith. Following your suggestion, I also turned on full logging on the Windows Firewall for all domains, but there are no blocked connections when I try to access that URL. I have no other things like ZoneAlarm or similar.…
-
sorry, any other idea to chase this problem?
-
Thanks Dan. No, that URL does not open in Chrome ("Oops! Google Chrome could not connect to 127.0.0.1:23119"). With IE the behavior is the same. All proxies are disabled. I'm quite lost...
-
Thanks for the feedback. I tried to completely disable Avast, but the problem is still there (weird). I also white-listed both localhost and 127.0.0.1 in avast. I don't know if it's relevant, but a ping both addresses (locahost and 127.0.0.1) gives …
-
Ok, some more info. If I enable debug output logging in the Zotero Connector, and if I try to update the status of Zoero Standalone, I get the following: (3)(+0001480): HTTP POST {} to http://127.0.0.1:23119/connector/ping (3)(+0001006): C…
-
I think this discussion can be closed...problem is fixed in 0.0.52 and is being discussed along with other issues on the github issue tracker.
-
Looks like I can't attach an XML file to the github issue tracker... should I copy-paste it in the text of the report on github?
-
Sure, give me some minutes. Thanks for your help.