---
title: AutoOps for ECE, ECK, or self-managed clusters troubleshooting
description: Learn about issues that might come up when connecting your clusters and using AutoOps. Use this guide to troubleshoot any issues you may encounter. I’m...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud on Kubernetes
applies_to:
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# AutoOps for ECE, ECK, or self-managed clusters troubleshooting
Learn about issues that might come up when connecting your clusters and using AutoOps.

## Troubleshoot issues

Use this guide to troubleshoot any issues you may encounter.
- [I’m trying to create a Cloud organization, but I’m already part of a different one.](#single-cloud-org)
- [I need to uninstall Elastic Agent.](#unistall-agent)
- [My cluster was disconnected from Elastic Cloud and I want to reconnect it.](#disconnected-cluster)
- [After running the installation command, I can't move on to the next steps.](#next-steps)
- [My organization's firewall might be preventing Elastic Agent from collecting and sending metrics.](#firewall)
- [Elastic Agent is failing to connect because it doesn't recognize my SSL certificate.](#custom-cert)
- [I went through the wizard with Elastic Cloud on Kubernetes (ECK) as my installation method, but I can't view any connected clusters in my account.](#eck-no-clusters) <applies-to>Elastic Cloud on Kubernetes: Generally available since 3.3</applies-to>
- [My `AutoOpsAgentPolicy` resource entered the `Invalid` phase after a license change.](#invalid-phase-license-change) <applies-to>Elastic Cloud on Kubernetes: Generally available since 3.3</applies-to>

<definitions>
  <definition term="I’m trying to create a Cloud organization, but I’m already part of a different one.">
    Users can only belong to one Elastic Cloud organization at a time. If you want to create or join another organization, you must [leave the previous one](/elastic/docs-content/pull/5399/cloud-account/join-or-leave-an-organization#ec-leave-organization) or use a different email address.
  </definition>
  <definition term="I need to uninstall Elastic Agent.">
    Refer to [Uninstall Elastic Agent](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/solutions/security/configure-elastic-defend/uninstall-elastic-agent) for instructions.
  </definition>
  <definition term="My cluster was disconnected from Elastic Cloud and I want to reconnect it.">
    If the cluster was disconnected by one of the users in your Cloud organization, you can repeat the [installation process](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops) to reconnect. If not, explore [additional resources](/elastic/docs-content/pull/5399/troubleshoot#troubleshoot-additional-resources) or [contact us](/elastic/docs-content/pull/5399/troubleshoot#contact-us).
  </definition>
  <definition term="After running the installation command, I can't move on to the next steps.">
    If an error appears on the screen, follow the suggestion in the error message and try to run the command again. If the issue is not resolved, explore [additional resources](/elastic/docs-content/pull/5399/troubleshoot#troubleshoot-additional-resources) or [contact us](/elastic/docs-content/pull/5399/troubleshoot#contact-us).
  </definition>
</definitions>

<tip>
  If you're having issues connecting your cluster to AutoOps and sending metrics to Elastic Cloud, run the [AutoOps Connectivity Check](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-connectivity-check) to test your configuration.
</tip>

<definitions>
  <definition term="My organization's firewall might be preventing Elastic Agent from collecting and sending metrics.">
    If you're having issues with connecting your cluster to AutoOps and you suspect that a firewall may be the reason, refer to [Troubleshoot firewalls blocking Elastic Agent](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-firewalls).
  </definition>
  <definition term="Elastic Agent is failing to connect because it doesn't recognize my SSL certificate.">
    If Elastic Agent is failing to connect your cluster to AutoOps because it doesn't recognize your SSL certificate, refer to [Configure AutoOps Elastic Agent with a custom SSL certificate](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-sm-custom-certification).
  </definition>
  <definition term="I went through the wizard with Elastic Cloud on Kubernetes (ECK) as my installation method, but I can't view any connected clusters in my account. Elastic Cloud on Kubernetes: Generally available since 3.3">
    Refer to [Troubleshoot connected clusters not appearing with ECK installation](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters) to diagnose and resolve common issues.
  </definition>
  <definition term="My AutoOpsAgentPolicy resource entered the Invalid phase after a license change. Elastic Cloud on Kubernetes: Generally available since 3.3">
    The [minimum required Elastic Agent version](/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops#prerequisites) for the ECK installation method depends on your license type. Enterprise licenses require agent versions 9.2.1 and later, and Basic licenses require versions 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter the `Invalid` phase.
    To resolve this issue, upgrade Elastic Agent.
  </definition>
</definitions>


## Run the AutoOps Connectivity Check

Run the [AutoOps Connectivity Check](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-connectivity-check) to test your system and diagnose any issues that might prevent you from connecting your cluster to AutoOps.

## Potential errors

The following table shows the errors you might encounter if something goes wrong while you set up and use AutoOps in your clusters.

| Error code                  | Error message                             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
|-----------------------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `HTTP_401`                  | Authentication failed                     | Connection denied because of an authentication error. Run the AutoOps Connectivity Check script to diagnose the issue. [Learn more](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-connectivity-check).                                                                                                                                                                                                                                                         |
| `HTTP_502`                  | Server error                              | Received an invalid response from the server. There may be an issue with the server status or network configuration. Run the AutoOps Connectivity Check script to diagnose the issue. [Learn more](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-connectivity-check).                                                                                                                                                                                          |
| `HTTP_503`                  | Server unavailable                        | Invalid or corrupt response received from the server. The server acting as a proxy may be busy or undergoing scheduled maintenance. If the issue persists, check the cluster's health and resource usage.                                                                                                                                                                                                                                                                                                                 |
| `HTTP_504`                  | Request timed out                         | Did not receive a response from the cluster within the expected time frame. Check the cluster's performance or consider changing your connection timeout settings.                                                                                                                                                                                                                                                                                                                                                        |
| `CLUSTER_ALREADY_CONNECTED` | Cluster connected to another account      | This cluster is already connected to another Elastic Cloud organization. Disconnect it and then try again.                                                                                                                                                                                                                                                                                                                                                                                                                |
| `CLUSTER_NOT_READY`         | Elasticsearch cluster is still connecting | Your Elasticsearch cluster is not yet ready to connect. Wait a few moments for it to finish starting up and then try again.                                                                                                                                                                                                                                                                                                                                                                                               |
| `HTTP_0`                    | Connection error                          | Elastic Agent couldn't connect to the cluster. Run the AutoOps Connectivity Check script to diagnose the issue. [Learn more](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/autoops-connectivity-check). If the issue persists, contact [Elastic support](https://support.elastic.co/) (for clusters on an Enterprise or Platinum license) or visit the [community forums](https://discuss.elastic.co/c/elastic-stack/monitoring/103).                                  |
| `VERSION_MISMATCH`          | Elasticsearch version is unsupported      | Upgrade your cluster to a [supported version](https://www.elastic.co/support/eol).                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| `UNKNOWN_ERROR`             | Installation failed                       | Could not install Elastic Agent. Consult the [troubleshooting guide](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5399/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting) or run the AutoOps Connectivity Check script to test your network settings. If the issue persists, contact [Elastic support](https://support.elastic.co/) (for clusters on an Enterprise or Platinum license) or visit the [community forums](https://discuss.elastic.co/c/elastic-stack/monitoring/103). |
| `x509`                      | Certificate signed by unknown authority   | Elastic Agent couldn't connect. SSL certificate signed by unknown authority.                                                                                                                                                                                                                                                                                                                                                                                                                                              |