Answered By: Jeff Beuck Last Updated: Aug 25, 2023 Views: 6122
During periods of unusually high usage, Google Scholar may begin asking Cleveland State University patrons to fill out a reCAPTCHA widget to prove they're not robots. Unfortunately, there is a security bug in this widget that may result in "Invalid domain for site key" errors for patrons who are using the Library's off-campus proxy server.
If you run into this error when trying to access full text articles in Google Scholar, there are two ways to work around it:
Workaround #1: If you have your own personal Google Account, link it to the Library:
- Go directly to the un-proxied version of Google Scholar at https://scholar.google.com/ .
- Click the "Sign In" button and log in with your Google account.
- From the menu icon (three bars at top left), select "Settings", then "Library Links".
- In the Library Links section of the Settings menu, search for "Cleveland State". Select the checkbox next to "Cleveland State Univ - Full text from CSU" then click the "Save" button in the lower right.
- Save and return to the GoogleScholar homepage. You now should be able to search Google Scholar without using CSU's off-campus proxy, but still see the "Full text from CSU" links that lead you to our full-text databases.
Workaround #2: If you don't have a personal Google account, use the Library's temporary search page to bypass the broken reCAPTCHA widget: https://library.csuohio.edu/temp/google-scholar-test.html .
If neither of the above workarounds fixes your Google Scholar access, please contact us at https://library.csuohio.edu/forms/connect.html . Google also usually resets the problematic reCAPTCHA requirement after about 24 hours.
Links & Files
Was this helpful? 0 0
Comments (1)
-
Hey there! Facing the "ERROR for site owner: Invalid key type for enterprise key" can be a real head-scratcher. While not enabling pricing for the enterprise version shouldn't be the root cause, there might be a slight hiccup in the setup. Firstly, double-check that the keys generated match the enterprise version. Sometimes, copy-paste gremlins cause chaos. If that doesn't do the trick, ensure your domain registration matches the one used during key creation. Mismatched domains can lead to a cryptic error dance. Now, for the genius part, your detailed guide on tackling this error is a must-read. I stumbled upon it (pure luck!), and it's a goldmine for troubleshooting. Check it out here: Invalid Domain for Site Keyby shasi_99 on Jan 30, 2024