on
02 Nov 2022
07:45 AM
- edited on
23 Jan 2026
10:36 AM
by
IzabelaRokita
Summary: This article describes how to address scenarios where OneAgent network protection blocks a port. It outlines configuration changes and exemptions that allow the application to use the required port safely.
OneAgent consists of multiple processes that communicate with a watchdog via a TCP port. At startup, OneAgent watchdog attempts to open the first available port between ports 50000 and 50100. In some cases, you may need this port for your own applications that are started after OneAgent. In such cases, you can change the port range that the OneAgent watchdog uses by calling the OneAgent command-line interface.
You can change the watchdog listening port by using
set-watchdog-portrange
via oneagentctl command-line tool:
./oneagentctl --set-watchdog-portrange 50005:50105
.\oneagentctl.exe --set-watchdog-portrange 50005:50105Restart OneAgent service to apply changes.
See Which network ports does Dynatrace Server use? for information on the ports used by Dynatrace.
Change the port range that the OneAgent watchdog uses by modifying the file watchdoguserconfig.conf.
-portrange=50000:50100
To:-portrange=50005:50105
Managing the watchdog port range is easy, but when it comes to the other OneAgent processes like oneagentos, things get more tricky. Some discussion on that topic can be found here: