fix: surface gateway error messages in Settings test connection#54
Merged
shanselman merged 1 commit intomasterfrom Mar 17, 2026
Merged
fix: surface gateway error messages in Settings test connection#54shanselman merged 1 commit intomasterfrom
shanselman merged 1 commit intomasterfrom
Conversation
The TestLogger was silently swallowing all gateway client errors, so connection failures showed a generic 'Connection failed' message. Now captures the last error/warning and displays the actual gateway message (e.g. 'origin not allowed') in the status label. Also keeps verbose logging to Debug.WriteLine for dbgview-mcp diagnostics.
shanselman
force-pushed
the
fix/verbose-test-connection-errors
branch
from
2f3d49e to
eea7a92
Compare
4 tasks
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.
The Settings Test button was showing a generic 'Connection failed' when the gateway rejected the connection. The actual error (e.g.
origin not allowed) was swallowed by the silent TestLogger.Now the TestLogger captures errors and the status label shows the real gateway message:
Before:
❌ Connection failedAfter:
❌ origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)Also adds verbose debug output from the test client for dbgview-mcp diagnostics.