What port does the OpenClaw Gateway use?
The OpenClaw Gateway uses port 18789 by default and binds to loopback by default. You can change gateway.port, but should not expose the admin surface directly to the public internet.
OpenClaw Gateway Setup: Current 2026 Guide
The OpenClaw Gateway is the control plane for sessions, channels, authentication, and state. It binds to loopback on port 18789 by default. Install it through onboarding, verify it with openclaw gateway status, and keep remote access behind SSH or a trusted private network.
What the Gateway Actually Does
Connects clients and channels
The Gateway coordinates agent sessions and the messaging channels you enable during configuration.
Owns runtime state
Sessions, authentication profiles, channel state, and the Control UI are managed through one Gateway process.
Enforces access
Gateway authentication protects the WebSocket and Control UI. Loopback is the safe default for a local installation.
Current Gateway Commands
These commands follow the current OpenClaw CLI flow. Older instructions that install a separate “gateway skill,” use a gateway.json file, or assume port 3100 are obsolete.
Install and configure the service
openclaw onboard --install-daemonCheck service status
openclaw gateway statusCheck Gateway health
openclaw gateway healthProbe the Gateway
openclaw gateway probeValidate configuration
openclaw config validateOpen the Control UI
openclaw dashboardSafe Local and Remote Access
Local Control UI
Run openclaw dashboard or open http://127.0.0.1:18789/. Treat it as an administrative surface, not a public website.
Remote Gateway
Keep the Gateway on loopback and forward it over SSH or a trusted tailnet. A standard tunnel is:
ssh -N -L 18789:127.0.0.1:18789 user@gateway-hostOpenClaw Gateway FAQ
How do I check whether the OpenClaw Gateway is running?
Run openclaw gateway status. For deeper checks, use openclaw gateway health, openclaw gateway probe, openclaw status --deep, or openclaw doctor.
How do I open the OpenClaw dashboard?
Run openclaw dashboard, or open http://127.0.0.1:18789/ on the machine that can reach the Gateway. Authentication is still required.
Gateway Troubleshooting Checklist
Run openclaw gateway status and confirm the service is installed and running.
Run openclaw config validate before troubleshooting integrations.
Use openclaw gateway health or openclaw gateway probe for a deeper connectivity check.
Confirm the client is targeting port 18789, unless you intentionally changed gateway.port.
For remote access, confirm the SSH or tailnet path is active and supply the configured token or password.
Run openclaw doctor when configuration or service state has drifted after an update.
Build and troubleshoot with other operators
The community is for people building AI agents, vibe-coded products, and AI-powered businesses. The bridge page explains the offer.
Explore the Community