---
title: "Debugging Lighthouse Scans"
description: "Debugging Lighthouse Scans for the Unlighthouse v1 beta."
canonical_url: "https://unlighthouse.dev/v1/guide/guides/debugging"
last_updated: "2026-10-03T08:07:15.591Z"
---

## Enable logs

```sh
pnpm exec unlighthouse --site https://example.com --debug
```

Debug logs show config resolution, route discovery, scan status, and audit failures.
Use `--debug=false` to override configured debug logging.

## Check discovery separately

Start with one explicit URL to distinguish discovery problems from audit problems:

```sh
pnpm exec unlighthouse-ci --site https://example.com --urls / --reporter json
```

For JavaScript-rendered navigation, supply a sitemap or explicit URLs.
The discovery crawler does not execute JavaScript.

## Check Chrome

The local auditor launches Chrome in headless mode.
Set `CHROME_PATH` when Chrome Launcher cannot find your installed browser.

```sh
CHROME_PATH=/usr/bin/google-chrome pnpm exec unlighthouse-ci --site https://example.com
```

`puppeteerOptions.headless`, `slowMo`, and page hooks do not control the v1 auditor.
See [Chrome Options](/guide/guides/puppeteer).

## Check authentication

Read [Authentication](/guide/guides/authentication) before testing protected routes.
Browser storage and audit headers do not authenticate the HTML discovery crawler.

## Report a failure

Include your Node.js version, package version, command, and relevant debug logs.
Remove credentials, tokens, cookies, and private URLs before sharing logs.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.