Skip to main content
OCLC Support


End of support for EZproxy on Solaris platform
OCLC ended support for EZproxy on the Solaris 10 (x86) platform on October 31, 2018. We no longer provide software for this platform. We will continue to provide Linux and Windows versions of the software. Customers using EZproxy on Solaris should plan to move their installation of EZproxy to Linux or Windows. If you have questions about this change, please reach out to Customer Support (

LoginPort specifies a port on which EZproxy should listen for incoming login, menu, and administration requests using http. The first LoginPort directive establishes the port that EZproxy will use when generating URLs that point to itself using http. Subsequent LoginPort directives establish additional ports on which EZproxy should listen for http requests.

By default, EZproxy listens on all IP interfaces. If the Interface directive is employed before LoginPort, then EZproxy will only attempt to listen on the specified interface and port.

On Linux, if port is below 1024 and -Virtual is not specified, then EZproxy must be started by the root user. In this instance, the RunAs directive can be used to direct EZproxy to change to a different user account once listening has been established on the specified port(s).

Qualifier Description
port The port on which EZproxy should listen for incoming http requests.
Option Description
-Virtual Do not actually listen on the port. When used, an additional LoginPort directive must follow to establish an actual port on which EZproxy should listen for requests.
LoginPort [-Virtual] port
Configure EZproxy to listen on the standard http web server port 80.
LoginPort 80

Migrate an existing EZproxy server with URLs that point to port 2048 to start using port 80. The sequence of LoginPort directives is crucial, as EZproxy will generate any URLs that points to itself based on the first LoginPort directive.

LoginPort 80
LoginPort 2048

Migrate an existing EZproxy server with URLs that point to port 2048 to start using port 80 on a server that already has an existing web server that already uses port 80. In this scenario, a second IP address is added to the server ( in this example). Refer to separate technical notes regarding adding additional IP addresses to existing servers for more information on this configuration.

LoginPort 80

Interface Any
LoginPort 2048

Direct EZproxy to act as though it is listening on port 80, but actually listen on port 8080. This configuration only works if a firewall is performing network address translation of external port 80 internal port 8080.

LoginPort -Virtual 80
LoginPort 8080
Related directives
FirstPort, Interface, LoginPortSSL, RunAs
  • Was this article helpful?