Dashboard reverse-proxy subpath and base-path URL handling
NousResearch/hermes-agent · cluster 25547 · dashboard
Data as of
Nothing open on GitHub. Fix merged in #27550. Check it covers your case.
The short answer
- Known?
- Yes. 9 related items grouped here, 3 issues already closed.
- Fix event
- A fix was merged to main in PR #27550. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #133903. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address problems with the dashboard when served under a URL prefix via reverse proxies, covering login page URLs, WebSocket paths, auth routes, and X-Forwarded-Prefix header support.
Open issues0
Open PRs0
Fixes on record
-
#27550 Batch salvage group 6 (final): streaming timeout config + docker exit-75 restart + dashboard loopback/base-path
files:
agent/chat_completion_helpers.py,gateway/run.py,hermes_cli/web_server.py,scripts/release.py,web/src/components/ChatSidebar.tsx,web/src/lib/gatewayClient.ts,web/src/pages/ChatPage.tsx -
#133903 fix(dashboard): auth URLs honour X-Forwarded-Prefix behind reverse-proxy subpath
files:
hermes_cli/dashboard_auth/login_page.py,hermes_cli/dashboard_auth/middleware.py,hermes_cli/dashboard_auth/routes.py,tests/hermes_cli/test_dashboard_auth_401_reauth.py,tests/hermes_cli/test_dashboard_auth_prefix.py,web/src/lib/api.ts
4 PRs closed without merging
From the close comments: merged via another change 2 · duplicate 1 · superseded by another PR 1
-
#25764 fix(dashboard): respect HERMES_BASE_PATH in WebSocket URLs (#25547) · merged via another change →
#27550,#25547 - #48625 fix(dashboard): respect X-Forwarded-Prefix in server-rendered login page · merged via another change
-
#48698 fix(dashboard): prefix login page URLs for reverse proxies (#48623) · duplicate →
#33311,#48625 - #50931 fix(dashboard): use relative auth paths for reverse-proxy subpath compatibility (#50889) · superseded by another PR
Closed issues · 3
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.21: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab