[Bug] Bridge 未启用。请在 config.toml 中启用 [bridge] 以支持网页聊天。

[jianzhoujz]

cc-connect Version

1.2.2-beta5

Operating System

macOS

Agent Type

Other

Platform

DingTalk

Installation Method

npm (npm install -g cc-connect)

Bug Description

我已经配置了[bridge]，重启过cc-connect，在web管理后台的会话页显示“Bridge 未启用。请在 config.toml 中启用 [bridge] 以支持网页聊天。”

Steps to Reproduce

1. 安装cc-connect 1.2.2-beta5。
2. 配置web后台
3. 进入web会话
4. 提示“Bridge 未启用。请在 config.toml 中启用 [bridge] 以支持网页聊天。”

Expected Behavior

正常使用web会话

Actual Behavior

提示“Bridge 未启用。请在 config.toml 中启用 [bridge] 以支持网页聊天。”

Configuration (config.toml)

data_dir = ""
attachment_send = ""
language = "zh"

[[projects]]
  name = "all-projects"
  mode = "multi-workspace"
  base_dir = "/Users/a/a"
  admin_from = "1"

  [projects.agent]
    type = "qoder"

    [projects.agent.options]
      mode = "yolo"
      model = "auto"

  [[projects.platforms]]
    type = "dingtalk"

    [projects.platforms.options]
      client_id = "1"
      client_secret = "1"

[log]
  level = ""

[speech]
  enabled = false
  provider = ""
  language = ""

  [speech.openai]
    api_key = ""
    base_url = ""
    model = ""

  [speech.groq]
    api_key = ""
    model = ""

  [speech.qwen]
    api_key = ""
    base_url = ""
    model = ""

[tts]
  enabled = false
  provider = ""
  voice = ""
  tts_mode = ""
  max_text_len = 0

  [tts.openai]
    api_key = ""
    base_url = ""
    model = ""

  [tts.qwen]
    api_key = ""
    base_url = ""
    model = ""

  [tts.minimax]
    api_key = ""
    base_url = ""
    model = ""







[webhook]
  port = 0

[bridge]
  enabled = true
  port = 9810
  token = "1"
  cors_origins = ["*"]

[management]
  enabled = true
  port = 9820
  token = "1"
  cors_origins = ["*"]

Logs / Error Output

Additional Context

No response

[github-actions]

👋 Thanks @jianzhoujz for opening this issue! We'll take a look soon.

[chenhg5]

感谢详细反馈！我们正在调查这个问题。

调试建议：

1. 检查日志中是否有配置解析警告
2. 尝试将 enabled = true 改为 enabled = true（检查空格问题）
3. 确认配置文件中没有嵌套层级错误

可能的根因：

• TOML 解析 *bool 指针时的异常
• 配置加载时 Bridge 部分没有被正确解析

我们正在本地复现并调试 config 加载逻辑，确认问题后会尽快修复。

[QunShanHe]

问题描述

Management API 正确返回了 Bridge 配置信息：
GET /api/v1/status
{
"data": {
"bridge": {
"enabled": true,
"path": "/bridge/ws",
"port": 9810,
"token_set": true
}
}
}

但是 Web UI (assets/index-*.js) 在构建 WebSocket URL 时，使用了 window.location.host 而不是 API 返回的 bridge.port：

// 当前实现
const wsUrl = ${window.location.protocol==="https:"?"wss:":"ws:"}//${window.location.host}${bridgeConfig.path}?token=${encodeURIComponent(b ridgeConfig.token)};

影响范围

当通过 http://localhost:9820 访问管理界面时：

• window.location.host = localhost:9820
• WebSocket 尝试连接：ws://localhost:9820/bridge/ws ❌
• 实际 Bridge WebSocket 端点：ws://localhost:9810/bridge/ws ✅

验证结果

9820 端口 - 返回 HTML（非 WebSocket）

$ curl -I http://localhost:9820/bridge/ws
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8

9810 端口 - 真正的 WebSocket 端点

$ curl -I "http://localhost:9810/bridge/ws?token=" -H "Connection: Upgrade" -H "Upgrade: websocket"
HTTP/1.1 405 Method Not Allowed
Sec-Websocket-Version: 13

期望行为

Web UI 应该使用 API 返回的 bridge.port (9810) 来连接 Bridge，而不是 Management UI 的端口 (9820)。

建议修复

修改 WebSocket URL 构建逻辑，使用 bridge.port：

// 方案 1：直接使用 bridge.port
const wsUrl = ${window.location.protocol==="https:"?"wss:":"ws:"}//${window.location.hostname}:${bridgeConfig.port}${bridgeConfig.path}?tok en=${encodeURIComponent(bridgeConfig.token)};

// 方案 2：或者由 API 直接返回完整的 WebSocket URL

环境信息

• cc-connect 版本：v1.2.2-beta.5
• 操作系统：Linux
• 安装方式：npm

[chenhg5]

Thanks for the detailed analysis. You're correct that the current implementation uses window.location.host which defaults to the management UI port (9820) instead of the bridge port (9810).

The code comment explains this is intentional for proxy scenarios:

// Use current page host:port so the request goes through the Vite/nginx proxy
// instead of directly hitting the bridge port (which may not be reachable).

Workaround for direct access:
Configure a reverse proxy (nginx, caddy) to forward /bridge/ws to the bridge port.

Potential fix options:

1. Add a config option to choose between proxy mode and direct mode
2. Try the bridge port directly, fall back to current host if connection fails

This is a valid feature request - marking for consideration.