fix(cockpit): align all proxy configs to port 8123 + E2E verification#35
Merged
Conversation
blove
added a commit
that referenced
this pull request
Apr 7, 2026
* docs: add cockpit E2E verification plan * fix(cockpit): align all proxy configs to port 8123 (serve script hardcodes this port)
blove
added a commit
that referenced
this pull request
Apr 7, 2026
* docs: add cockpit E2E verification plan * fix(cockpit): align all proxy configs to port 8123 (serve script hardcodes this port)
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
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
Critical fix: All 13 non-streaming cockpit examples had proxy configs pointing to wrong ports (8124-8145). The serve script hardcodes
--port 8123for all LangGraph backends, but each proxy.conf.json expected a unique port. Only the streaming example (port 8123) worked.Fix: Updated all 14 proxy.conf.json files to target port 8123.
E2E Verification Results (Chrome Extension)
Known issues (cosmetic, not blocking):
<chat>host)interrupt()APITest plan