Skip to content

[Bug] LINE channel webhook returns 404 after v2026.5.28 update #89184

Closed

Description

@t0063801

OS: Win10 x64 | OpenClaw: 2026.5.28 | @openclaw/line: 2026.5.28

Bug: /line/webhook POST returns 404 after v2026.5.28 update

Steps:

  1. Install @openclaw/line plugin
  2. Configure LINE credentials
  3. Restart gateway
  4. POST to /line/webhook → 404

Detail:
LINE plugin loads (9 plugins: ..., line, ...), channel starts, no errors in logs. But webhook POST always 404. GET returns dashboard HTML.

Tried: force reinstall, different webhookPath values. Was working pre-update.

Environment

  • OpenClaw version: 2026.5.28
  • @openclaw/line plugin version: 2026.5.28
  • OS: Windows 10 x64
  • Node: v22.22.2

Summary

After upgrading OpenClaw to 2026.5.28, the LINE channel webhook endpoint (/line/webhook) returns HTTP 404 on POST requests, even though the LINE plugin is loaded and the channel starts successfully.

Steps to Reproduce

  1. Install @openclaw/line plugin: openclaw plugins install @openclaw/line
  2. Configure LINE channel with valid credentials in openclaw.json
  3. Restart gateway
  4. Test POST to http://127.0.0.1:18789/line/webhook

Actual Behavior

  • POST /line/webhook → 404 Not Found
  • GET /line/webhook → 200 (returns Control UI dashboard HTML)
  • Other webhook paths tested: /line, /webhook/line, /api/line/webhook → all 404

Expected Behavior

POST /line/webhook should return 200 (with LINE webhook handler)

Evidence

  • Gateway confirms LINE plugin is loaded
  • Log shows: [default] starting LINE provider - channel starts successfully
  • No LINE-related errors in gateway logs after startup
  • Tried force-reinstalling and different webhookPath → no change
  • This was working before the 2026.5.28 update
  • ngrok tunnel and LINE credentials are valid

