hermes - 💡(How to fix) Fix [BUG] Analytics dashboard API returns 401 Unauthorized after v0.13.0 update [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#25275Fetched 2026-05-14 03:47:38
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×4commented ×1

Root Cause

This is the same auth regression pattern as Kanban (#24186) — the dashboard's API routes are rejecting requests that should be authenticated via the session token, but the auth check is failing.

Confirmed:

curl http://127.0.0.1:9000/api/analytics/sessions?limit=5
→ {"detail":"Unauthorized"}

Code Example

curl http://127.0.0.1:9000/api/analytics/sessions?limit=5
{"detail":"Unauthorized"}
RAW_BUFFERClick to expand / collapse

Problem

After v0.13.0 update, the /analytics dashboard page returns 401 Unauthorized for its API endpoints. The page itself loads but all data requests fail with {"detail":"Unauthorized"}.

Steps to Reproduce

  1. Open http://127.0.0.1:9000/analytics in browser
  2. Open DevTools Network tab — observe all /api/analytics/* requests return 401 Unauthorized

Root Cause

This is the same auth regression pattern as Kanban (#24186) — the dashboard's API routes are rejecting requests that should be authenticated via the session token, but the auth check is failing.

Confirmed:

curl http://127.0.0.1:9000/api/analytics/sessions?limit=5
→ {"detail":"Unauthorized"}

Expected Behavior

Analytics data should load for authenticated dashboard sessions, same as it did before the update.

Impact

  • Analytics dashboard is completely non-functional
  • Same root cause as Kanban 401 Unauthorized — likely a shared auth middleware regression

Related Issues

This is likely the same auth regression as #24186 (Kanban 401 Unauthorized). Both the Kanban plugin API and Analytics API are returning 401 after the update, suggesting a systemic auth middleware issue in the dashboard.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING