# Fix Kubernetes ActiveGate Errors in Dynatrace Deployments

**URL:** <https://community.dynatrace.com/t/fix-kubernetes-activegate-errors-in-dynatrace-deployments/40266>\
**Category:** Container platforms\
**Tags:** linux, cloud-foundry, container, kubernetes\
**Created:** [June 19, 2023, 8:33am UTC](https://community.dynatrace.com/t/fix-kubernetes-activegate-errors-in-dynatrace-deployments/40266 "2023-06-19T08:33:59Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![radek\_jasinski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radek_jasinski/32/10432_2.png) [@radek\_jasinski](https://community.dynatrace.com/u/radek_jasinski)\
**Post date:** [June 21, 2023, 2:40pm UTC](https://community.dynatrace.com/t/fix-kubernetes-activegate-errors-in-dynatrace-deployments/40266/9 "2023-06-21T14:40:53Z")

</div>

No, based on the log you have issues with the connection between ActiveGate and your Dynatrace cluster. You should to check this part of your system.

Maybe another good way is a use proxy for AG: [Proxy for ActiveGate — Dynatrace Docs](https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-activegate/configuration/set-up-proxy-authentication-for-activegate)

---

_[View the full topic](https://community.dynatrace.com/t/fix-kubernetes-activegate-errors-in-dynatrace-deployments/40266)._
