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?
Created on Sep 15, 2014 1:27:04 PM by
5 Replies
Accepted Answer
This article applies to PRTG Network Monitor 13 or later
PRTG Port Usage
PRTG requires several ports on your system to be open and reachable for full functionality. You have to make sure that specific ports are available on the PRTG webserver, for remote probes, clustering, and for various monitoring technologies.
Please 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 one in the webGUI in the User Interface settings, section Web Server. The Enterprise Console also uses this port to connect to the server, as well as mobile apps. 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 webserver port is used. If necessary, you can change this in the registry. |
| Auto-update and activation | 443 | See this article for details. |
| Update check and download | 80 | See this article for details. |
| Active Directory integration | TCP and UDP 389 (non-secure), TCP 636 (SSL) | LDAP port for AD 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 the port 80 (443 for SSL) by default and starts before PRTG so that the port is not available for PRTG. Please 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 on the core server only. Please see this article if you need to change it. |
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. For this purpose, the particularly used 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; see this article for details |
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
Created on Sep 15, 2014 1:29:29 PM by
Last change on Sep 28, 2018 7:12:18 AM by
Hi Daniel,
I want to monitor a server remotely from an external network. Both the networks are connected through VPN.
If i just open one firewall port for remote probe - 23560 (or Cluster Port set by me in the PRTG Administrator), can i use all sensors like CPU monitoring, Disk Space monitoring etc. and will i be able to monitor windows services (restart it if it's down)
Regards, John
Hi John,
As long as you make sure that the Remote Probe(s) are reachable using the specific port through VPN, you're all set. See also the White Paper on Remote Probes: https://www.paessler.com/press/whitepapers/white_paper_managing_central_monitoring
Regards, Erhard
Created on Aug 10, 2015 9:38:01 AM by
Hello!
What port use PRTG when use Remote PowerShell scripts (for ex. Exchange Mail Queue).
Thank you!
Hello Vasiliy,
That should be either 5985 (for HTTP) or 5986 (for HTTPS).
Kind regards,
Erhard
Created on Feb 12, 2019 1:42:48 PM by
Please log in or register to enter your reply.
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.
Add comment