Agent Client Collector not connecting correctly

Ansly21
Tera Contributor

8 hours ago

Hello everyone, we have an issue in which Agent Client Collector is connecting to the wrong instance.

To give a background, we have three instances: Dev, Test, and Prod. We have first started testing ACC in our DEV environment, so we enabled the WebSocket and generated an API-Key.

 

So, we first enabled the WebSocket for a MID servers, let's name it MID A. Few agents have already connected successfully and is reporting in our DEV instance. We wanted to migrate it to our Test instance, so first we have disabled the WebSocket for MID A in Dev instance and enabled MID A WebSocket in Test instance. Somehow, it was able to report in our Test instance, even though we haven't configured the api-key. (Note: IP address and port is the same + API key is uniquely generated in each instance and applies to all MID servers)

 

We are thinking on how it was able to connect, even if the api-key is wrongly configured.

Previously, we were able to repoint our agents with by changing the api-key.

Now, when we do that, it somehow goes to our Prod and Test instances randomly.

Also, when we performed the "acc self-test,"  we saw that the authentication is failing, but in the logs, it is showing the "successfully connected..."

Has anyone encountered the same issue of repointing agents to a different instance? If so, any help is appreciated. Thanks!

 

Regards,

Ansly

Labels:
0 Helpfuls
  • 81 Views
1 REPLY 1

ayushraj7012933
Mega Guru

6 hours ago

Hi @Ansly21 

I faced something similar a while back. In my case, I first checked whether the ACC agent was using the correct instance URL and API key. I also made sure the MID Server was connected only to the intended instance.

If your Dev, Test, and Prod instances are cloned, it's worth generating a new API key and re-enrolling the agent. That helped rule out any old configuration.

Also, seeing "Successfully connected" in the logs doesn't always mean the authentication was successful. It just means the WebSocket connection was established. Since the ACC self-test is showing authentication failed, I'd focus on the agent configuration and authentication rather than network connectivity.

Just curious, are your Dev, Test, and Prod instances cloned? And are you using the same MID Server across all three environments?



 

0 Helpfuls