Skip to main content

Common Issues

Quick answers to the most frequently encountered problems on OpenClaw Host.

My instance is stuck on "Provisioning"​

Cause: Instance provisioning typically completes within 1-2 minutes. If it takes longer, there may be a temporary resource delay.

Solution:

  1. Wait at least 2 minutes.
  2. Refresh the dashboard page.
  3. Check that your payment was processed in Billing > Invoice History.
  4. If the status does not change after 5 minutes, try Dashboard > Instance > Retry Provision.
  5. If it still does not work, contact support.

My bot is not responding to messages​

Cause: Multiple things can prevent responses -- the channel might not be connected, the AI provider might be misconfigured, or the instance might be down.

Solution:

  1. Check that your instance shows as Running in the dashboard.
  2. Verify the channel is Connected under Instance > Channels.
  3. Check that your AI provider API key is valid under Instance > AI Provider.
  4. Check the logs for error messages.

I cannot connect my channel​

Cause: Usually a problem with the bot token or missing permissions on the platform.

Solution:

  1. Verify you copied the full token with no extra spaces.
  2. For Discord: make sure you enabled Message Content Intent and Server Members Intent.
  3. For Slack: make sure you have both the xoxb- bot token and the xapp- app-level token.
  4. For Telegram: send /token to @BotFather to get a fresh token.
  5. See the specific channel guide for detailed setup steps: Telegram, Discord, Slack.

My AI provider is not responding​

Cause: The API key might be invalid, expired, or out of credits.

Solution:

  1. Verify your API key is correct in Instance > AI Provider.
  2. Check your AI provider's dashboard for billing or credit issues:
  3. Check the logs for specific error codes (401 = bad key, 429 = rate limited, 402/insufficient_quota = no credits).

My instance keeps restarting​

Cause: This usually means the instance is crashing due to a configuration issue or resource exhaustion.

Solution:

  1. Check the logs for error messages right before the restart.
  2. If you see OOMKilled, your instance is running out of memory. Consider upgrading your plan.
  3. If you see a configuration error, try resetting the problematic setting via the CLI or dashboard.
  4. Contact support if the restarts continue with no clear cause in the logs.

I changed my AI provider key but the bot still uses the old one​

Cause: Configuration changes sometimes require a gateway restart to take effect.

Solution:

  1. Go to Instance in the dashboard.
  2. Click Restart Instance.
  3. Wait for the instance to reach Running status.
  4. Test again.

I forgot my account password​

Solution:

  1. Go to the login page.
  2. Click Forgot Password.
  3. Enter your email address.
  4. Check your inbox for a password reset link.
  5. If you do not receive an email within a few minutes, check your spam folder.