What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Which ports does PRTG use on my system?



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?

cluster firewall monitoring ports prtg remote-probe reports tcp udp webserver

Created on Sep 15, 2014 1:27:04 PM by  Gerald Schoch [Paessler Support]

7 Replies

Accepted Answer



This article applies as of PRTG 22

Important notice: This article is no longer kept up to date. See the PRTG Manual: List of Default Ports for up-to-date information.

PRTG port usage

PRTG requires that several ports on your system are open and reachable for full functionality. You must 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.

PRTG web server

Port userPort numberRemarks
Web serverTCP 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 PRTG 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+.
Reports8085 (PDF reports)This port is only opened and blocked on the local PRTG core server (localhost). For HTML reports, the configured web server port is used. If necessary, you can change this in the registry.
Auto-update and activation443For details, see Which servers does PRTG connect to for software auto-update, activation, etc.?
Update check and download80For details, see Which servers does PRTG connect to for software auto-update, activation, etc.?
Active Directory integrationTCP 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 userPort numberRemarks
Connections between remote probes and PRTG core server23560It is sufficient to open or forward this TCP port only on the PRTG core server. If you need to change it, see How can I customize ports for core-probe-connections used by PRTG?

PRTG application server

Port userPort numberRemarks
Connections between the PRTG application server and the PRTG core server23580


Port userPort numberRemarks
Communication between cluster nodes23570All communication between cluster nodes is directed through this TCP port.


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. You can find a comprehensive and up-to-date list of all ports used by sensors in the PRTG Manual: List of Default Ports.

Note: The used ports can be different depending on your configuration. Usually, you can change the default ports in PRTG in the root, group, probe, device, and/or sensor settings.


NotificationPort numberRemarks
PushTCP 443Target 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).
SNMP TrapUDP 162
SyslogUDP 514


Created on Sep 15, 2014 1:29:29 PM by  Gerald Schoch [Paessler Support]

Last change on Sep 7, 2023 8:08:25 AM by  Jacqueline Conforti [Paessler Support]



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

Created on Aug 10, 2015 7:47:56 AM



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  Erhard Mikulik [Paessler Support]




What port use PRTG when use Remote PowerShell scripts (for ex. Exchange Mail Queue).

Thank you!

Created on Feb 12, 2019 1:12:06 PM



Hello Vasiliy,

That should be either 5985 (for HTTP) or 5986 (for HTTPS).

Kind regards,


Created on Feb 12, 2019 1:42:48 PM by  Erhard Mikulik [Paessler Support]



Do PRTG Core servers require inbound access to TCP port 44387 for file transfer w/ Beta features like Probe Transfer & Config viewer? If so, is the port used for any other features?

Created on Nov 3, 2022 9:45:27 PM

Last change on Nov 8, 2022 5:06:29 AM by  Felix Wiesneth [Paessler Support]




port 44387 is not used by default. PRTG uses 443 for HTTPS, 80 for HTTP redirection to HTTPS and 8085 for reports.

Created on Nov 4, 2022 11:58:13 AM by  Arne Seifert [Paessler Support]

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.