A user encountered an error related to network communication after upgrading to version 9.0. They were asked to specify their region and test various components, including Real-Time DX, Agent Outbound, and Scoutbees. Additionally, they were informed that agents will try to reach out to cu-agents-cpa.controlup.com in order to retrieve a Personal Access Token for communication with ControlUp Monitors.
Read the entire ‘Troubleshooting Network Communication Issues in ControlUp 9.0’ thread below:
URL –> https://cu-agents-cpa.controlup.com validation result: Validation Failed.This issue is related to Network communication.
is this new with 9.05? after upgrading, our Monitor is failing to upload
What region are you on? If you are in US/ROW type ‘us’ – For EU, type ‘eu’: us
Are you testing Real-Time DX (Hybrid Cloud)? yes/no: yes
Are you testing Agent Outbound? yes/no: yes
Are you testing Edge DX? yes/no: no
Are you testing Scoutbees? yes/no: no
Are you testing Secure DX? yes/no: no
Are you testing an API URL? yes/no: no
****Real-Time DX (Hybrid Cloud) Testing****
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
URL –> validation result: OK
S3 –> Upload Validation: OK
****Agent Outbound Testing****
URL –> validation result: Validation Failed.This issue is related to Network communication.
URL –> validation result: OK
URL –> validation result: OK
****Testing Finished. Please close the program****
Hi @member this is not a new requirement, but already exists in 9.0
However, this URL only needs to be reachable if you want to use agent outbound communication
With 9.x, will the agent on the VDAs by default try to report directly out or do I need to configure something?
With 9.0, and agent outbound communication enabled, agents will try to reach out to cu-agents-cpa.controlup.com in order to retrieve a Personal Access Token (PAT) which is a new security mechanism to communicate with ControlUp Monitors
It’s not about reporting computer/session/process data to our backend directly. This is still done by the monitors
Continue reading and comment on the thread ‘Troubleshooting Network Communication Issues in ControlUp 9.0’. Not a member? Join Here!
Categories: All Archives, ControlUp Edge DX, ControlUp Real-Time DX, ControlUp Scoutbees, ControlUp Secure DX