Understanding the “Failed to create PAT” Error Message for Outbound Communications in ControlUp

Users discuss the "Failed to create PAT" error message, with some providing background information that the PAT is a unique JWT for each agent machine and serves as a security mechanism to authenticate agents against monitors. Some users suggest discussing this further in private before summarizing in the thread.

Read the entire ‘Understanding the "Failed to create PAT" Error Message for Outbound Communications in ControlUp’ thread below:

What does the message "Failed to create PAT" when attempting to enable outbound communications mean? This is on 9.0.0.1680

Full message:

Connection loop started but connection has failed. Restarting connection loop => Set Registration Key => Starting connection => Discovering available brokers => Connection loop started but connection has failed. Delaying before retry.

Reason: Failed to create PAT

Hi @member, let’s have a private chat on this. It makes sense to summarize our findings in this thread later on, sounds OK?

Regarding the "Failed to create PAT" error message, here some background:

The PAT is a JWT which is unique for each agent machine. The PAT is obtained from our backend (cu-agents.cpa.controlup.com) to which either the agent itself (online brokering flow) or monitors (offline brokering flow) need to have access to

The PAT is a security mechanism that authenticates the agent against the monitors. Whenever the agents starts to stream computer data to the monitor, it sends the PAT in each request

In @member’s case, the agents are not allowed to contact our backend, so we had to switch to the Offline Brokering flow.

Continue reading and comment on the thread ‘Understanding the “Failed to create PAT” Error Message for Outbound Communications in ControlUp’.  Not a member? Join Here!