You are currently viewing Zend Server 5.x documentation. Click here to view the latest Zend Server online documentation.

You are here: Zend Server Installation Guide > Post Installation > Ports and Services

Ports and Services

Web Server Ports

According to your choice of operating system and installation method, your web server on which Zend Server is installed, will be listening on a different port.

Linux using DEB or RPM packages:
Zend Server will be installed on the distribution supplied web server which listens to port 80 by default. This can be set to another port by editing your Apache configuration.
Windows on IIS:
Zend Server will be installed on the built-in IIS web server which listens to port 80 by default. This can be set to another port from the IIS configuration Manager.
Windows on Apache:
Zend Server will be installed on the bundled Apache web server which listens on port 80 by default. unless a different port was selected during installation. This can be set to another port from your Apache configuration file at <install_dir>\Apache2\conf\httpd.conf and changing the value of the directive Listen.

Firewall Settings

The following document describes the minimal set of ports that must be opened in your firewall in order for the different Zend Server and Zend Server Cluster Manager components to function.

If you are not using one of the Zend Server or Zend Server Cluster Manager components listed below, you are not required to open any of its related ports.

Note

Most ports can be configured. Each component’s relevant documentation includes configuration details.

Zend Server Administration Interface (Web GUI)

Function	Port / Protocol	Comments
Web GUI Access	TCP/10081 (HTTP) from client browser to Zend Server and from Zend Server Cluster Manager to Zend Server	Should be open for administrative access, and between Zend Server Cluster Manager and cluster members. May be blocked if HTTPS (10082) is always used.
Web GUI Access	TCP/10082 (HTTPS) from client browser to Zend Server and from Zend Server Cluster Manager to Zend Server	Linux only. Should be open for administrative access, and between Zend Server Cluster Manager and cluster members. May be blocked if HTTPS is never used.
Local Web Server Control for Zend Server GUI	TCP/10083 (HTTP) on localhost on Zend Server	Must be open for localhost access only

Debugging and Profiling

Function	Port / Protocol	Comments
Debugging / Profiling in open LAN	TCP/10137 (Proprietary Debugger Protocol) from Zend Server (the debugging server) to Zend Studio (client machine)	Zend Studio must be able to accept incoming connections from server. Will work when server and client are in the same LAN. If machines are separated by NAT routers or Firewalls, usage of tunneling or SSH port forwarding is required.
Tunneling	TCP/80 (HTTP, persistent connection) from Zend Studio to Zend Server.	Linux / Mac only. Required to bypass NAT routers or Firewalls between Zend Studio and Zend Server. Connection starts as HTTP but is kept alive after HTTP request ends, and will be used to tunnel debugging traffic.
Studio Settings Auto-Detection	TCP/20080 (HTTP) on localhost on the client’s machine	No interaction with the server is required - sent using AJAX to http://localhost:20080 by the user’s browser, in order to check Zend Studio configuration before debugging events. Not used if Studio Settings auto-detection is turned off.

Zend Java Bridge

Function	Port / Protocol	Comments
Java Bridge	TCP/10001 (Proprietary JB Protocol) on localhost from Zend Server to local JVM