Gateway Service Port Override & Node Handshake Failure
Environment:
OS: Windows 11
OpenClaw Version: 2026.2.9
Model Stack: Gemini 1.5 Pro / Flash
Setup: Single machine (Local Gateway + Local Node)
Problem Description:
I am experiencing a persistent conflict between the Windows Scheduled Task service and the CLI configuration regarding the Gateway port, which is preventing my local Node from connecting.
Port Conflict/Override:
My openclaw.json is configured for port 19000.
However, the openclaw gateway status reports that the service is running on the default 18789.
Any attempt to force the service to 19000 results in an "exited immediately" state or the service reverting to 18789.
openclaw doctor --fix identifies the port discrepancy but cannot force the Scheduled Task to respect the JSON config port.
Node Connection Failure:
Even when I align the Node to the service port (openclaw node start --url ws://127.0.0.1:18789), the Gateway registry shows the node as connected: false.
openclaw gateway status shows the RPC probe is OK on 18789, but the nodes status command never reflects an active connection.
Bind Logic:
Setting gateway.bind to 0.0.0.0 in the JSON results in an "Invalid input" error during the service start-up, forcing me back to auto (which resolves to 127.0.0.1).
Current State:
The Gateway is "listening" on 18789, but it's not "talking" to the local Node. Is there a known issue with the Windows 11 Scheduled Task service ignoring port overrides in openclaw.json, or a specific handshake requirement for local nodes that I'm missing?
OS: Windows 11
OpenClaw Version: 2026.2.9
Model Stack: Gemini 1.5 Pro / Flash
Setup: Single machine (Local Gateway + Local Node)
Problem Description:
I am experiencing a persistent conflict between the Windows Scheduled Task service and the CLI configuration regarding the Gateway port, which is preventing my local Node from connecting.
Port Conflict/Override:
My openclaw.json is configured for port 19000.
However, the openclaw gateway status reports that the service is running on the default 18789.
Any attempt to force the service to 19000 results in an "exited immediately" state or the service reverting to 18789.
openclaw doctor --fix identifies the port discrepancy but cannot force the Scheduled Task to respect the JSON config port.
Node Connection Failure:
Even when I align the Node to the service port (openclaw node start --url ws://127.0.0.1:18789), the Gateway registry shows the node as connected: false.
openclaw gateway status shows the RPC probe is OK on 18789, but the nodes status command never reflects an active connection.
Bind Logic:
Setting gateway.bind to 0.0.0.0 in the JSON results in an "Invalid input" error during the service start-up, forcing me back to auto (which resolves to 127.0.0.1).
Current State:
The Gateway is "listening" on 18789, but it's not "talking" to the local Node. Is there a known issue with the Windows 11 Scheduled Task service ignoring port overrides in openclaw.json, or a specific handshake requirement for local nodes that I'm missing?
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?
