JSTOR PDFs not downloading with Zotero Chrome connector

abigailburman
Hi everyone, I'm my absolute wits end. Zotero, the connector, and my browser are all up to date. I've accepted the terms and conditions once before downloading. However, it still won't save any pdfs. I get the Xs. I'm trying to download from URLs that look like http://www.jstor.org/stable/20722457. It's UC Berkeley access if that helps.
  • abigailburman
    It also won't download the snapshot.
  • adamsmith
    And the above URL is the URL exactly as you see it in your browser's address bar right?
  • abigailburman
    Exactly the URL. The access is provided by the university, but it's not through a proxy. I even set up proxy settings just to be safe, no dice.
  • fbennett
    This might not be the cause, but I wonder if it might be failing for a protocol mismatch. Do you possibly get a different result with https://www.jstor.org/stable/20722457 ?
  • adomasven
    Could you produce a Debug ID from Zotero?

    1. In the Help menu, go to Debug Output Logging and select Enable.
    2. In your browser click on the Save to Zotero button and wait for the saves to fail.
    3. Before doing anything else, in Zotero return to Help → Debug Output Logging and click Submit Output, which will disable logging and submit the output to zotero.org. A window should pop up containing a Debug ID. Click “Copy to Clipboard” and paste the Debug ID into this forum thread.
  • dpcrawford75
    I have been having the same problem. Downloading pdfs from jstor used to be a no brainer, now they will not download for me.

    I accomplished the debug steps as noted above. Here's my ID: D1168836336
  • dstillman
    @dpcrawford75:
    https://0-www.jstor.org.library.[…].edu/stable/pdfplus/10.[…].pdf?acceptTC=true

    0-www.jstor.org.library.[…].edu:443 uses an invalid security certificate.
    That's a problem with the proxied URL — it won't serve a valid security certificate that way. What are the full URLs when you're on the JSTOR page and when you load a PDF? (You can X out any identifying info as I do above.)
  • dpcrawford75
    You're right, the certs were bad. I was accessing jstor from a bookmark, but the certificate from that url expired a week or two ago. I accessed jstor from the univ's library link instead, and it worked fine. Thanks for the help!
Sign In or Register to comment.