CDP Proxy fails to connect in WSL2: missing UUID in WebSocket path

[pine2D]

Environment

• OS: WSL2 (Ubuntu) connecting to Chrome on Windows host
• Chrome: 146.0.7680.178 (Windows)
• Node.js: v24.14.1
• web-access: 2.4.2
• Chrome launch: --remote-debugging-port=9222 --user-data-dir=D:\ChromeDebugProfile

Problem

CDP Proxy repeatedly fails with 连接错误: 连接失败 when running in WSL2.

Root cause: In WSL2, discoverChromePort() in cdp-proxy.mjs cannot find the DevToolsActivePort file because:

1. The Linux paths (~/.config/google-chrome/DevToolsActivePort) don't exist — Chrome runs on Windows
2. The win32 paths aren't checked because os.platform() returns linux in WSL

So it falls through to port scanning, which finds port 9222 but returns { port, wsPath: null }. Then getWebSocketUrl() builds ws://127.0.0.1:9222/devtools/browser without a UUID.

Modern Chrome (tested on 146) rejects WebSocket connections without the browser UUID in the path — resulting in a 1006 close code.

Reproduction

# In WSL2, with Chrome remote debugging on Windows:

# This fails (no UUID):
node -e "const ws = new WebSocket('ws://127.0.0.1:9222/devtools/browser'); ws.onerror = e => console.log('FAIL', e.type); ws.onclose = e => console.log('code', e.code)"
# → FAIL error, code 1006

# This works (with UUID):
node -e "fetch('http://127.0.0.1:9222/json/version').then(r=>r.json()).then(j=>{const ws = new WebSocket(j.webSocketDebuggerUrl); ws.onopen = () => console.log('OK')})"
# → OK

Suggested Fix

After port scanning succeeds, fetch the UUID via HTTP API before returning:

// In discoverChromePort(), the port scanning fallback section:
for (const port of commonPorts) {
    const ok = await checkPort(port);
    if (ok) {
      console.log(`[CDP Proxy] 扫描发现 Chrome 调试端口: ${port}`);
      // Fetch UUID-bearing wsPath from HTTP API (required by modern Chrome)
      let wsPath = null;
      try {
        const resp = await fetch(`http://127.0.0.1:${port}/json/version`);
        const info = await resp.json();
        if (info.webSocketDebuggerUrl) {
          const url = new URL(info.webSocketDebuggerUrl);
          wsPath = url.pathname;
        }
      } catch (e) { /* fall through with null wsPath */ }
      return { port, wsPath };
    }
}

This is a minimal, non-breaking change — it only adds a /json/version HTTP call (not a WebSocket, so it won't trigger Chrome's authorization popup) as a fallback when DevToolsActivePort is unavailable.

Notes

• The /json/version endpoint is a standard Chrome DevTools Protocol HTTP API, available whenever remote debugging is active
• This fix also benefits any Linux environment where Chrome is started with --remote-debugging-port but DevToolsActivePort is missing or inaccessible
• The check-deps.mjs script has the same DevToolsActivePort path limitation for WSL2, though it only affects port detection (not the connection failure)

[wakeya]

Title：
CDP Proxy 连接失败：fallback 模式未获取 WebSocket UUID

Body：

Bug Description

CDP Proxy 在 fallback 模式（手动指定调试端口）下无法成功连接 Chrome。

复现步骤

1. 通过外部方式（如 MCP server）启动 Chrome，启用 --remote-debugging-port=9222
2. 运行 node scripts/check-deps.mjs
3. 输出显示 browser: ok (port 9222) [通过手动调试端口连接]
4. 但随后 proxy 超时报错：❌ 连接超时

实际错误

curl http://localhost:3456/targets 返回 {"error":"连接失败"}

查看日志可见重复的：
[CDP Proxy] 通过手动调试端口连接: 9222
[CDP Proxy] 连接错误: 连接失败 （端口缓存已清除，下次将重新发现）

Root Cause

discoverChromePort() 的 fallback 分支直接返回 { port: fallbackPort, wsPath: null }。

这导致 CDP Proxy 用路径 ws://127.0.0.1:9222/devtools/browser 连接（无 UUID），而 Chrome 要求完整路径 ws://127.0.0.1:9222/devtools/browser/。

正常模式（通过 DevToolsActivePort 文件发现）不受影响，因为文件第 2 行包含了真实的 WebSocket UUID。

Suggested Fix

fallback 时查询 /json/version 获取真实的 webSocketDebuggerUrl，提取 UUID 路径：

  const fallbackPort = await findFallbackPort();
  if (fallbackPort !== null) {
    let wsPath = null;
    try {
      const res = await fetch(`http://127.0.0.1:${fallbackPort}/json/version`);
      if (res.ok) {
        const data = await res.json();
        const wsUrl = data.webSocketDebuggerUrl || '';
        const match = wsUrl.match(/ws:\/\/127\.0\.0\.1:\d+(\/.*)/);
        if (match) wsPath = match[1];
      }
    } catch { /* ignore */ }
    connectedBrowser = { id: 'unknown', label: '...', source: 'fallback' };
    console.log(`[CDP Proxy] 通过手动调试端口连接: ${fallbackPort}${wsPath ? ' (获取到 wsPath)' : ' (无 wsPath)'}`);
    return { port: fallbackPort, wsPath };
  }

文件： scripts/cdp-proxy.mjs，第 92–99 行

修复后 connected: true ✅，curl http://localhost:3456/targets 正常返回页面列表 ✅。

Environment

• Node.js 24.13.1 (macOS/Linux)
• Chrome with --remote-debugging-port=9222 (非默认 user-data-dir)
• web-access v2.5.2