LINE channel config is being silently ignored on Windows
LINE channel config is being silently ignored on Windows
Body:
Hello! I'm trying to connect OpenClaw to a LINE bot on Windows, but I'm having trouble getting the gateway to read my channel configuration.
OpenClaw Version: 2026.3.2
OS: Windows
Issue: The channels.line section in my config.yaml is silently ignored on startup. The gateway starts normally, but there are no logs indicating that the LINE channel is being loaded. This results in a 502 Bad Gateway error when LINE tries to send a webhook request.
What I've confirmed:
The @line/bot-sdk package is listed as a dependency in package.json, so the code should be there.
My config.yaml is correctly formatted with valid tokens.
I have tried placing config.yaml in multiple locations (C:\Users\ti.openclaw, C:\Users\ti) and even tried running openclaw gateway run from within the .openclaw directory.
Using openclaw gateway run --dev also doesn't change the outcome.
It seems like the gateway is completely bypassing the channel loading mechanism. Is there a specific build flag, an environment variable, or another configuration setting required to enable channels in this version?
Thank you for your help!
Body:
Hello! I'm trying to connect OpenClaw to a LINE bot on Windows, but I'm having trouble getting the gateway to read my channel configuration.
OpenClaw Version: 2026.3.2
OS: Windows
Issue: The channels.line section in my config.yaml is silently ignored on startup. The gateway starts normally, but there are no logs indicating that the LINE channel is being loaded. This results in a 502 Bad Gateway error when LINE tries to send a webhook request.
What I've confirmed:
The @line/bot-sdk package is listed as a dependency in package.json, so the code should be there.
My config.yaml is correctly formatted with valid tokens.
I have tried placing config.yaml in multiple locations (C:\Users\ti.openclaw, C:\Users\ti) and even tried running openclaw gateway run from within the .openclaw directory.
Using openclaw gateway run --dev also doesn't change the outcome.
It seems like the gateway is completely bypassing the channel loading mechanism. Is there a specific build flag, an environment variable, or another configuration setting required to enable channels in this version?
Thank you for your help!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
