Skip to main content

​
Common issues

​
vibe command missing

Check whether the installer printed PATH guidance. Then inspect:
If installed through uv tool, the tool bin directory may not be loaded in your current shell.

​
Agent CLI not found

Verify the selected backend:
Install the missing backend or update the CLI path in the setup wizard.

​
Chat bot is silent

Check:
  • The platform credential is correct.
  • The bot or app is installed into the workspace/server/group.
  • The channel or chat is enabled in Avibe.
  • The selected backend is enabled.
  • The working directory exists.
Then run:

​
Slack bot is silent

Check:
  • Socket Mode is enabled.
  • Bot token scopes are correct.
  • App-level token is correct.
  • Bot is invited to the channel.
  • Channel is selected in Avibe.

​
Telegram group is silent

Check:
  • Bot privacy mode.
  • Whether the bot needs to be mentioned.
  • Whether the group appears in discovered chats.
  • Whether the group is selected in Avibe.

​
Web UI is unreachable from another device

Localhost only works on the same machine. Use:
This opens the local Web UI through a secure avibe.bot tunnel.

​
Custom domain returns 503 or 403

If you front the Web UI with your own reverse proxy on a custom domain and the page returns 503 (or a state-changing action returns 403 invalid origin), Avibe hasn’t been told to trust that domain. Declare both VIBE_UI_TRUSTED_PROXY_IPS (your proxy’s IP) and VIBE_UI_TRUSTED_PUBLIC_ORIGINS (e.g. https://avibe.example.com), and forward the host headers — the proxy IP alone still returns 503. See Reverse proxy & custom domains.