Can we change the PRTG Service to use another port?

Please use the PRTG Administration Tool to change the port of PRTG's web server. This is a Windows application you can start on the computer where your PRTG core server is running.

For a list of ports that PRTG requires, please see the article Which ports does PRTG use on my system?

Hello,

we changed the default SSL port of our PRTG instance to 9443, as we don't want the either 443 or 8443 to be used (there other applications running on these ports).

When starting PRTG, the Application Server Sensor shows everything red (as in no data can be read/retrieved). Addind new sensors or consulting the logs is also not possible, so I guess the PRTG Application Server cannot be started.

Looking at the logs on C:\ProgramData\Paessler\PRTG Network Monitor\Logs\appserver\Server.log we see the following:
> Could not bind endpoint to address 127.0.0.1:8443: cannot bind webserver to "127.0.0.1:8443"

So even though we changed the SSL Port to 9443 (through the PRTG Admin Tool), somehow internally the App Server is still trying to use the 8443 port.

How can we change this behaviour? Can we set the used port with a RegKey?

Regards

Hello Johann,

The Application Server Sensor monitors the status of the new UI (its application server), it does not show the status of the current web interface. Since you can see the status of the Application Server sensor, I assume that the current web interface still works, and that only the new UI does not work, is this correct?

Kind regards,
Sasa Ignjatovic, Tech Support Team

Hello Sasa,

yes that seems to be the case. So by the looks of it the Application Server (aka the new UI?) is hardcoded with both ports 8443 and 8080. We set PRTG to non-SSL Ports, and we see on the Application Server in error state and its log file shows the following:

ERRR TId 0 Server> Could not bind endpoint to address 127.0.0.1:8080

The machine this PRTG instance is running on has already applications using the default ports (443 and 80 for IIS and 8443 for Windows Admin Center). So no matter what alternative port we assign to the main PRTG Web Server, the Application Server will always fail to bind a port. This is what we tried:

• SSL Setup: PRTG Webserver configured with 9443 -> App Server tries to use 8443
• No SSL Setup: PRTG Webserver configured with 8080 -> App Server tries to use 8080

Note: through the PRTG Admin Tool one cannot setup 8080 explicitly, but I suppose the Web Server uses 8080 as a fallback from the port 80 in case this one is in active use (which is our case).

So ultimately we won't be able to use new UI on our current environment. Is there any planned improvement regarding the used ports on the App Server?

Hello Johann,

Thank you for the reply.

As you noticed, the port for the Application Server (for the new UI) is hard coded, and currently it is not possible to change it. It is planned to implement this feature in the future, but there is no ETA for it yet.

Kind regards,
Sasa Ignjatovic, Tech Support Team