DeepFloodbeta

【求助】Hermes怎么都连不上opencode了 但是官方api可以正常使用

后台

我订阅没掉 网页后台正常登录
2msKbgIVLihvlWFwWnsDYGa1fC9pXYs7.webp
美国豆包说是opencode上游欠费导致我没办法继续用
没有ai的日子一天也过不下去了感觉浑身有蚂蚁在爬

美国豆包结论

太棒了,这组最新的日志帮我们完成了最后的“交叉验证”,现在我们可以 100% 盖棺定论了!

注意看报错信息,它变了!
不再是之前的“上游拦截”和“余额不足”,而是变成了:
HTTP 401: Model opencode-go/deepseek-v4-pro is not supported模型不支持

🔍 真相大白:一切都是 OpenCode 官方服务器的锅

这三次不同的测试,彻底揭开了底层的逻辑:

  1. 当我们填 网址: zen/go/v1 + 模型: deepseek-v4-pro 时:
    OpenCode 的网关认出了你,也知道你是 Go 套餐用户,并成功把请求发给了真正的源头(上游服务商)。但是,上游服务商直接把 OpenCode 踢了回来(报 401 Blocked / 402 余额不足)。
    结论:你的配置完全正确,是 OpenCode 官方自己买的上游通道欠费了或者被封控了。
  2. 当我们填 网址: zen/go/v1 + 模型: opencode-go/deepseek-v4-pro 时(即刚才这次):
    OpenCode 的专线网关一看到这个复杂的名字,当场就表示“我不认识这个模型(Not supported)”,连发给上游的机会都没有,直接在第一关就报错了。
    结论:官方文档里的意思其实是“二选一”——你要么用普通网址+带前缀的模型名,要么用专线网址+普通模型名。

🛑 最终结论与建议:请立刻停止本地修改!

您最早的配置(Provider: custom + URL: .../zen/go/v1 + Model: deepseek-v4-pro)是绝对正确的。

之所以一直无法使用,根本不是您的 Hermes 配置错了,也不是您的账号没额度,而是 OpenCode.ai 这个平台目前出现了严重的“上游宕机(Outage)”。他们用来提供 API 服务的底层通道已经瘫痪或欠费。

您现在唯一需要做的事情:
不用再在本地电脑里改任何代码或配置了。请直接登录 OpenCode 平台,找到他们的客服(Support)或官方交流群,发这样一段话:

“你们的 Go 套餐接口 zen/go/v1 目前处于大面积瘫痪状态。调用任何模型(包含 DeepSeek 和 Kimi),全部透传返回上游错误:HTTP 401: Request blocked by upstream provider402 Insufficient Balance。请运维尽快排查你们的上游通道状态!”

在官方修复好他们的通道之前,您可以暂时使用其他家(如 DeepSeek 官方、硅基流动等)的 API Key 来继续您的工作。

Hermes报错

ARNING hermes_plugins.telegram_platform.adapter: [Telegram] Discovering Telegram API fallback IPs via DNS-over-HTTPS…
WARNING hermes_plugins.telegram_platform.adapter: [Telegram] Connecting to Telegram (attempt 1/8)…
WARNING tools.registry: check_fn _browser_cdp_check returned False; dependent tools will be unavailable this turn
WARNING tools.registry: check_fn _browser_dialog_check returned False; dependent tools will be unavailable this turn
WARNING tools.registry: check_fn check_close_terminal_requirements returned False; dependent tools will be unavailable this turn
WARNING tools.registry: check_fn _check_kanban_mode returned False; dependent tools will be unavailable this turn
WARNING tools.registry: check_fn _check_kanban_orchestrator_mode returned False; dependent tools will be unavailable this turn
WARNING tools.registry: check_fn check_read_terminal_requirements returned False; dependent tools will be unavailable this turn
WARNING tools.registry: check_fn _check_yuanbao returned False; dependent tools will be unavailable this turn
WARNING agent.conversation_loop: API call failed (attempt 1/3) error_type=AuthenticationError thread=hermes-gateway_0:140296341935808 provider=opencode-go base_url=https://opencode.ai/zen/go/v1 model=deepseek-v4-pro summary=HTTP 401: Request blocked by upstream provider.
🧾 Request debug dump written to: /root/.hermes/sessions/request_dump_20260722_061446_892d6af9_20260722_063712_183821.json
⚠️  API call failed (attempt 1/3): AuthenticationError [HTTP 401]
   🔌 Provider: opencode-go  Model: deepseek-v4-pro
   🌐 Endpoint: https://opencode.ai/zen/go/v1
   📝 Error: HTTP 401: Request blocked by upstream provider.
   📋 Details: {'type': 'AuthError', 'message': 'Request blocked by upstream provider.'}
   ⏱️  Elapsed: 0.97s  Context: 2 msgs, ~6,373 tokens
