Repository navigation
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper 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 marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper 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.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivityMarked as stale due to inactivity
Description
OS: Win10 x64 | OpenClaw: 2026.5.28 | @openclaw/line: 2026.5.28
Bug: /line/webhook POST returns 404 after v2026.5.28 update
Steps:
- Install @openclaw/line plugin
- Configure LINE credentials
- Restart gateway
- 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
- Install @openclaw/line plugin: openclaw plugins install @openclaw/line
- Configure LINE channel with valid credentials in openclaw.json
- Restart gateway
- 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
Reacted by clawsweeper
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper 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 marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper 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.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.Auth, provider routing, model choice, or SecretRef resolution may break.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Priority
None yet
Activity
clawsweeper commentedon Jun 1, 2026
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.defaultand 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:
accountConfigfor the normalized LINE account id instead of skipping the default account, so credentials underchannels.line.accounts.defaultreach token and secret resolution. (extensions/line/src/accounts.ts:101, be48a430bfa6)enabledasbaseEnabled && accountEnabled, so configured named accounts are enabled unless explicitly disabled. (extensions/line/src/accounts.ts:128, be48a430bfa6)accounts.default, preferringaccounts.defaultover top-level credentials, and treating named accounts without explicitenabledas enabled. (extensions/line/src/accounts.test.ts:205, be48a430bfa6)startAccountlogs the LINE provider start, loadsmonitorLineProvider, and passes the resolved account token, secret, account id, runtime, and webhook path into the monitor. (extensions/line/src/gateway.ts:46, be48a430bfa6)monitorLineProviderregisters 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)extensions/line/src/monitor.lifecycle.test.ts:243, be48a430bfa6)Likely related people:
accounts.defaultlookup 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)extensions/line/src/accounts.ts,extensions/line/src/accounts.test.ts)src/plugins/http-registry.ts,src/plugins/runtime.ts,src/gateway/server-runtime-state.ts)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.
t0063801 commentedon Jun 2, 2026
openclaw-barnacle commentedon Jul 6, 2026
This issue has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.