Download EZproxy

Install EZproxy 6.4.4 GA for Windows

This document describes how to install EZproxy 6.4.4 GA for Windows. If you are updating from an older version of EZproxy, please refer to the update instructions.

Ability versus right

EZproxy allows you to extend access to your databases to remote users. However, your licensing agreement with database vendors may not authorize you to provide remote access. As an implementer of remote access, it is your responsibility to verify licensing agreements and only permit remote access as authorized.

Installation Instructions

EZproxy is a completely stand-alone application. It does not require nor use any existing web server that is already installed on your server.

If you are already running a web server on the system where EZproxy is running, do not attempt to install EZproxy within directories that are used by that web server.

If you are running IIS, do not install EZproxy within the inetpub directory, and do not try to configure a web server for EZproxy within IIS Manager.

Before getting started

EZproxy 6.4.4 requires users to obtain a WSKey to run the software. Before downloading EZproxy, please request your WSKey. To request and obtain a Key, please see How to Request a WSKey.

  1. Open a "Command Prompt" window by going to Start | Run..., typing
    in the Open: box, then clicking OK.

  2. Create a directory for EZproxy and make it your current directory with commands such as:
    md \ezproxy
    cd \ezproxy

  3. Download ezproxy-windows.exe (from the Download EZproxy page) into this directory.

  4. Rename ezproxy-windows.exe to ezproxy.exe with the command:
    rename ezproxy-windows.exe ezproxy.exe

  5. To create the default version of most of the files mentioned above, issue the command:
    ezproxy -m
    The "-m" stands for "missing file replacement," and this command can be used at any time to reconstruct any missing files without overwriting existing files that you have changed.

  6. Follow the instructions for your Windows Server to configure the Windows Firewall to work with EZproxy. This should include adding EZproxy as an exception using the firewall control panel. For more detailed steps, see documentation on firewall access for your server model.

  7. To verify whether EZproxy can automatically detect your host name correctly, as well as to check whether firewalls may interfere with your ability to use EZproxy, issue the command:
    ezproxy -c
    This command will make your server connect to an OCLC server. Your server will provide its name and IP address, and the OCLC server will attempt to verify this information. Your server will then display various messages to let you know what changes may be required for EZproxy to function properly.

    Note:If you do not like the idea of your server connecting to an OCLC server, you may omit this step.

    Note: If your network requires the use of a standard proxy server to connect out to the Internet, this test will fail. In this case, you will need to configure EZproxy to use your outgoing proxy server using the Proxy directive, and then you can complete the network connectivity test by finishing the installation of EZproxy and using a browser installed either on the same server or within your network to log in to the EZproxy Administration page, where you can use the Test network connectivity option. This performs a more thorough network test, including offering the option to incorporate your outgoing proxy server in the test.

  8. Use a text editor to edit the file config.txt. If suggested from the previous step, manually specify your host name in this file. The file also contains suggestions for other changes.

  9. Use a text editor to edit the file user.txt. To this file, add a line similar to this:
    changing someuser to the username you want to use for testing and somepass to the password you want to use for testing. In this example, admin should appear literally as shown.

  10. Copy your full WSKey from the OCLC Developer Network WSKeys screen (obtained by following the instructions at How to Request a WSKey), and paste it into your command prompt window with the key command as follows:
    ezproxy -k 123456789101112
    substituting your complete key for 123456789101112.

    Note: In the Windows Command Prompt, the keyboard shortcut Control-V will not paste copied text into the command line. You must right-click to open a list of options and click paste to enter the copied text.

  11. Start the server with the command:

  12. Using your web browser, connect to your server on port 2048. If your EZproxy server was named, you would use this URL:

  13. Enter the username and password that you created when you edited the user.txt file. This should bring you to the main server administration page.
    If, instead of the menu page, you end up at a page indicating that the EZproxy cookie was blocked, see EZproxy Cookie Blocked for information on why this happened and how to address it.

Note: The options presented and how effectively they work will depend on how well you customized config.txt. As you make additional changes to config.txt, you will need to stop and restart ezproxy to make the changes take effect.

After you have completed your installation and are able to log into the administration page, you can find the database stanzas necessary to configure resources on the Database Setup page and information about different authentication methods on the User Authentication page.

Installing as a Windows service

The configuration steps required to install EZproxy as a service so it starts up when the system is booted are available at Configure EZproxy to Run as a Windows Service.

Windows Error 1067

When installing EZproxy as a service under Windows, you may receive error 1067 when you try to start the service. This is a general error message that indicates that EZproxy failed to start successfully. When this occurs, try the following steps located here.


EZproxy runs on all versions of Windows 2000, Windows 2003, Windows 2008, Windows 2012, Windows 2016, Windows XP / XP Professional, Windows Vista, Windows 7, Windows 8, and Windows 10.

The minimum recommended configuration for an EZproxy for Windows server:

Pentium II 400 with 256 MB of RAM
10 MB of disk space is required for installation.
Additional disk space is required to accommodate user authentication files and server log files.

Additional System Considerations

This program can be executed from a non-privileged account, so please consider running it from a non-administrative account.

If your site employs a proxy server for all outgoing connections to the Internet, you will need to enter the host and port information for this proxy server into the config.txt file using the Proxy directive.

If your site is protected by a firewall, external users may be unable to connect to EZproxy unless your firewall administrator allows incoming traffic to ports 2048 and above.

User authentication

EZproxy provides a variety of methods for authenticating users. For more information on these options, see User Authentication.


EZproxy uses the following files:

Filename Purpose
ezproxy-windows.exe This binary file is the actual EZproxy program.
config.txt This user editable text file contains configuration directives, including information on your licensed databases. In EZproxy 5.0 and earlier, this file was named ezproxy.cfg.
user.txt This user editable text file contains user authentication information. At its simplest, this file contains usernames and passwords. In EZproxy 5.0 and earlier, this file was named ezproxy.usr.
ezproxy.log This text file is a record of proxy server usage in the NCSA web server log file format. If used with standard web log analysis software, this file can provide information on the volume of remote use.
messages.txt This text file is a record of certain informational and error conditions that occurred when EZproxy was running. In EZproxy 5.0 and earlier, this file was named ezproxy.msg.
ezproxy.hst This text file contains information on active users and virtual web server proxies.
license.txt This text file is the licensing agreement for this program.
*** The following user editable HTML files are located in the docs subdirectory. ***
cookie.htm EZproxy uses a domain-based cookie as its ongoing verification that a user has authenticated. If the remote user disallows the cookie, the contents of this file are sent to explain the reason why the cookie is required.
login.htm When the built-in user validation feature is used, this web page is sent to the remote user to prompt for authentication.
loginbu.htm If the user does not successfully authenticate to the login.htm page, the user is sent this page.
logout.htm When the user logs out from EZproxy, this web page is sent to confirm the logout.
menu.htm This web page provides a basic menu of databases. In most instances, this file is only used for testing purposes. For production use, you are more likely to create URLs in remote documents that look like which users will then use to connect to remote databases. See also LoginMenu.

Note: You will only download ezproxy-windows.exe. All of the other files are created automatically during the installation process.

Technical details

Additional technical information can be found at EZproxy Technical Notes.


The following are additional commands that can be used with EZproxy for Windows.

Resetting all files

If you want to reset all of the files to their original distributed contents, you can use the command:

ezproxy -r

If you want to restore just one or two of the original files, rename or delete the existing file that you want replaced, then issue the command:

ezproxy -m

This page last revised: December 26, 2017