See the ports you need to open for your ActiveGates, depending on their types and your deployment scenario.
|9999||OneAgent||Environment and Cluster ActiveGate||HTTPS|
|9999||Environment ActiveGate||Cluster ActiveGate||HTTPS||Dynatrace Managed only|
|8443||Environment and Cluster ActiveGate||Managed Cluster node1||HTTPS||Dynatrace Managed|
|443||Environment and Cluster ActiveGate||Managed Cluster node1||HTTPS||Dynatrace Managed|
|443||Environment ActiveGate||Cloud/virtualization environments (AWS, VMware, Azure, GCP)||HTTPS|
|443||Environment ActiveGate||Dynatrace Server||HTTPS||Dynatrace SaaS only|
9999 that is used for communication with OneAgents and other ActiveGates can be manually re-configured in the ActiveGate
If you use Browser monitors or HTTP monitors in private synthetic locations, you need to make sure the synthetic-enabled ActiveGate has access to the tested resource. If you use ActiveGate plugins, you need to make sure the ActiveGate executing the plugins has access to the monitored technology.
For Dynatrace Managed, ActiveGate must have network access to other services as well on specific ports, based on your deployment scenario.
1 Dynatrace environments with a cluster version earlier than 1.166 use port
8443. New Dynatrace environments still use port
8443, but this port doesn't need to be exposed to the outside of the cluster nodes. Upgraded Dynatrace environments preserve port settings from the previous version. As a result, it is possible to have an upgraded Dynatrace environment that still uses port