OpenClaw Error: Web Login Provider Is Not Available — Fix Guide

What Causes This Error?

The full error message reads: Error: Web Login Provider Is Not Available. It appears when you try to access OpenClaw's web UI and the system cannot find a configured authentication provider to handle the login flow.

This happens in one of four scenarios:

1. No AUTH_PROVIDER is set. OpenClaw's web UI requires an authentication provider when AUTH_ENABLED=true (which is the default). If you have not set AUTH_PROVIDER in your .env file, OpenClaw does not know which OAuth service to use for login, and it throws this error.

2. The provider credentials are missing. You set AUTH_PROVIDER=google but forgot to add GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. OpenClaw finds the provider name but cannot initialize it without valid credentials.

3. The provider credentials are invalid. The client ID or secret is wrong, expired, or belongs to a different OAuth application. OpenClaw tries to validate the credentials on startup and fails silently, leaving the provider unavailable.

4. Legacy environment variables. If you upgraded from ClawdBot or MoltBot, you might have old variable names like CLAWDBOT_AUTH_PROVIDER or MOLTBOT_AUTH_PROVIDER. These were removed in OpenClaw 3.22. The current variables use the AUTH_ prefix without any project name.

What Is the Quickest Fix?

If you do not need web UI authentication — for example, if you only access OpenClaw via Telegram, Discord, WhatsApp, or the API — the fastest fix is to disable authentication entirely:

# In your .env file
AUTH_ENABLED=false

Then restart OpenClaw:

docker compose restart

This removes the login screen entirely. The web UI will be accessible without authentication. Only do this if the web UI is not exposed to the public internet, or if you have other access controls in place (VPN, reverse proxy with HTTP auth, etc.).

If you do need authentication, continue with the provider-specific setup below.

How Do You Set Up Google OAuth?

Google OAuth is the most common choice. Here is the complete setup:

1. Go to the Google Cloud Console. Navigate to APIs & Services → Credentials.
2. Create an OAuth 2.0 Client ID. Click "Create Credentials" → "OAuth client ID." Choose "Web application" as the application type.
3. Set the authorized redirect URI. Add https://your-domain.com/auth/callback/google. Replace your-domain.com with your actual OpenClaw domain. If running locally, use http://localhost:18789/auth/callback/google.
4. Copy the credentials. Google will show you a Client ID and Client Secret. Copy both.
5. Add to your .env file:

AUTH_ENABLED=true
AUTH_PROVIDER=google
GOOGLE_CLIENT_ID=your-client-id-here.apps.googleusercontent.com
GOOGLE_CLIENT_SECRET=your-client-secret-here
AUTH_CALLBACK_URL=https://your-domain.com/auth/callback/google

6. Restart OpenClaw. Run docker compose restart and try accessing the web UI. You should see a "Sign in with Google" button.

Common mistakes: forgetting the /auth/callback/google path in the redirect URI, using HTTP instead of HTTPS, or copying the credentials with extra whitespace.

4 AI personas and 7 free skills — browse the marketplace.

How Do You Set Up GitHub OAuth?

GitHub OAuth is simpler to configure and a good choice for developer-focused teams:

1. Go to GitHub Developer Settings. Navigate to Settings → Developer Settings → OAuth Apps → New OAuth App.
2. Fill in the application details. Set the "Authorization callback URL" to https://your-domain.com/auth/callback/github.
3. Copy the credentials. After creating the app, you will see a Client ID. Generate a client secret and copy it immediately (it is only shown once).
4. Add to your .env file:

AUTH_ENABLED=true
AUTH_PROVIDER=github
GITHUB_CLIENT_ID=your-github-client-id
GITHUB_CLIENT_SECRET=your-github-client-secret
AUTH_CALLBACK_URL=https://your-domain.com/auth/callback/github

5. Restart OpenClaw. You should now see a "Sign in with GitHub" button on the login page.

GitHub's OAuth flow is straightforward and rarely causes issues. The most common problem is mismatched callback URLs — the URL in your .env must exactly match the URL in your GitHub OAuth app settings.

How Do You Verify Your Configuration?

After setting up your OAuth provider, verify that everything is correct:

Check the startup logs. Run docker compose logs openclaw and look for authentication-related messages. A successful configuration shows:

[auth] Provider: google
[auth] Callback URL: https://your-domain.com/auth/callback/google
[auth] Provider initialized successfully

If you see errors like [auth] Failed to initialize provider or [auth] Invalid client credentials, your credentials are wrong or the provider is misconfigured.

Check your .env file for typos. Common issues include:

• Extra spaces around the = sign (use AUTH_PROVIDER=google, not AUTH_PROVIDER = google)
• Quotes around values that should not have them
• Invisible characters copied from web pages (retype the values manually if unsure)
• Wrong variable names (check for legacy CLAWDBOT_ or MOLTBOT_ prefixes)

Test the callback URL. Navigate directly to https://your-domain.com/auth/callback/google in your browser. You should be redirected to the Google login page. If you get a 404, the URL is wrong or OpenClaw is not running on that domain.

What If It Still Does Not Work?

If you have verified the provider, credentials, and callback URL but still see the error:

• Clear your browser cache. Old cookies or cached redirects can interfere with the OAuth flow. Try an incognito/private window.
• Check your reverse proxy. If you use Nginx, Caddy, or Traefik in front of OpenClaw, make sure it forwards the /auth/ path correctly. Proxy misconfiguration is a common cause of OAuth failures.
• Check the container environment. Run docker compose exec openclaw env | grep AUTH to verify that the environment variables are actually reaching the container. Docker Compose sometimes caches old .env values — run docker compose up -d --force-recreate to rebuild.
• Check network access. The OpenClaw container needs outbound HTTPS access to the OAuth provider (accounts.google.com, github.com, etc.). If you have restrictive firewall rules or a corporate proxy, this can block the OAuth handshake.
• Try a different provider. If Google is not working, try GitHub or Discord to isolate whether the issue is provider-specific or a general configuration problem.
• Reset and start fresh. Delete all AUTH_* variables, set AUTH_ENABLED=false, restart, verify the UI works without auth, then re-enable auth one step at a time.

If none of the above works, post your sanitized configuration (remove client secrets) in the OpenClaw community for help from other operators.