LoggerMan
Open dashboard

Or browse the quick start

Troubleshooting

Symptoms, likely causes, and fixes for common LoggerMan issues.

Logs never appear in the dashboard

  • Confirm the active project in the sidebar switcher matches the projectId in your app.
  • Verify LOGGERMAN_BASE_URL is reachable from the machine sending logs (tunnel URL, not wrong port).
  • Check the token matches Settings → API keys (regenerating invalidates old tokens).
  • Send a test log from Integration — if that works, the issue is in your app env or network, not LoggerMan core.
  • Inspect browser or server console for SDK errors (status 401/403/400).

CORS blocked in the browser (localhost or another site)

Calling the ingest API with fetch from a web page on a different origin (for example Live Server on http://127.0.0.1:5500) triggers a browser preflight. If you see “No Access-Control-Allow-Originheader”, the deployment may be missing CORS support — ingest routes on LoggerMan reflect your page's Origin and answer OPTIONS with 204.

curl and server-side scripts are not subject to CORS; only browser JavaScript is. For production apps, prefer logging from your backend or the Node SDK rather than exposing the project token in client-side HTML.

401 or 403 from the API

401 — missing or malformed Authorization header. Ensure Bearer prefix and no extra quotes.

403 — token does not authorize this project ID. Double-check ID and token pair; regenerate if unsure.

Dashboard stuck on “Loading projects…”

Usually a network or sign-in issue — ad blockers, strict firewalls, or an expired session can block the dashboard from loading your projects. Sign out and back in, try another browser or network, then refresh.

If loading takes longer than a few seconds, LoggerMan shows an error instead of spinning forever — use that message as a starting point.

Cannot add a team member

The email must belong to an existing LoggerMan user. Ask them to sign up first, then retry. Typos and plus-address aliases must match exactly.

Test log works but app logs do not

  • Server vs client: tokens must only run server-side.
  • Wrong env file loaded (`.env` vs `.env.local` in Next.js).
  • Fire-and-forget without await on serverless — request may terminate early.

Invalid JSON or validation errors (400)

message is required. type and criticality must be allowed enum values. metadata must be a plain object, not a string or array.

Still stuck?

Re-read the Quick start and API reference. Compare your request to a working Integration test log. If the dashboard itself will not load, contact support with your account email and what you already tried from this page.