# Connection Issues and Errors Code 0 with Dynatrace **URL:** \ **Category:** Open Q&A\ **Tags:** account-management, data-privacy-and-product-security, documentation, infrastructure-operations\ **Created:** [December 9, 2024, 9:56am UTC](https://community.dynatrace.com/t/connection-issues-and-errors-code-0-with-dynatrace/49255 "2024-12-09T09:56:05Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![TahirJanwari](https://avatars.discourse-cdn.com/v4/letter/t/a87d85/32.png) [@TahirJanwari](https://community.dynatrace.com/u/TahirJanwari)\ **Post date:** [December 9, 2024, 9:56am UTC](https://community.dynatrace.com/t/connection-issues-and-errors-code-0-with-dynatrace/49255/1 "2024-12-09T09:56:05Z")
Hello Community, We are encountering the following problems with the Dynatrace platform: 1. **Unstable Connection Alert** : Despite having a stable internet connection, we frequently see the message “Your connection is unstable.” 2. **Recurring Errors (Error Code: 0)**: The message “We have hit an error” with Error Code: 0 appears often, interrupting our ability to use the platform effectively. Does anyone have insights into why these issues, particularly Error Code 0, are occurring? ---
**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\ **Post date:** [December 17, 2024, 1:47pm UTC](https://community.dynatrace.com/t/connection-issues-and-errors-code-0-with-dynatrace/49255/2 "2024-12-17T13:47:09Z")
Hi [@TahirJanwari](https://community.dynatrace.com/user/74616) Regarding the highlighted concerns: - For the multi-node deployments, ensure the attached requirements are fulfilled: > **[Hardware requirements](https://docs.dynatrace.com/managed/managed-cluster/installation/managed-hardware-requirements)** > > Review the hardware sizing, storage, and multi-node cluster requirements before installing Dynatrace Managed on your infrastructure. ![2024-12-17_17h09_41.png](https://global.discourse-cdn.com/dynatrace/original/2X/f/fc99ad2942bfc6ab93dfd9f394b56af25773ea87.png) Ensure the accurate sizing for the cluster nodes to afford unexpected loads and extended monitoring requirements: - [Hardware requirements — Dynatrace Managed Docs](https://docs.dynatrace.com/managed/shortlink/managed-requirements) If the current situation is related to cloud deployments please verify the actual setup against the suggested or proposed Dynatrace recommendations: - [Hardware requirements for cloud deployments — Dynatrace Managed Docs](https://docs.dynatrace.com/managed/managed-cluster/installation/managed-hardware-requirements-for-clouds) **If the previously mentioned are properly addressed PFA factors for validation:** - [**DNS Resolution Problems** :](https://docs.dynatrace.com/managed/shortlink/managed-dns-setup) Regardless having a stable internet connection, there could be intermittent DNS issues causing the platform to report an “Unstable Connection.” - **Firewall/Proxy Interference** : Inaccurate configurations are blocking or slowing the connection between your device and Dynatrace servers. This could lead to instability and cause intermittent connection drops. - **Network Latency** : High latency, even with a stable internet connection, might be affecting communication with the Dynatrace servers, leading to connection instability warnings. - Ensure the attached ports are allowed between the cluster nodes: [Cluster node ports — Dynatrace Managed Docs](https://docs.dynatrace.com/managed/managed-cluster/installation/which-network-ports-does-dynatrace-server-use) - **Network Configuration** : Incorrect network configurations such as VPN, DNS, or subnet issues could cause intermittent connectivity issues or communication problems with the Dynatrace servers. - **Devices resources** that are used to access Dynatrace aren’t sufficient. **On Dynatrace side:** - Ensure the Solution components are up-to-date. - There is no issue with Dynatrace cluster nodes and [mission control](https://docs.dynatrace.com/managed/shortlink/managed-network-ports#outbound-to-mission-control) at least. - Ensure the communications between [OAs](https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/installation-and-operation/linux/installation/customize-oneagent-installation-on-linux#proxy) && [AGs](https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/configuration/set-up-proxy-authentication-for-activegate) and [AGs](https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/configuration/set-up-reverse-proxy-for-activegate) && Cluster nodes are stable either directly or through proxies or [Load balancers](https://docs.dynatrace.com/managed/shortlink/managed-load-balancer) - [Configuration properties and parameters of ActiveGate — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/configuration/configure-activegate#com-compuware-apm-webserver) - Ensure the platform isn’t overloaded due to direct monitoring traffic that hit the cluster directly so ensure the Network zones are configured accurately to ensure the seamless traffic reachability to Dynatrace cluster without affecting platform performance or stability. - As per the previous point ensure each [Network Zone](https://docs.dynatrace.com/managed/manage/network-zones) contains at least “2” AGs or “4” depending on the actual or excessive monitoring signals that go through it to the Cluster nodes. Customize Managed setup: - [Customize Managed Cluster installation — Dynatrace Managed Docs](https://docs.dynatrace.com/managed/shortlink/managed-custom-install) **A key factor to consider:** - Checking error and warning messages in each cluster node log files, it should point directly to the actual error causing the highlighted errors. Hoping it adds value. KR, Peter