# Troubleshooting

Find the missing link between installation and received evidence.


## Nothing appears

1. Confirm the correct runtime entry initialized with the project's actual `pk_…` key.
2. Confirm `endpoint` is the API base URL, not the dashboard URL or `/ingest` path.
3. Confirm the runtime can reach that URL from the user's device or server.
4. Check consent, `enabled`, sampling, Browser SDK settings, and the selected environment/component filters.
5. Generate one safe test event, await `flush()`, and inspect `getDiagnostics()`.

## HTTP responses

| Result | What to inspect |
| --- | --- |
| Invalid origin | Allowed application/public origins and proxy configuration |
| 401 / 403 | Key type, revocation, project access, or expired agent credentials |
| 413 | Payload size; do not increase limits to hide an unbounded payload |
| 429 | Request-rate or monthly telemetry limits and Retry-After |
| 503 | Collector/limiter readiness and its database/Redis dependencies |

## Service waiting for traffic

A known service with no runtime calls has insufficient evidence. Exercise the real application path, instrument its runtime, or deliberately configure a lightweight active monitor. Repository detection is not a health check.

## No release or replay

Release metadata must be reported and match runtime tags. Replay needs local opt-in, project enablement, visitor consent, sampling eligibility, successful chunk delivery, and storage. Check those paths separately.

## Agent cannot connect a repository

CLI login authenticates to Everock. GitHub still needs the user's/App's permission for that repository. Re-run the initial GitHub authorization when access was revoked or the installation excludes that repository.

Do not paste API keys, cookie values, private URLs, or replay contents into a public bug report.