Activity

  1. clawsweeper commented on Jun 1, 2026

    @clawsweeper
    Contributor

    Thanks for the context here. I did a careful shell check against current main, and this is already implemented.

    Close as implemented on current main: the merged LINE resolver fix in #81471 now loads accounts.default, default-enables configured named accounts, and leaves webhook registration downstream of a correctly resolved account; the broader runtime-loaded workspace-plugin route issue remains separately tracked at #94572.

    I found the merged PR that appears to have closed this: #81471: fix(line): load accounts.default and default-enable named accounts.

    So I’m closing this as already implemented rather than keeping a duplicate issue open.

    Review details

    Best possible solution:

    Keep the merged LINE resolver behavior, ship it in the next release, and track any unrelated current-main plugin route lifecycle failure under #94572 or a new focused report.

    Do we have a high-confidence way to reproduce the issue?

    Yes for the original shipped failure path: current source plus the merged PR proof show the old resolver skipped accounts.default and disabled named accounts, while current main contains the repair; I did not run a fresh live LINE repro in this read-only pass.

    Is this the best way to solve the issue?

    Yes. The owner-plugin resolver fix is the narrowest maintainable solution for the LINE account-credential/enabled-state route-registration failure; the broader runtime-loaded workspace-plugin route lifecycle remains a separate open issue.

    Security review:

    Security review: This is a non-PR issue and does not itself report a security-sensitive flaw.

    AGENTS.md: found and applied where relevant.

    What I checked:

    • Current LINE resolver reads the account entry: Current main resolves accountConfig for the normalized LINE account id instead of skipping the default account, so credentials under channels.line.accounts.default reach token and secret resolution. (extensions/line/src/accounts.ts:101, be48a430bfa6)
    • Current LINE enabled-state behavior matches the intended default: Current main computes enabled as baseEnabled && accountEnabled, so configured named accounts are enabled unless explicitly disabled. (extensions/line/src/accounts.ts:128, be48a430bfa6)
    • Regression tests cover the fixed resolver cases: The test suite now covers resolving credentials from accounts.default, preferring accounts.default over top-level credentials, and treating named accounts without explicit enabled as enabled. (extensions/line/src/accounts.test.ts:205, be48a430bfa6)
    • Webhook registration path is downstream of a started account: startAccount logs the LINE provider start, loads monitorLineProvider, and passes the resolved account token, secret, account id, runtime, and webhook path into the monitor. (extensions/line/src/gateway.ts:46, be48a430bfa6)
    • Webhook monitor registers plugin HTTP route and accepts signed POSTs: monitorLineProvider registers the normalized LINE webhook path through the plugin route helper and returns HTTP 200 after matching a valid LINE signature. (extensions/line/src/monitor.ts:341, be48a430bfa6)
    • Route behavior has adjacent monitor coverage: Monitor lifecycle tests assert LINE account target registration, shared-path signed POST dispatch, and normalized trailing-slash webhook POST dispatch returning 200. (extensions/line/src/monitor.lifecycle.test.ts:243, be48a430bfa6)

    Likely related people:

    • edenfunf: Authored the merged LINE resolver PR that changed accounts.default lookup and named-account enablement, with focused regression tests and real LINE/ngrok proof. (role: fix author; confidence: high; commits: cdda4c02a236, 0647260f8727; files: extensions/line/src/accounts.ts, extensions/line/src/accounts.test.ts)
    • vincentkoc: Merged the resolver fix PR and appears in adjacent LINE/plugin-route review history for this channel boundary. (role: merger and recent area contributor; confidence: medium; commits: 0647260f8727; files: extensions/line/src/accounts.ts, extensions/line/src/accounts.test.ts)
    • steipete: Authored the pinned plugin HTTP route registry work that defines the gateway route-registration boundary used by LINE webhooks. (role: adjacent route-registry owner; confidence: medium; commits: c336a205646a, a69f6190ab56; files: src/plugins/http-registry.ts, src/plugins/runtime.ts, src/gateway/server-runtime-state.ts)
    • coygeek: Authored recent server-local plugin HTTP dispatch hardening on the same gateway route/context boundary that distinguishes this LINE fix from the broader workspace-plugin route issue. (role: recent adjacent contributor; confidence: medium; commits: 5dba99d0b35b, 01a256eb05c6; files: src/gateway/server-runtime-state.ts, src/gateway/server.impl.ts, src/gateway/server/plugins-http.runtime-scopes.test.ts)

    Codex review notes: model internal, reasoning high; reviewed against be48a430bfa6; fix evidence: merged PR #81471, commit 0647260f8727, main fix timestamp 2026-06-28T22:44:31Z.

  2. added
    P2Normal backlog priority with limited blast radius.
    impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.
    impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    on Jun 1, 2026
  3. t0063801 commented on Jun 2, 2026

    @t0063801
    Author

    作業系統: Win10 x64 | OpenClaw: 2026.5.28 | @openclaw/line: 2026.5.28

    錯誤: v2026.5.28 更新後,/line/webhook POST 要求回傳 404錯誤。

    步驟:

    1. 安裝 @openclaw/line 插件
    2. 配置 LINE 憑證
    3. 重啟網關
    4. 向 /line/webhook 發送 POST 請求 → 404

    詳情: LINE 外掛程式載入正常(共 9 個外掛程式:...、line、...),頻道已啟動,日誌中無錯誤。但 webhook POST 請求始終傳回 404 錯誤,GET 要求返回儀表板 HTML 程式碼。

    已嘗試:強制重新安裝,不同的 webhookPath 值。更新前運作正常。

    環境

    • OpenClaw 版本:2026.5.28
    • @openclaw/line 外掛程式版本:2026.5.28
    • 作業系統:Windows 10 x64
    • 節點版本:v22.22.2

    概括

    將 OpenClaw 升級到 2026.5.28 後,LINE 通道 webhook 端點 (/line/webhook) 在 POST 請求時傳回 HTTP 404,即使 LINE 外掛程式已載入且通道已成功啟動。

    重現步驟

    1. 安裝 @openclaw/line 外掛:openclaw plugins install @openclaw/line
    2. 在 openclaw.json 中配置 LINE 通道並新增有效憑證
    3. 重啟網關
    4. 測試向http://127.0.0.1:18789/line/webhook發送 POST 請求

    實際行為

    • POST /line/webhook → 404 找不到
    • GET /line/webhook → 200(返回 Control UI 儀表板 HTML)
    • 其他測試的 webhook 路徑:/line、/webhook/line、/api/line/webhook → 全部回傳 404

    預期行為

    POST /line/webhook 應該回傳 200(使用 LINE webhook 處理程序)

    證據

    • 網關確認 LINE 插件已加載
    • 日誌顯示:[預設] 正在啟動 LINE 提供者 - 通道已成功啟動
    • 啟動後網關日誌中未發現與線路相關的錯誤
    • 嘗試強制重新安裝和使用不同的 webhook 路徑 → 問題依舊
    • 在 2026.5.28 更新之前,此功能運作正常。
    • ngrok隧道和LINE憑證有效
  4. added
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    and removed
    issue-rating: 🦪 silver shellfishThin issue quality; more reproduction proof or environment detail is needed.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    on Jun 15, 2026
  5. openclaw-barnacle commented on Jul 6, 2026

    @openclaw-barnacle

    This issue has been automatically marked as stale due to inactivity.
    Please add updates or it will be closed.

  6. locked as resolved and limited conversation to collaborators on Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivity

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions