openclaw - 💡(How to fix) Fix [Bug]: Gateway not starting on Windows – Dashboard unreachable (127.0.0.1 refused to connect) [2 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#60490Fetched 2026-04-08 02:50:28
View on GitHub
Comments
2
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
commented ×2labeled ×2renamed ×1

Gateway does not start on Windows, causing the dashboard at 127.0.0.1:18789 to refuse connection

Root Cause

Gateway does not start on Windows, causing the dashboard at 127.0.0.1:18789 to refuse connection

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Gateway does not start on Windows, causing the dashboard at 127.0.0.1:18789 to refuse connection

Steps to reproduce

Install OpenClaw on Windows Uninstall Reinstall OpenClaw on windows Open PowerShell as Administrator Run: openclaw gateway status Run: openclaw dashboard

Expected behavior

Gateway starts successfully and dashboard is accessible at http://127.0.0.1:18789/

Actual behavior

Gateway is registered but not running RPC probe fails Dashboard URL opens but browser shows "127.0.0.1 refused to connect" Restart command times out after 60 seconds

OpenClaw version

2026.4.2 (d74a122)

Operating system

Windows 11

Install method

powershell -c "irm https://openclaw.ai/install.ps1 | iex"

Model

ollama local

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

<img width="1792" height="1003" alt="Image" src="https://github.com/user-attachments/assets/0b0d1eb4-f0aa-4241-a457-aee7858b5428" />

Logs, screenshots, and evidence

https://www.youtube.com/watch?v=bEpoiPfNlnM

Impact and severity

severe

Additional information

No response

extent analysis

TL;DR

The issue with the OpenClaw gateway not starting on Windows may be resolved by checking the installation and configuration of OpenClaw, specifically focusing on the PowerShell commands used for installation and the status of the gateway service.

Guidance

  • Verify the installation process by re-running the installation command powershell -c "irm https://openclaw.ai/install.ps1 | iex" to ensure that OpenClaw is correctly installed.
  • Check the status of the OpenClaw gateway service using the command openclaw gateway status to see if it provides any error messages or clues about why the gateway is not running.
  • Attempt to start the gateway manually using a command like openclaw gateway start (if available) to see if it throws any specific errors.
  • Review the logs and evidence provided in the issue, such as the YouTube video link, for any hints about the cause of the failure.

Example

No specific code snippet can be provided without more details on the OpenClaw commands and their expected outputs.

Notes

The provided information lacks specific details about the OpenClaw configuration, the exact error messages seen when running the commands, and the contents of the logs and video evidence. Therefore, the guidance is limited to general troubleshooting steps.

Recommendation

Apply workaround: Given the lack of detailed error messages and the specific nature of the issue, applying a workaround such as manually starting the gateway service or reinstalling OpenClaw might temporarily resolve the issue until a more permanent fix can be found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Gateway starts successfully and dashboard is accessible at http://127.0.0.1:18789/

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Gateway not starting on Windows – Dashboard unreachable (127.0.0.1 refused to connect) [2 comments, 1 participants]