Loading

AutoOps for ECE, ECK, or self-managed clusters troubleshooting

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 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 or use a different email address.

I need to uninstall Elastic Agent.
Refer to Uninstall Elastic Agent for instructions.
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 to reconnect. If not, explore additional resources or contact us.
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 or contact us.
Tip

If you're having issues connecting your cluster to AutoOps and sending metrics to Elastic Cloud, run the AutoOps Connectivity Check to test your configuration.

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.
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.
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.
Refer to Troubleshoot connected clusters not appearing with ECK installation to diagnose and resolve common issues.

Run the AutoOps Connectivity Check to test your system and diagnose any issues that might prevent you from connecting your cluster to AutoOps.

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.
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.
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. If the issue persists, contact Elastic support (for clusters on an Enterprise or Platinum license) or visit the community forums.
VERSION_MISMATCH Elasticsearch version is unsupported Upgrade your cluster to a supported version.
UNKNOWN_ERROR Installation failed Could not install Elastic Agent. Consult the troubleshooting guide or run the AutoOps Connectivity Check script to test your network settings. If the issue persists, contact Elastic support (for clusters on an Enterprise or Platinum license) or visit the community forums.
x509 Certificate signed by unknown authority Elastic Agent couldn't connect. SSL certificate signed by unknown authority.