Docs
Troubleshooting Guide
Fix common setup problems quickly with practical checks and direct recovery steps.
🚨 Common Issues
Bot isn't responding to commands
Symptoms: Commands are ignored, no reactions or replies
Quick checks:
- Verify the bot is online: Check the member list - is the bot's status green?
- Check the prefix: Default is
!. Try !ping to test. - Permissions: Does the bot have "Send Messages" and "Embed Links" in the channel?
- Role hierarchy: Bot's role must be above roles it needs to manage.
Solutions:
- Check service status for outages
- Re-invite the bot with proper permissions
- Check Discord's server outage status
- Use the dashboard to verify configuration
Moderation commands not working
Symptoms: !kick, !ban, !mute fail or show permission errors
Required permissions:
!kick needs: Kick Members!ban / !unban need: Ban Members!mute needs: Moderate Members (timeout)!warn needs: Send Messages + Embed Links
Solutions:
- Go to Server Settings → Roles → Sloth Lee
- Enable required permissions listed above
- Make sure bot role is above the roles it needs to moderate
- Verify moderator roles are configured:
!modrole list
Note: The bot cannot moderate members with higher roles than itself, including server owners.
Tickets not creating channels
Symptoms: Users click ticket button but nothing happens
Checklist:
- Did you run setup?
!ticketsetup must be run first - Permissions: Bot needs "Manage Channels" and "Manage Permissions"
- Category limit: Discord allows max 50 channels per category. Check if category is full.
- Channel limit: Discord allows max 500 channels per server.
Solutions:
- Run
!ticketsetup to reconfigure - Check bot permissions in Server Settings → Roles
- Clean up old ticket channels:
!ticketcleanup - Verify categories exist:
!ticketcategory list
Music commands failing
Symptoms: !play errors, no audio, or bot disconnects
Requirements:
- Bot needs "Connect" and "Speak" permissions in voice channels
- You must be in a voice channel when using commands
- FFmpeg must be installed on the host (server-side, not user-side)
Solutions:
- Join a voice channel first, then
!play - Check voice channel permissions for the bot role
- Try a different URL or search query
- If self-hosting: verify FFmpeg installation
Automod not triggering
Symptoms: Spam/raids not being caught, no automatic actions
Verify configuration:
!automodstatus - Check if automod is enabled!antispam - Verify spam detection settings!antiraid - Check raid protection settings
Common issues:
- Whitelisted users/roles: Admins and whitelisted roles bypass automod
- Thresholds too high: Lower detection thresholds for more sensitivity
- Bot role position: Bot cannot moderate users with equal or higher roles
- Missing permissions: Bot needs "Kick Members" or "Ban Members" for actions
Recommended settings:
!antiraid 5 10 kick
!antispam 5 3 mute
!antiinvite on deleteDashboard not loading or showing errors
Symptoms: Dashboard page blank, login fails, or data not displaying
Quick fixes:
- Clear browser cache and cookies
- Try incognito/private browsing mode
- Re-authorize Discord OAuth connection
- Check status page for service issues
Login issues:
- Make sure you have "Manage Server" permission in your Discord server
- Verify the bot is in your server
- Try logging out and back in to Discord
Anti-nuke accidentally banned someone
Symptoms: Legitimate admin/mod was banned by anti-nuke protection
Immediate recovery:
- Server owner can use
!approveappeal <appeal_id> - Or manually unban via Server Settings → Bans
- Add them to whitelist:
!whitelist @user
Prevention:
- Whitelist all trusted admins:
!whitelist @Admin - Whitelist admin roles:
!whitelist @Administrator - Adjust thresholds:
!antinukeset role_creates 10 - Review configuration:
!antinukeinfo
🆘 Emergency Commands
Use these in crisis situations:
!lockdown
Emergency server-wide lockdown (locks all channels)
!raidmode on
Activate maximum raid protection immediately
!quarantine @user
Isolate suspicious user (removes all roles and permissions)
!purge 100
Bulk delete up to 100 messages in current channel
Recovery: Use !lockdown undo or !raidmode off to restore normal operation.