Which network ports does ActiveGate use?

See the ports you need to open for your ActiveGates, depending on their types and your deployment scenario.

Origin	Port	Destination	Deployment
OneAgent	9999	Cluster ActiveGate	Managed only
OneAgent	9999	Environment ActiveGate	Managed and SaaS
Cluster ActiveGate	443¹	Managed Cluster Node	Managed only
Environment ActiveGate	9999	Cluster ActiveGate	Managed only
Environment ActiveGate	443¹	Managed Cluster Node	Managed only
Environment ActiveGate	443	Cloud/virtualization environments	Managed and SaaS
Environment ActiveGate	443	SaaS DESK Server	SaaS only

Origin	Port	Intermediate	Port	Destination	Deployment
Environment ActiveGate	9999	Cluster ActiveGate	443¹	Managed Cluster Node	Managed only

The port 9999 that is used for communication with OneAgents and other ActiveGates can be manually re-configured in the ActiveGate custom.properties file.

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 DESK Managed, ActiveGate must have network access to other services as well on specific ports, based on your deployment scenario.

¹ DESK environments with a cluster version earlier than 1.166 use port 8443. New DESK environments still use port 8443, but this port doesn't need to be exposed to the outside of the cluster nodes. Upgraded DESK environments preserve port settings from the previous version. As a result, it is possible to have an upgraded DESK environment that still uses port 8443.