DOI look-up is not working

dstillman
This discussion was created from comments split from: ISBN lookup not working for book in WorldCat.
  • pszejner
    edited July 28, 2023
    Some colleagues and I I've been having trouble with the DOI look-up for several weeks now... and we keep getting this message "Zotero could not find a record for the specified identifier. Please verify the identifier and try again"
  • dstillman
    (Please start new threads for new issues — the thread you posted to isn't related. I've moved this to a new thread.)
    I am a bit annoyed that the DOI look-up is not working for weeks now
    See Etiquette. There's no problem with DOI lookup in general. If you're having trouble with something, just report it without assuming that it's happening to anyone but you.

    Can you provide a Debug ID for an attempt that fails?
  • pszejner
    Hi, here is the debug ID I have D1212636634 thanks for the help
  • dstillman
    (3)(+0000657): Translate: Could not find a result using DOI Content Negotiation -- trying next translator

    (3)(+0000000): HTTP GET https://doi.org/10.[…] failed with status code 403
    You're being blocked with a 403 Forbidden error by either doi.org or your proxy server.

    Did you do many DOI lookups at once before this started?

    Is your proxy server shared with others, such that all lookups from a single organization would come from the same IP?

    We received one similar report the other day, I believe for the first time, so it's possible that doi.org changed to more aggressive blocking, but it might also be related to your proxy server.
  • pszejner
    Thank you, I have not made many DOI lookups at once before this started. I will contact the IT from this Institution, they might help.
  • dstillman
    Are you able to load a doi.org URL in your browser?
  • adamsmith
    (Reminder that the requests to DOI.org are sent with an accept header, which shouldn't, but could conceivably trigger a 403 from the proxy server. Both CrossRef and DOI.org are set up to be very generous with what they allow for query frequency, so while not impossible, I'd be surprised if they sent a 403)
  • dstillman
    There was also a 403 for the doi.org request in the Airiti translator, which uses a normal GET request.
  • pszejner
    @dstillman, Yes I am able to load the doi.org URL
  • dstillman
    If you go to Tools → Developer → Run JavaScript in Zotero and run these, what do you get?

    return (await Zotero.HTTP.request('GET', 'https://doi.org/10.1038%2Fngeo722', { headers: { Accept: "application/vnd.datacite.datacite+json, application/vnd.crossref.unixref+xml, application/vnd.citationstyles.csl+json" }})).status

    return (await Zotero.HTTP.request('GET', 'https://doi.org/10.1038%2Fngeo722')).status
  • pszejner
    inboth cases I get this error

    Error: HTTP GET https://doi.org/10.1038/ngeo722 failed with status code 403:


    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">



    ....
    ....
    ....
    ....
  • dstillman
    OK, can you run this and send the full output to support@zotero.org with a link to this thread?

    return (await Zotero.HTTP.request('GET', 'https://doi.org/10.1038%2Fngeo722')).response
  • pszejner
    Sure, I just did that
    thanks for the support
  • dstillman
    Great, thanks. It's from your organization's network security software:
    Zscaler makes the internet safe for businesses by protecting their employees from malware, viruses, and other security threats
    So, yes, you'll need to speak to your IT department.
  • dstillman
    @pszejner: Oh, it's actually blocking Zotero because it thinks it's an old version of Firefox (on which Zotero is based):
    Not allowed to use the browser: Firefox (60.0)
    You should be able to fix this yourself by switching to the Zotero 7 beta.
  • pszejner
    I just deactivated the Zscaler. and the DOI look-up works...
Sign In or Register to comment.