Improve error messages for common dev server issues#27
Merged
Conversation
Add actionable error messages for HTTPS-on-HTTP misconfigurations (TLS ClientHello detection), connection failures with status-specific guidance, tool extraction warnings with file paths, port conflict fallback messaging, and resource build-not-found errors with resource names.
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
1 participant
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
clientErrorhandlers across all three HTTP servers (MCP dev, production, sandbox) and log a clear message pointing to ngrok HTTPS misconfiguration instead of dumping raw bytes.sunpeak dev.Test plan
pnpm validatepasses (lint, typecheck, build, 247 unit tests, 22 e2e tests, docs, all examples, production server, inspect mode, dev server)