> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting by Symptom

> Start from what you see - a crash-looping pod, a failed deploy, an offline cluster, a pending certificate, a missing pipeline run - and go to the page that fixes it.

Find the row that matches what you see and follow its link. For the general order of checks on a cluster that misbehaves, read [Troubleshoot a Cluster](https://docs.ankra.ai/guides/troubleshoot-a-cluster.md) first.

## By symptom

| You see | Where it shows | Go to |
| - | - | - |
| A pod is crash-looping | **Health → Pods** counts it under crash-looping; the pod's **Restarts** keep rising | [Troubleshoot a Cluster → Read what the containers printed](https://docs.ankra.ai/guides/troubleshoot-a-cluster.md#3-read-what-the-containers-printed): read **Previous instance** on the pod's **Logs** tab, then [Logs](https://docs.ankra.ai/platform/logs.md) |
| A pod stays Pending | **Health → Pods** counts it under pending; the pod's phase reads Pending | [Troubleshoot a Cluster → Find the object in Kubernetes](https://docs.ankra.ai/guides/troubleshoot-a-cluster.md#2-find-the-object-in-kubernetes): the pod's **Events** say why it was not scheduled. When no node has room, add nodes in [Cluster Nodes](https://docs.ankra.ai/platform/cluster-nodes.md) or turn on [Cluster Autoscaling](https://docs.ankra.ai/guides/cluster-autoscaling.md) |
| A deploy failed | The cluster's **Technical details → Operations** lists a failed operation | [Find out why a deploy failed and retry it](https://docs.ankra.ai/platform/operations.md) |
| The cluster is offline | The cluster shows **Offline**; **Health** says `The cluster agent is offline. These are the last reported readings.` | [Ankra Agent → Troubleshooting](https://docs.ankra.ai/concepts/cluster-agent.md#troubleshooting), and [what still works meanwhile](https://docs.ankra.ai/guides/troubleshoot-a-cluster.md#when-the-agent-is-offline) |
| A cluster's health check is not healthy | The cluster's **Health** page shows a check or a score that is not healthy | [Read a cluster's overview and health → Go from a check that is not healthy](https://docs.ankra.ai/platform/cluster-overview-and-health.md#4-go-from-a-check-that-is-not-healthy) |
| A hostname has no certificate, or does not resolve | The certificate stays pending; the Ingress host does not answer | [Use Your Own Domain → What can go wrong](https://docs.ankra.ai/guides/use-your-own-domain.md#what-can-go-wrong) |
| A push or pull request made no pipeline run | No `Ankra pipeline` check on the commit, or a check that says why nothing ran | [Ankra CI Troubleshooting](https://docs.ankra.ai/guides/ankra-ci-troubleshooting.md#a-push-or-pull-request-started-no-run) |
| The bill went up | The invoice or the usage report is higher than last period | [Usage](https://docs.ankra.ai/platform/usage.md) for which meter grew and on which cluster, [Cloud Cost](https://docs.ankra.ai/platform/cloud-cost.md) for each cluster's spend, [Cost Budgets and the Autopilot](https://docs.ankra.ai/guides/cost-budgets-and-autopilot.md) to cap it |
| A log search finds nothing older than the containers keep | **Cluster logs → History** offers to set up a log store | [Ankra Hosted Logs](https://docs.ankra.ai/guides/hosted-logs.md), or connect a [log source](https://docs.ankra.ai/integrations/log-sources.md) |
| No shell in the container | The **Exec** tab connects and the shell exits, or the image is distroless | [Debug Pods](https://docs.ankra.ai/platform/debug-pods.md) |
| A Secret's values read `[protected]` | The Secret's **YAML** tab | [Kubernetes Resources → Secrets](https://docs.ankra.ai/platform/kubernetes-insights.md#secrets) |

## By message

Messages as the product shows them, with the page that explains each.

| Message | Where | Explained on |
| - | - | - |
| `The cluster agent is offline. These are the last reported readings.` | Cluster **Health** | [Troubleshoot a Cluster](https://docs.ankra.ai/guides/troubleshoot-a-cluster.md#when-the-agent-is-offline) |
| `The cluster is offline. These are previously recorded resources.` | Kubernetes resource lists | [Kubernetes Resources](https://docs.ankra.ai/platform/kubernetes-insights.md#resource-lists) |
| `The cluster agent is offline, so no pods are reported.` | Pods list | [Troubleshoot a Cluster](https://docs.ankra.ai/guides/troubleshoot-a-cluster.md#when-the-agent-is-offline) |
| `This object is managed. Change its source of truth.` | **Review resource actions** | [Kubernetes Resources → Change a resource](https://docs.ankra.ai/platform/kubernetes-insights.md#change-a-resource) |
| `Your role cannot perform this action.` | **Review resource actions** | [Kubernetes Resources → Change a resource](https://docs.ankra.ai/platform/kubernetes-insights.md#change-a-resource) |
| `Your role cannot read container logs on this cluster.` | A pod's **Logs** tab | [Logs](https://docs.ankra.ai/platform/logs.md#what-can-go-wrong) |
| `Live logs need the cluster agent.` | **Cluster logs → Live** | [Logs](https://docs.ankra.ai/platform/logs.md#what-can-go-wrong) |
| `Ankra hosted logs are on, but no line has arrived from this cluster.` | **Cluster logs → History** | [Logs](https://docs.ankra.ai/platform/logs.md#what-can-go-wrong) |
| `The log store could not confirm these lines are this cluster's.` | **Cluster logs → History** | [Log Sources → Sharing one log store between clusters](https://docs.ankra.ai/integrations/log-sources.md#sharing-one-log-store-between-clusters) |
| `This search could not be run.` | **Cluster logs → History** | [Logs](https://docs.ankra.ai/platform/logs.md#what-can-go-wrong) |
| `This cluster's agent cannot send logs to Ankra yet.` | An application's **Logs → History** | [Ankra Hosted Logs → What History tells you](https://docs.ankra.ai/guides/hosted-logs.md#what-history-tells-you) |
| `Connecting a log store of your own is not available` | **Settings → Integrations → Log store** | [Log Sources → What can go wrong](https://docs.ankra.ai/integrations/log-sources.md#what-can-go-wrong) |
| `You need kubernetes.exec permission on this cluster.` | A pod's **Exec** tab | [Pod Terminal → Troubleshooting](https://docs.ankra.ai/platform/pod-terminal.md#troubleshooting) |
| `The terminal did not connect. Check the agent and try again.` | A pod's **Exec** tab | [Pod Terminal → Troubleshooting](https://docs.ankra.ai/platform/pod-terminal.md#troubleshooting) |
| `AGENT_OUTDATED` | `ankra cluster debug create` | [Debug Pods → Requirements](https://docs.ankra.ai/platform/debug-pods.md#requirements) |
| `No trigger this pipeline declares matches this event, so there is nothing to run.` | The `Ankra pipeline` check | [Ankra CI Troubleshooting](https://docs.ankra.ai/guides/ankra-ci-troubleshooting.md) |
| `Awaiting authority approval` | The `Ankra pipeline` check | [Ankra CI Troubleshooting](https://docs.ankra.ai/guides/ankra-ci-troubleshooting.md) |

## Still stuck

Press `⌘J` (`Ctrl+J`) on the page where you see the problem and ask [Ask Ankra](https://docs.ankra.ai/platform/ai-assistant.md) about it, or [contact support](https://docs.ankra.ai/platform/support.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.