I would like to know the ports that PRTG requires for full access and functionality. Can you please provide a list with all (potentially) used ports?
This article applies as of PRTG 20
PRTG port usage
PRTG requires that several ports on your system are open and reachable for full functionality. You have to make sure that specific ports are available on the PRTG web server, for remote probes, clustering, and for various monitoring technologies.
See the following tables for all used ports.
Web server
| Port User | Port Number | Remarks |
|---|---|---|
| Web server | TCP 80 (HTTP), 443 (HTTPS) Fallbacks: 8443 and 8444+ (HTTPS), 8080+ (HTTP) | You can change the TCP port or define a custom TCP port in the PRTG web interface under Setup | System Administration | User Interface, section Web Server. PRTG Desktop and the PRTG apps for iOS or Android also use this port to connect to the server. For versions previous to 18.3.44, the HTTPS fallback ports are 8443 and 32000+. |
| Reports | 8085 (PDF reports) | This port is only opened and blocked on the local PRTG server (localhost). For HTML reports, the configured web server port is used. If necessary, you can change this in the registry. |
| Auto-update and activation | 443 | For details, see Which servers does PRTG connect to for software auto-update, activation, etc.? |
| Update check and download | 80 | For details, see Which servers does PRTG connect to for software auto-update, activation, etc.? |
| Active Directory integration | TCP and UDP 389 (non-secure), TCP 636 (SSL) | This is the LDAP port for Active Directory integration. |
Note: If the PRTG web server always uses a fallback port after a server restart, check for programs that use the same port as PRTG on startup. For example, the integrated Microsoft IIS web server uses port 80 (443 for SSL) by default and starts before PRTG so that the port is not available for PRTG. This is why you need to define a different port for IIS or disable it. You can also disable the World Wide Web Publishing Service on startup to get the same effect.
Remote probes
| Port User | Port Number | Remarks |
|---|---|---|
| Connections between remote probes and core server | 23560 | It is sufficient to open or forward this TCP port only on the core server. If you need to change it, see How can I customize PRTG’s ports for core-probe-connections? |
Cluster
| Port User | Port Number | Remarks |
|---|---|---|
| Communication between cluster nodes | 23570 | All communication between cluster nodes is directed through this TCP port. |
Monitoring
PRTG sensors use various monitoring technologies to query the desired data. These technologies need open ports for the communication between the PRTG core server and the monitored devices in the network.
| Technology | Port Number (default) |
|---|---|
| Cloud (Ping and HTTP) | TCP 443 (8443 before PRTG version 15.4.20) |
| HTTP (proxy) | TCP 8080 |
| IMAP | TCP 143 (non-secure), 993 (SSL) |
| LDAP | TCP/UDP 389 (non-secure), TCP 636 (SSL) |
| MSSQL | TCP 1433 |
| MySQL | TCP 3306 |
| Oracle | TCP 1521 |
| POP3 | TCP 110 (non-secure), 995 (SSL) |
| PostgreSQL | TCP 5432 |
| SMTP | TCP 25 (non-secure), 465 (SSL), 587 (SSL) |
| SNMP | UDP 161 |
| SNMP Trap | UDP 162 |
| SSH | TCP 22 |
| Syslog | UDP 514 |
| WBEM | TCP 5988 (non-secure), 5989 (SSL) |
| WMI | TCP 135, high port ranges 49152-65535 and 1024-5000; for details, see My WMI sensors don't work. What can I do? |
Note: This list might not be complete. The used ports can be different depending on your configuration. Usually, you can change the default ports in PRTG in the particular device and/or sensor settings.
Notifications
| Notification | Port Number | Remarks |
|---|---|---|
| Push | TCP 443 | Target URL: https://api.prtgcloud.com:443 Note: In PRTG versions previous to 15.4.20, push notifications used port 8443 (https://push.prtgcloud.net:8443). |
| SMTP | TCP 25 | – |
| SNMP Trap | UDP 162 | – |
| Syslog | UDP 514 | – |
More
- How To Change the Port Used for Report Generation?
- Which servers does PRTG connect to for software auto-update, activation, etc.?
Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
