Full text downloads not working with Uni's proxy
I am running Zotero 6 on WIndows and use the connector on Firefox. I recently changed employers and noticed that the Zotero connector never works for Full text PDF downloads with my new Uni's proxy even if I have access to the PDF. It always switches to Open-access PDFs even if it shows Full text PDF (e.g. Science Direct) for a few seconds initially.
I looked into the logs but couldn't find any errors. How can I troubleshoot this? Thanks
I looked into the logs but couldn't find any errors. How can I troubleshoot this? Thanks
Can you provide a Debug ID from Zotero for SD and non-SD attempts that fail?
SD no proxy (works fine): D1491378590
SD with proxy: D1583690896
SD with proxy: D1511596106
AEAWEB with proxy: D2082172059
On all 3 tests with the proxy it shows Full Text for a second or two and then automatically switches to Open Access. I don't think this has to do with the anti bot protections but somehow Zotero doesn't work through my Uni's proxy.
https://www.sciencedirect.com/science/article/pii/S0014292117301551
- SD with proxy 1 FAIL: D14162002
https://www.sciencedirect.com/science/article/pii/S0304393222001088
- SD with proxy 1 FAIL: D180549137
- SD with proxy 2 WORKING: D189098143
https://www.aeaweb.org/articles?id=10.1257/aer.96.4.1193
- AEAWEB with proxy 1 fail: D425068210
- AEAWEB with proxy 2 WORKING: D977792289
https://www.sciencedirect.com/science/article/pii/S0923753421022146
- SD without proxy WORKING: D2094098067, D1492563480
https://www.zotero.org/support/kb/incomplete_cert_chain
They can see that the server shows "Chain issues: Incomplete" on the SSL Labs test.
[JavaScript Error: "The connection was refused when attempting to contact wss://stream.zotero.org/." {file: "chrome://zotero/content/xpcom/streamer.js" line: 155}]
I'm trying to upload a full-text version on the New England Journal of Medicine. The same problem occurs on the science direct website
(Once this is fixed, ScienceDirect might still fail due to https://forums.zotero.org/discussion/comment/450008/#Comment_450008.)