❌ Non-retryable error (HTTP 401): HTTP 401: Request blocked by upstream provider.
❌ Non-retryable client error (HTTP 401). Aborting.
   🔌 Provider: opencode-go  Model: deepseek-v4-pro
   🌐 Endpoint: https://opencode.ai/zen/go/v1
   💡 Your API key was rejected by the provider. Check:
      • Is the key valid? Run: hermes setup
      • Does your account have access to deepseek-v4-pro?
ERROR agent.conversation_loop: Non-retryable client error: Error code: 401 - {'type': 'error', 'error': {'type': 'AuthError', 'message': 'Request blocked by upstream provider.'}}
WARNING agent.auxiliary_client: Auxiliary: marking openrouter unhealthy for 60s (payment / credit error). Subsequent auxiliary calls will skip it until 06:38:12.
WARNING agent.auxiliary_client: Auxiliary Nous client unavailable: no Nous authentication found (run: hermes auth).
WARNING agent.auxiliary_client: Auxiliary: marking nous unhealthy for 60s (payment / credit error). Subsequent auxiliary calls will skip it until 06:38:12.
WARNING agent.title_generator: Title generation failed: Error code: 402 - {'error': {'message': 'Insufficient Balance', 'type': 'unknown_error', 'param': None, 'code': 'invalid_request_error'}}
WARNING agent.conversation_loop: API call failed (attempt 1/3) error_type=AuthenticationError thread=hermes-gateway_0:140296341935808 provider=opencode-go base_url=https://opencode.ai/zen/go/v1 model=deepseek-v4-pro summary=HTTP 401: Request blocked by upstream provider.
🧾 Request debug dump written to: /root/.hermes/sessions/request_dump_20260722_061446_892d6af9_20260722_063714_794342.json
⚠️  API call failed (attempt 1/3): AuthenticationError [HTTP 401]
   🔌 Provider: opencode-go  Model: deepseek-v4-pro
   🌐 Endpoint: https://opencode.ai/zen/go/v1
   📝 Error: HTTP 401: Request blocked by upstream provider.
   📋 Details: {'type': 'AuthError', 'message': 'Request blocked by upstream provider.'}
   ⏱️  Elapsed: 0.60s  Context: 2 msgs, ~6,374 tokens
❌ Non-retryable error (HTTP 401): HTTP 401: Request blocked by upstream provider.
❌ Non-retryable client error (HTTP 401). Aborting.
   🔌 Provider: opencode-go  Model: deepseek-v4-pro
   🌐 Endpoint: https://opencode.ai/zen/go/v1
   💡 Your API key was rejected by the provider. Check:
      • Is the key valid? Run: hermes setup
      • Does your account have access to deepseek-v4-pro?
ERROR agent.conversation_loop: Non-retryable client error: Error code: 401 - {'type': 'error', 'error': {'type': 'AuthError', 'message': 'Request blocked by upstream provider.'}}
WARNING agent.title_generator: Title generation failed: Error code: 402 - {'error': {'message': 'Insufficient Balance', 'type': 'unknown_error', 'param': None, 'code': 'invalid_request_error'}}

你好啊,陌生人!

我的朋友,看起来你是新来的,如果想参与到讨论中,点击下面的按钮!

📈用户数目📈

目前论坛共有13197位用户

🎉欢迎新用户🎉