- Print
- DarkLight
- PDF
9.0 - New Communication Ports and URLs
- Print
- DarkLight
- PDF
Before upgrading to version 9.0, ensure that ControlUp components are allowed to communicate with our new backend services. This article lists only the new URLs that need to be whitelisted. Add these new URLs in addition to URLs needed in previous versions. You can find the full list of required URLs here for US organizations and here for EU customers
All URLs you find below need to be accessed via port 443. All these services are running via REST.
Monitors
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 whitelisting all URLs as listed below to avoid communication issues
- cu-services-cpa.controlup.com
- cu-services-cpa-us.controlup.com
- cu-services-cpa-eu.controlup.com
- cu-services-cpz-us.controlup.com
- rt-app-services-us.controlup.com
Consoles
The console will also attempt to connect to cu-services-cpa.controlup.com to retrieve a list of backend services required for version 9.0. Similar to the monitors, we highly recommend whitelisting all three URLs, especially if you are operating the console on machines across different geographical regions
- cu-services-cpa.controlup.com
- cu-services-cpa-us.controlup.com
- cu-services-cpa-eu.controlup.com
Agents
For the optional outbound communication feature, ensure you whitelist the following URLs. Similarly, we recommend whitelisting all URLs if your agent machines operate across various geographical locations.
- cu-agents-cpa.controlup.com
- cu-agents-cpa-us.controlup.com
- cu-agents-cpa-eu.controlup.com
For the remote control feature in VDI & DaaS, whitelist the following URLs
- solve-ws-proxy-us.controlup.com (IPs: 3.210.212.180 and 44.205.79.193)
- solve-ws-proxy-eu.controlup.com (IPs: 18.194.198.179 and 18.159.29.205)