https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241193#M2287 <P>Thanks for the recommendation here. We customized the name of our secret. There was no secret by the name of dynakube. I went ahead and deleted the dynakube, the secret, and any leftover resources in the namespace then redeployed. All is good now.</P> Wed, 27 Mar 2024 11:49:07 GMT sivart_89 2024-03-27T11:49:07Z https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241139#M2282 <P>I'm suddenly seeing the error below and the operator pod and 2 AG pods are not functional, with the error being in the AG pod. We are using operator version 0.12.1 and I have decoded the secret and confirmed the apiToken does have the <STRONG>'Create ActiveGate tokens'</STRONG> scope. I even tried deleting the secret and creating it back with the tokens. What else can I look at here? I prefer to not wipe everything out and start fresh (delete the dynakube crd, reapplying yaml files, etc).</P><P><BR />2024-03-26 21:22:10 UTC WARNING [&lt;ltr71653&gt;] [&lt;collector.core&gt;, InitialCollectorSetupPoller] Initial collector setup received with error:REQUEST_REJECTED, reason=Invalid ActiveGate Token source=ANY_SERVER 0x0000000000000000 [Suppressing further messages for 1 hour]</P> Tue, 26 Mar 2024 21:34:39 GMT https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241139#M2282 sivart_89 2024-03-26T21:34:39Z https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241140#M2283 <P>Hello, I recommend you to check <A href="https://community.dynatrace.com/t5/Container-platforms/OpenShift-ActiveGate-token-missing/m-p/213400" target="_blank" rel="noopener">this</A> response from <a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/22017">@Babar_Qayyum</a>&nbsp;</P> Wed, 27 Mar 2024 21:25:20 GMT https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241140#M2283 DanielS 2024-03-27T21:25:20Z https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241143#M2284 <P>What response are you referring to? I don't see it linked here. I've also tried looking up their profile and viewing some recent posts but did not find anything relevant.</P> Tue, 26 Mar 2024 22:03:07 GMT https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241143#M2284 sivart_89 2024-03-26T22:03:07Z https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241151#M2285 <P>I have seen this kind of error when there are a couple of secrets, one dynakube secret and one with a custom name.</P><P>Please check it.</P> Wed, 27 Mar 2024 07:34:32 GMT https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241151#M2285 PacoPorro 2024-03-27T07:34:32Z https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241193#M2287 <P>Thanks for the recommendation here. We customized the name of our secret. There was no secret by the name of dynakube. I went ahead and deleted the dynakube, the secret, and any leftover resources in the namespace then redeployed. All is good now.</P> Wed, 27 Mar 2024 11:49:07 GMT https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241193#M2287 sivart_89 2024-03-27T11:49:07Z https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241272#M2292 <P>Sorry, link updated.</P> Wed, 27 Mar 2024 21:25:39 GMT https://community.dynatrace.com/t5/Container-platforms/Invalid-ActiveGate-Token-for-Container-AG-in-Kubernetes/m-p/241272#M2292 DanielS 2024-03-27T21:25:39Z