---
title: "Troubleshoot private probes | Grafana Cloud documentation"
description: "Troubleshoot Synthetic Monitoring private probes by checking agent versions, authentication, API connectivity, logs, and metrics, and find community or account support."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Troubleshoot private probes

If a Synthetic Monitoring private probe isn’t connecting or working as expected, use the following checks to review the agent’s configuration, logs, and metrics. For failures reported by a check, refer to [Troubleshoot a failing check](/docs/grafana-cloud/observe-and-act/testing/synthetic-monitoring/analyze-results/troubleshoot-checks/).

1. Check the probe version using the `-version` flag and make sure you are running a supported version.
2. Make sure the probe has a valid probe access token.
3. Make sure the probe can connect to the Synthetic Monitoring API server.
4. Run the Synthetic Monitoring Agent in debug mode with the `-debug` and `-verbose` flags and check for errors in the logs.
5. Check the Synthetic Monitoring Agent metrics. The default address for Synthetic Monitoring Agent Prometheus metrics is `localhost:4050/metrics`.

If you are still facing issues with Private Probes, ask for help in the [community forum](https://community.grafana.com/). Refer to [Account types and support available for Grafana Cloud users](/docs/grafana-cloud/account-management/support/#account-types-and-support-available-for-grafana-cloud-users) for more information.