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

# Connection Problems

> Diagnose and fix connections that show as inactive or in error

## Overview

When a connection isn't reporting data or shows an `error` status, it's almost always a credential, URL or reachability issue. This page walks through the common causes for each platform. For general problems see [Common Issues](/troubleshooting/common-issues).

## Reading Connection Status

| Status     | What it usually means                                                            |
| ---------- | -------------------------------------------------------------------------------- |
| `inactive` | Newly created and not yet confirmed, or paused. Wait for the first check.        |
| `error`    | Checks are failing — bad credentials, wrong URL, or the platform is unreachable. |
| `active`   | Healthy and passing checks.                                                      |

<Tip>
  A connection created via API or dashboard starts `inactive` and becomes `active` after its first successful check. If it stays `inactive` for more than a few minutes, treat it like an `error`.
</Tip>

## n8n

<AccordionGroup>
  <Accordion title="Wrong base URL">
    * Use the full instance URL (e.g. `https://n8n.example.com`), not a workflow or webhook URL.
    * Make sure the URL is reachable from the public internet — a `localhost` or private-network address won't work.
  </Accordion>

  <Accordion title="Invalid or expired API key">
    * Regenerate the n8n API key and update the connection ([PUT /v1/connections/{id}](/api-reference/connections#update-a-connection) or the dashboard).
    * Confirm the key has the access n8n requires for the REST API.
  </Accordion>

  <Accordion title="Instance unreachable">
    * Check the instance is up and not behind a VPN, IP allowlist or firewall that blocks Opsmatic.
    * Verify TLS certificates are valid.
  </Accordion>
</AccordionGroup>

## Make.com

<AccordionGroup>
  <Accordion title="Invalid API token">
    * Recreate the Make.com API token and update the connection.
    * Confirm the token belongs to the right team.
  </Accordion>

  <Accordion title="Wrong region">
    * Make.com is region-specific. Ensure the connection's `region` matches your account's (e.g. `eu1`, `eu2`, `us1`).
  </Accordion>
</AccordionGroup>

## OpenClaw

<AccordionGroup>
  <Accordion title="No heartbeats / missed heartbeat">
    * Confirm the daemon is running and configured with the **ingest API key** generated when the connection was created.
    * The ingest key is a `usage-ingestion` key shown **once** — if it was lost, recreate the connection to get a new one.
    * A stopped daemon opens a `missed_heartbeat` incident. Restart it and the connection recovers on the next heartbeat.
  </Accordion>

  <Accordion title="Costs look wrong">
    * See [how costs are calculated](/connections/openclaw-setup#how-costs-are-calculated). Entries without a provider-reported cost are priced server-side.
  </Accordion>
</AccordionGroup>

## Verifying With the API

```bash theme={null}
# Check the connection's current status
curl -H "Authorization: Bearer ops_your_api_key" \
  https://api.opsmatic.com/v1/connections/conn_abc123

# See recent failed availability checks
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/availability?connection_id=conn_abc123&is_available=false"

# See any open incident for the connection
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/incidents?connection_id=conn_abc123"
```

## Still Stuck?

<Card title="Contact Support" icon="life-ring" href="/troubleshooting/support">
  If the connection still won't come up, reach out — include the connection ID and service type.
</Card>