This article applies to PRTG Network Monitor 8 or later
Free Port 443 for Use With PRTG's Web Server
In order to connect to PRTG's web server securely, you can set it to use https on port 443. In order for this to work, the port must not be occupied by any other application or service.
When running an IIS, it might (by default) listen on all IP addresses configured on the current machine, and therefore block port 443 for the address you're trying to use with PRTG.
In order to run PRTG side-by-side with a Microsoft Internet Information Service (IIS), please add all addresses actively used by your (non-PRTG) websites to the IP listen list, e.g. using the following command:
netsh http add iplisten ipaddress=x.y.z.w
Additionally, make sure that none of the addresses you want to use with PRTG appears in the IP listen list. To show the list, you can use the following command:
netsh http show iplisten
Once you made sure port 443 for the respective IP address is free, you can use it with PRTG.
UPDATE: Custom Port for PRTG SSL Web Server Available
You can now also configure PRTG to run on a port number different from 443. This can be an alternative solution when running a web server on the same machine..
As of version 12.3.4 [Stable] a custom SSL port for the PRTG web server can now be defined.
Quote from the version history:
Improved [Core]: PRTG web server can now run on https (SSL) on a user specific port (other than 443)
See Also
Why does PRTG block IIS SSL sites?
Add comment