fix(dashboard): allow websocket clients for public binds#32614
Closed
cbjerg wants to merge 1 commit into
Closed
Conversation
This was referenced May 26, 2026
Open
Open
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
A recent hardening change made dashboard WebSockets loopback-only. That is correct for the default localhost bind, but it breaks the existing LAN dashboard use case when the operator explicitly starts the dashboard with e.g.
hermes dashboard --host 0.0.0.0 --insecure --tui: the HTTP UI loads remotely, but/api/events,/api/ws, and/api/ptyare rejected, causing the chat sidebar to showevents feed disconnected.Test Plan
python -m pytest tests/hermes_cli/test_web_server_host_header.py -q/api/eventsconnects from127.0.0.1:9119and LAN addresses after restarting the dashboard