OpenClaw "Access Not Configured" Error: Quick Fix Guide

Getting "access not configured" when trying to use OpenClaw's dashboard or browser interface? This means the gateway isn't set up to accept web connections. Here's how to fix it.

Error Messages

You might see any of these:

OpenClaw: access not configured.

Error: web login provider is not available.

Device identity required.

TUI gateway disconnected — closed idle.

They all point to the same root issue: the gateway needs configuration before it accepts browser or API connections.

Quick Fix

Step 1: Set Gateway Mode

openclaw config set gateway.mode local

Step 2: Restart

openclaw restart

Step 3: Approve Your Device

Open the dashboard URL in your browser. You'll see a pairing request. Approve it:

openclaw devices list
openclaw devices approve DEVICE_ID

That's it. The dashboard should now work.

"Web Login Provider Is Not Available"

This specific error means web-based authentication isn't enabled. Fix:

openclaw config set gateway.mode local
openclaw restart

If you're accessing from a different machine:

openclaw config set gateway.mode remote
openclaw config set gateway.host "0.0.0.0"
openclaw restart

"Device Identity Required"

Every new browser connection needs approval. This is a security feature.

# See pending devices
openclaw devices list

# Approve the device
openclaw devices approve DEVICE_ID

If you're connecting via Telegram, approve differently:

openclaw pairing approve telegram CODE

"TUI Gateway Disconnected — Closed Idle"

The TUI (terminal UI) connection timed out. This happens when:

1. The gateway was stopped while TUI was open
2. The system went to sleep
3. Network connection was interrupted

Fix: Simply restart:

openclaw restart

Then reopen the TUI:

openclaw tui

Dashboard Loads But Shows Blank Screen

If the dashboard URL loads but the page is empty or shows a loading spinner:

Check 1: Gateway is running

openclaw status

Look for gateway: running. If it's stopped:

openclaw gateway start

Check 2: Wait for full startup

The gateway takes up to 40 seconds to be fully ready. Check logs:

openclaw logs --follow

Wait for [gateway] listening on before refreshing the dashboard.

Check 3: Browser cache

Clear your browser cache and cookies for the OpenClaw dashboard URL, then reload.

Check 4: Port mismatch

Make sure you're accessing the right port:

openclaw config get gateway.port

Navigate to http://localhost:PORT (use the port from the output).

Docker-Specific Access Issues

Container is running but dashboard is inaccessible

Check port mapping:

docker port YOUR_CONTAINER_ID

Make sure the gateway port is mapped:

docker run -p 3001:3001 openclaw-stack

"Connection refused" from outside the container

The gateway might be binding to 127.0.0.1 inside the container:

docker exec -it YOUR_CONTAINER_ID \
  openclaw config set gateway.bind "0.0.0.0"
docker restart YOUR_CONTAINER_ID

Run Doctor

When in doubt:

openclaw doctor --fix

This checks and fixes:

• Gateway mode configuration
• Port availability
• Device pairing status
• Config validation

Access Without the Hassle

ClawTank gives you instant dashboard access with a pre-configured HTTPS URL. No gateway mode setup, no device pairing — just deploy and open your browser.