Bug type

Regression (worked before, now fails)

Summary

Environment:

• OpenClaw version: 2026.3.13
• OS: Windows 10.0.26200 x64
• Node: 24.14.0
• Install method: npm global
• LINE plugin loaded from:
  C:\Users\cklee\AppData\Roaming\npm\node_modules\openclaw\extensions\line

Config:

• channels.line.enabled = true
• channels.line.channelAccessToken set
• channels.line.channelSecret set
• channels.line.dmPolicy = "pairing"
• plugins.entries.line.enabled = true
• plugins.load.paths includes the line extension
• plugins.allow = ["line"]

Observed behavior:

• Gateway log shows:
  [line] [default] starting LINE provider (CK bot)
• But POST requests to /line/webhook return 404

Repro:

1. Start gateway with openclaw gateway
2. Confirm LINE provider starts in logs
3. Run:
   curl -i -X POST http://127.0.0.1:18789/line/webhook
4. Result:
   HTTP/1.1 404 Not Found

Additional notes:

• GET /line/webhook returns the OpenClaw Control UI HTML
• ngrok forwarding works and LINE can reach the machine
• ngrok logs show repeated POST /line/webhook -> 404
• At least once there was a 200 response, but mostly 404
• Pairing approval can succeed, suggesting partial LINE flow works, but normal message delivery is unstable/broken

Expected behavior:

• /line/webhook should be registered and handle LINE webhook POST requests consistently

Steps to reproduce

1. Install OpenClaw 2026.3.13 on Windows.
2. Enable the LINE plugin and configure channels.line with a valid channelAccessToken and channelSecret.
3. Start the gateway with openclaw gateway.
4. Confirm the log shows: [line] [default] starting LINE provider (...).
5. Send a POST request to http://127.0.0.1:18789/line/webhook.
6. Observe that the response is 404 Not Found.

Expected behavior

The LINE webhook route should be registered correctly, so POST requests to /line/webhook return a successful webhook response instead of 404, and incoming LINE messages are delivered to OpenClaw normally.

Actual behavior

The gateway log shows that the LINE provider starts successfully, but POST requests to /line/webhook return 404 Not Found. Webhook verification in LINE Developers fails or behaves inconsistently, and incoming LINE messages are not delivered reliably. Pairing could succeed once, but normal message replies still did not work because webhook requests kept returning 404.

OpenClaw version

2026.3.13

Operating system

Windows 11

Install method

No response

Model

openai-codex/gpt-5.4 (default main agent model)

Provider / routing chain

LINE Messaging API webhook -> ngrok public HTTPS URL -> local OpenClaw gateway on 127.0.0.1:18789 -> main agent (openai-codex/gpt-5.4)

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response