Skip to content

Troubleshooting

TL;DR

Start by checking whether your bot is Online/Offline/Error in the dashboard.

Most issues are permissions, role hierarchy, or Discord configuration.

Having issues? Find solutions to the most common problems here.

Last updated: 2025-12-14


  1. Go to app.vibecord.dev
  2. Find your bot
  3. Is it showing “Online”, “Offline”, or “Error”?

Tell VibeCord to start your bot: “Start the bot” or “Deploy my bot”. Wait 30-60 seconds.

If it shows “Starting” for more than 5 minutes

Section titled “If it shows “Starting” for more than 5 minutes”

Try telling VibeCord to stop and restart: “Stop the bot” then “Start the bot”. If it still won’t start, contact support.

Click on the bot to see the error details. Common errors:

  • Rate limited — Too many requests, wait 15 minutes
  • Invalid configuration — Try regenerating your bot
  • Server error — Our team has been notified, try again later

Each plan has different limits on how many bots can run at once. Check your current plan to see your allowance.

If you’re at your limit, stop another bot or upgrade your plan.


Check your dashboard. The bot should show “Online” status.

Commands start with /. Type / in Discord to see available commands.

Your bot might not have permission to read or send messages in that channel.

Fix: Go to Server Settings → Channels → Select channel → Permissions → Add your bot → Allow “View Channel” and “Send Messages”

If the command involves roles, your bot’s role needs to be higher than the roles it manages.

Fix: Server Settings → Roles → Drag your bot’s role above roles it needs to manage

Test in another channel to see if it’s a channel-specific issue.


  1. Go to your bot’s page on the dashboard
  2. Click the Commands tab
  3. Compare with what you expected

Sometimes commands are named slightly differently. Check the full list.

Edit your bot and add the command to your description:

“Add a /help command that lists all available commands”

Then regenerate.


This is usually a role hierarchy issue.

  1. Go to Discord Server Settings → Roles
  2. Find your bot’s role
  3. Drag it above all roles the bot needs to assign
  4. Click Save

Discord prevents bots from assigning roles that are at or above their own role. It’s a security feature.

Make sure the role you’re trying to assign actually exists in the server.


Your bot needs:

  • View Channel (for welcome channel)
  • Send Messages
  • (Optional) Manage Roles (if assigning roles)

Make sure your welcome message is configured for a channel that exists.

Have someone join your server to test. You can’t trigger join events yourself.

Review your bot description. Is the welcome message clearly defined?


  • Make sure you clicked Authorize, not Cancel
  • Try signing in again
  • Try a different browser (Chrome, Firefox, Safari, Edge)
  • Clear your browser cache
  • Disable browser extensions temporarily

Think about what changed recently:

  • Did you edit the bot?
  • Did you change server settings?
  • Did you update role permissions?

Sometimes asking the AI to investigate helps:

“Check if there are any errors with my bot” “What’s wrong with the deployment?”

Or create a new project if the issue persists.

Look at your bot’s activity log in the dashboard for error messages.


Free plan bots run for a limited time. After the time expires, the bot goes offline.

Solution: Upgrade to a paid plan for 24/7 uptime.

During peak times, responses might be slightly slower.

Commands that do many things take longer. Consider simplifying if speed is critical.


Tell VibeCord to stop the bot first (“Stop the bot”), then try editing or deleting.

Try refreshing. If the issue persists, try a different browser.

Make sure you’re signed into the correct account that owns the bot.


If none of these solutions work:

  1. Check our status page — There might be a known issue
  2. Gather information:
    • What are you trying to do?
    • What error message do you see?
    • When did it last work?
  3. Contact support → — We’re here to help!

We typically respond within 24 hours.

References