Supported operating systems and browser versions

ebrary’s reader requires recent versions of operating systems and browsers as follows:

Supported operating systems:

  • Windows:  7, 8, 8.1
  • Windows 10 is currently certified for the ebrary Reader only (August 2016).  Other features such as search, bookshelf and admin tools have not yet been certified for Windows 10.
  • OS X:  10.8 (Mountain Lion) and 10.9 (Mavericks)

Note that Windows RT is not supported.

Supported browsers: The browser versions we support parallel the frequency with which the browsers auto-update.

  • Chrome:  latest version
  • FireFox:  latest two versions
  • Safari:  latest two versions
    • For Safari, “Private Browsing” does not work when using proxied links
  • Internet Explorer:  versions 9, 10 and 11 only. Note that  the “Allow font downloads” policy setting in Internet Explorer needs to be enabled for correctly displaying some navigation  icons.
    • For IE 9, make sure compatibility mode is turned off
    • IE 8 is not supported with the new reader as its underlying architecture is limiting when it comes to applying modern UX web designs and coding techniques.

Note that browser add-ons/extensions that alter or add a suffix to ebrary URLs do not work with ebrary.

  • Example:  “Dragon NaturallySpeaking” browser extension

Troubleshooting when pages of a book won’t load

Once you click “Read Online” you should see the following icons, and below them, the cover or first page of the book.

If the icons or pages don’t show, check the following:

1.  Javascript needs to be enabled on your browser

2. Certain domains and/or IPs cannot be blocked:

  • * (see below if you cannot use *)
  • eb_reader.js
  • require.min.js
or if you cannot use *, then:

If a site can only whitelist IPs, not domains, the following IPs should be whitelisted:

  • (for *
  • (for
    Note, ebrary sites in China do not use ajax, so do not need to unblock for sites in China
3. Certain ports cannot be blocked:
  • All of the above domains use standard ports 80 and 443

4. Make sure Java cache isn’t full

  • To clear your Java cache:
    • Open your computer’s Control Panel
    • From there, open “Java”
    • Under “General” tab, ” Temporary Internet Files”, click “Settings…”
    • Then click “Delete Files…”
5. Some VPNs are not compatible with ebrary
  • URL-rewriting VPNs are not compatible with ebrary
6. Don’t use VPN if using another form of remote authentication, such as:
  • proxied links
  • EZproxy SSO
  • ebrary-hosted remote access (RPA)
  • Athens
  • Shibboleth
  • Referring URL

7. In Safari, “Private Browsingdoes not work when using proxied links

8. “Accessibility Mode” causes fewer icons to be displayed.

  • This is a special setting to work with screen readers, and somehow your username may be in this mode.
  • For a screenshot showing the limited icons displayed in Accessibility Mode,  >see more
  • The team at can check your username’s settings.


To check what version of Java you are running (PC)

ebrary requires Java.  To check that you have a recent version of Java:

  • Under the Windows start menu, go to Control Panel
  • Then select Programs
  • Click to open Java
  • On the General tab, click the About button
  • The installed version of Java will then display

Make sure javascript is enabled in your browser

For ebrary to work, Javascript needs to be enabled.

For directions to enable Javascript for all browser types, see:

We’ve also written instructions specifically for Google Chrome:

1. Under the 3 bars icon, select “Settings”

2. Select “Show advanced settings”

3. Under “Privacy”, select “Content Settings”

4. Under “JavaScript”, click “Allow all…”

5. Click “Done”



“Java-based Reader” Installation Issues

To open a book for online reading, we recommend clicking on its title or cover.

However, if your ebrary site happens to also offer ebrary’s older stand-alone reader, the “Java-based Reader” (aka the Unity Reader), and you wish to use it, click the “Java-based Reader” button instead; it is located below the book in search results.

The Java-based Reader is being phased out and may not work smoothly on newer systems, here are some tips if you experience problems:

  • Make sure you have the most recent version of Java, at least version 7
  • Cookies need to be enabled

Error Code 102 usually means the Unity Reader was unable to connect to ebrary servers, here are some suggestions:

  • must not be blocked on ports 80 and 443
    • This has been a common problem with sites that are using proxies
  • Make a firewall exception for the Unity Reader
  • Make sure you have write access to your home directory
    • The Unity Reader does not require admin rights for installation but it creates personalized files for users in their home directory
    • Occasionally, roaming profiles have resulted in issues with this

Error Code 30 issues or expired/invalid session errors:

  • If you are using a proxy such as a Bluecoat or Squid Proxy, ensure the proxy server does not cache-control any content from ebrary.

If you are still having trouble, visit the following diagnostic sites and send the results to us.