#how tostart openclaw gateway

1 messages · Page 1 of 1 (latest)

thorny vine
#

rror: unknown command 'start'
(Did you mean status?)
PS C:\Users\jan> openclaw open
error: unknown command 'open'
PS C:\Users\jan> openclaw gateway start

🦞 OpenClaw 2026.2.17 (4134875) — Ah, the fruit tree company! 🍎

Failed to discover Ollama models: TypeError: fetch failed
Restarted Scheduled Task: OpenClaw Gateway
PS C:\Users\jan> openclaw gateway start

🦞 OpenClaw 2026.2.17 (4134875) — Ah, the fruit tree company! 🍎

Restarted Scheduled Task: OpenClaw Gateway
PS C:\Users\jan> openclaw gateway open
error: too many arguments for 'gateway'. Expected 0 arguments but got 1.
PS C:\Users\jan> openclaw gateway restart

🦞 OpenClaw 2026.2.17 (4134875) — Meta wishes they shipped this fast.

Restarted Scheduled Task: OpenClaw Gateway
PS C:\Users\jan>

ancient masonBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

wary stratusBOT
#

Those errors are just “wrong command names” (plus one Ollama warning) — nothing is broken there.

1) There is no openclaw start or openclaw open

  • openclaw start → not a thing (use openclaw gateway start to start the service)
  • openclaw open → not a thing (use openclaw dashboard to open the Control UI)

Docs: https://docs.openclaw.ai/cli/dashboard

2) openclaw gateway open is also not a command

gateway doesn’t have an open subcommand, so it complains about the extra argument.

What you probably want instead:

  • Start/restart the background Gateway service (what you already did):
    openclaw gateway status
# 
  openclaw gateway restart
  • Run the Gateway in the foreground (for debugging / to see logs live):
    openclaw gateway
# or:
openclaw gateway run

Docs: https://docs.openclaw.ai/cli/gateway

3) “Failed to discover Ollama models: TypeError: fetch failed”

This usually just means OpenClaw tried to talk to Ollama (typically http://127.0.0.1:11434) and Ollama isn’t running/reachable.

  • If you want Ollama: start Ollama, then retry.
#
  • If you don’t care about Ollama: you can ignore that warning for now.

Next best step

Run and paste:

openclaw gateway status
openclaw status

That’ll show whether the scheduled task is running and whether the RPC probe can actually reach the Gateway.

thorny vine
#

no i want the breowser ui

wary stratusBOT
#

Use the Dashboard command (that’s the browser UI):

openclaw dashboard

If it can’t auto-launch a browser on your Windows box, print the URL and open it manually:

openclaw dashboard --no-open

By default it’s usually here (same machine as the Gateway):

If the page says unauthorized / asks for auth, grab the gateway token and paste it into the UI: