Communication Ports for VDI & DaaS (US Region)

This article covers the communication requirements for deploying ControlUp version 9.0 and higher for VDI & DaaS in the US + rest of the world (non-EU) region. Visit these articles to see the communication requirements for:

• Synthetic Monitoring (Scoutbees)
• ControlUp for Physical Endpoints & Apps
• Communication Ports for VDI & DaaS (EU Region)

Network testing tool

You can use our network connection testing tool to make sure you have all the network communication requirements in place.

9.0 Specific URLs

All 9.0 and higher specific URLs below need to be accessed via port 443. All these services are running via REST.

9.0 Monitors

9.0 and higher monitors initially attempt to connect to cu-services-cpa.controlup.com. Depending on their geolocation, they will then attempt to connect to a region-specific URL (either -us or -eu). If your organization operates monitors in different geographical regions, we highly recommend to allowlist all URLs as listed below to avoid communication issues.

Outbound Connections

The following table includes all the communication ports that you need for ControlUp to work properly. To use our integrations, you must allowlist mandatory ports and URLs, as well as mandatory outbound URLs.

When you use a proxy in your environment, you must allowlist and open the ControlUp cloud configuration servers through your proxy.

From the Real-Time Agent Machine*

For the optional outbound communication feature, ensure you allowlist the following URLs. Similarly, we recommend to allowlist all URLs if your agent machines operate across various geographical locations.

* These URLs are only relevant to use Agent Outbound Communication in ControlUp version 9.0

From the machine used to access the DEX Platform web app

To manage your VDI & DaaS environment from the web UI, your machine must have access to:

9.0 Consoles

9.0 and higher consoles initially attempt to connect to cu-services-cpa.controlup.com to retrieve a list of required backend services. Similar to the monitors, we highly recommend to allowlist all URLs, especially if you are operating the console on machines across different geographical regions.

From the Real-Time Console Machine

To use the Real-Time DX desktop console (used for configuration and connecting to your virtual infrastructure), your machine must have access to:

From the Real-Time Monitor Machine

From the Real-Time Data Collector Machine

Required Connection for Real-Time Reports from New Data Pipeline

To enable ControlUp monitors to send data to the new data pipeline for reporting, add the respective URL to your allow list based on your region:

• https://monitor-receiver-azure-eastus-prod.controlup.com/v1/data
• https://monitor-receiver-azure-canadacentral-prod.controlup.com

Or by IP address, as mentioned in the Monitor table above:

• 20.168.200.122 (US East)
• 20.220.227.160 (Canada)

If you use legacy reports to view historical data, add the following URLs to your allow list:

• https://cu-services-cpa-us.controlup.com
• https://cu-services-cpz-us.controlup.com

Synthetic Monitoring

ControlUp for VDI & DaaS includes proactive synthetic testing for your network infrastructure and EUC gateways. Visit Communication requirements for Scoutbees for details.