Related Links:
In this Topic Hide
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.
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.
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 |
Updates periodical check for the GUI |
TCP/80 (HTTP) from Zend Server to updates.zend.com |
If closed, no updates will be listed in the Administration tab. This does not affect the Linux package managers’ ability to fetch updates. |
Update Notification Email Subscription |
TCP/80 (HTTP) from Zend Server to now.eloqua.com |
Optional, one time only. Not required for normal operation. |
Function |
Port / Protocol |
Comments |
Event Reporting – Zend Server Cluster Manager |
TCP/3306 (MySQL) from cluster members to DB Server |
DB Server may be on the machine running Zend Server Cluster Manager, or may be on a dedicated machine, depending on your configuration. Only required when running in Cluster. |
Event Viewing – Zend Server Cluster Manager |
TCP/3306 (MySQL) from Zend Server Cluster Manager to DB Server |
DB Server may be on the machine running Zend Server Cluster Manager, or may be on a dedicated machine, depending on your configuration. Only required when running in Cluster. |
Event E-mail Action |
TCP/25 (SMTP) from Zend Server to configured mail server |
Optional, depends on configuration. Only used if e-mail action is enabled. |
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. |
Event Debugging and Profiling |
HTTP/S on application port (usually TCP/80) from Zend Server or Zend Server Cluster Manager to application server or alternate debugging server |
The Zend Server/Zend Server Cluster Manager GUI will attempt to reproduce the original triggering HTTP request when debugging an event. For this reason, in order to debug or profile an event, the GUI must be able to send HTTP/S requests to the same host name / port on which the application runs, or to an alternate debugging server if one is configured. |
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. |
Function |
Port / Protocol |
Comments |
Java Bridge |
TCP/10001 (Proprietary JB Protocol) on localhost from Zend Server to local JVM |
Function |
Port / Protocol |
Comments |
Job Queuing |
TCP/10085 (Proprietary JQ protocol) from Zend Server to Job Queue Daemon (on local or remote machine) |
On Linux, Zend Server is configured by default to use UNIX Domain Sockets instead of TCP. Opening port is only required in cluster or when queuing to a remote machine. |
Job Execution |
TCP/80 (HTTP) or any other port, depending on Job URL, from Job Queue Daemon to executing server |
Application Dependant: target host and port depend on Job URL, which may change per job. |
Function |
Port / Protocol |
Comments |
Session Data Exchange – PHP to Session Clustering Daemon |
TCP/10062 on localhost on each Zend Server instance Windows only. |
In Linux, UNIX Domain Sockets are used by default. |
Session Data Exchange – Cluster Members |
TCP/10060 between Zend Server instances |
May be initiated between any pair of Session Clustering Daemons. Kept open until connection times out. |
Graceful Shutdown |
TCP/10063 between Zend Server instances |
Initiated during graceful shutdown / startup between the terminated server and replacement servers. |
Session Clustering Discovery and Status Checks |
UDP/10070 between Zend Server instances |
UDP Broadcast or Unicast (depending on configuration) between all cluster members.
|
|
|
|
Related Links: |
|
|