docs: add Chrome 142+ Private Network Access troubleshooting #1559
Conversation
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
Add troubleshooting section for Chrome 142+ blocking localhost connections due to Private Network Access (PNA) enforcement. Includes solution to allow local network access in Chrome settings and additional troubleshooting steps.
Contributor
|
Mintlify preview ID generated: preview-docsch-1763715230-b3b7ac8 |
katmayb
approved these changes
Nov 21, 2025
Contributor
katmayb
left a comment
katmayb
left a comment
There was a problem hiding this comment.
lgtm from a docs point of view, just style nits and a couple of links you could add.
Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
Contributor
|
Mintlify preview ID generated: preview-docsch-1763754907-1e81f0c |
Contributor
Author
|
thanks @katmayb! applied suggested changes. |
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.
Description
Adds troubleshooting documentation for Chrome 142+ blocking localhost connections to LangSmith Studio.
Problem
Starting with Chrome version 142, users are experiencing "Failed to initialize Studio" errors when trying to connect LangSmith Studio to their local development server via
langgraph dev. This is due to Chrome's full enforcement of the Private Network Access (PNA) specification, which blocks HTTPS sites from accessing HTTP localhost servers by default.Changes
src/langsmith/troubleshooting-studio.mdxTesting
References