databuddy-analytics / databuddy-analytics/Databuddy

fix(demo): protected dashboard sections fail with a generic error in Live Demo

Open
#650 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
1.2k
Forks
216
Avg merge
14h 53m
Merged PRs (30d)
154

Description

Description

The public Live Demo exposes dashboard sections that are not accessible correctly for an unauthenticated visitor.

When opening the Live Demo and navigating to certain sections such as Audience, the page displays:

Something went wrong. Try again in a moment.

Checking the Network tab shows that the page sends a request to:

POST /v1/query

which returns:

401 Unauthorized

Since the Live Demo is publicly accessible and no login flow is presented before accessing these sections, this results in a broken and confusing demo experience.

Steps to reproduce

  1. Open https://databuddy.cc/demo
  2. Click Live Demo
  3. Navigate to Audience
  4. Observe the error message
  5. Open DevTools → Network
  6. The request to /v1/query returns 401 Unauthorized

Expected behavior

The Live Demo should either:

  • provide access to the supported demo dashboard sections without requiring the visitor to authenticate, or
  • clearly indicate that a section requires authentication instead of showing a generic error.

Actual behavior

The page sends a protected API request that returns 401 Unauthorized, and the UI only displays a generic:

Something went wrong. Try again in a moment.

Additional context

The Dashboard itself loads demo data successfully, but navigating to certain other dashboard sections results in the unauthorized request and generic error.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Live Demo entry point at /demo and reproduce the Audience navigation flow while inspecting POST /v1/query in the Network tab. Trace why protected sections are requested without authentication and determine whether supported sections should load demo data or clearly identify authentication requirements. Done means no generic error appears for unauthenticated visitors.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.