Troubleshooting

​

Problem

​

Critical Solution

// noCallHome: true,

​

Why This Happens

​

Steps

1. Navigate to node_modules/@distube/yt-dlp/dist/index.js
2. Search for noCallHome: true (appears twice)
3. Add // at the beginning of both lines
4. Save the file
5. Restart the bot with npm start

​

Prevention

// In package.json
"scripts": {
  "postinstall": "sed -i 's/noCallHome: true,/\/\/ noCallHome: true,/g' node_modules/@distube/yt-dlp/dist/index.js"
}

​

Problem

​

Possible Causes

• The video is region-locked
• The video has been removed by the uploader
• The video is private or unlisted
• Age-restricted content

​

Solutions

1. Try a different video: Search for an alternative version of the song
2. Use official channels: Official music videos are less likely to be removed
3. Check video accessibility: Open the URL in a browser to verify it’s available

# Try with a direct YouTube URL
r!play https://youtube.com/watch?v=VIDEO_ID

​

Problem

​

Cause

​

Solution

1. Find an alternative version of the song
2. Use the official music video if available
3. Search for a live performance or cover version

​

Problem

​

Solution 1: Use Included FFmpeg

​

Solution 2: Manual Installation

​

Windows (using Chocolatey)

1. Install Chocolatey
2. Open PowerShell as administrator:

choco install ffmpeg

3. Restart your terminal or computer

​

Linux

sudo apt update
sudo apt install ffmpeg

​

macOS

brew install ffmpeg

​

Verify Installation

ffmpeg -version

​

Problem

​

Solutions

1. Update FFmpeg: Ensure you have the latest version
2. Check system resources: High CPU usage can cause encoding issues
3. Reinstall ffmpeg-static:

npm uninstall ffmpeg-static
npm install ffmpeg-static

4. Use system FFmpeg: Install FFmpeg manually (see above) and remove ffmpeg-static

​

Problem

​

Checklist

1. Verify prefix: Make sure you’re using the correct prefix: r!

# Correct
r!play song name

# Incorrect
!play song name
/play song name

2. Check bot status: Ensure the bot is online (green/idle status)
3. Verify permissions: Bot needs “Read Messages” and “Send Messages” permissions
4. Check token: Verify your .env file has the correct Discord token

TOKEN=your_actual_token_here

5. Console logs: Check the bot’s console for error messages
6. Test with r!help: Try the help command to see if the bot responds at all

​

Problem

​

Solutions

1. Check embed permissions: Bot needs “Embed Links” permission
2. Verify channel permissions: Ensure bot can send messages in that specific channel
3. Check message filters: Some servers have automated moderation bots that might delete bot messages

​

Problem

​

Common Scenarios

​

Can’t Join Voice Channel

• Connect
• Speak
• Use Voice Activity

1. Right-click the voice channel
2. Edit Channel → Permissions
3. Add bot’s role with Connect and Speak permissions

​

Can’t Send Messages

• Send Messages
• Embed Links

1. Check channel permissions
2. Ensure bot’s role has “Send Messages” and “Embed Links”

​

Can’t See Commands

• Read Messages/View Channels

1. Enable “View Channel” for bot’s role in channel settings

​

Problem

​

Solutions

1. Check voice channel permissions:
   • Right-click voice channel → Edit Channel
   • Go to Permissions tab
   • Ensure bot role has “Connect” enabled
2. Check user limit: If the channel is full, the bot can’t join
3. Region restrictions: Some voice channels may have region locks
4. Role hierarchy: Ensure bot’s role isn’t restricted by higher roles

​

Problem

​

Solutions

1. Check Speak permission: Verify bot has “Speak” permission
2. Verify FFmpeg: Ensure FFmpeg is properly installed

ffmpeg -version

3. Check Discord voice settings:
   • User Settings → Voice & Video
   • Ensure correct output device is selected
   • Check if Discord is muted
4. Restart voice connection:

r!stop
# Rejoin voice channel and try again
r!play song name

5. Check voice dependencies: Look at console logs for voice dependency report

​

Problem

​

Possible Causes

1. Network instability: Poor internet connection
2. Discord API issues: Temporary Discord outages
3. Server region: Voice server latency
4. Memory issues: Bot running out of memory

​

Solutions

1. Check network: Ensure stable internet connection
2. Monitor resources: Check CPU and memory usage
3. Update dependencies:

npm update

4. Increase event listeners (already configured in the bot):

require('events').EventEmitter.defaultMaxListeners = 15;

​

Problem

​

Solutions

1. Check Discord status: Visit Discord Status
2. Verify network: Ensure ports aren’t blocked by firewall
3. Update @discordjs/voice:

npm update @discordjs/voice

4. Check voice dependencies: The bot logs dependency report on startup
5. Reinstall voice dependencies:

npm install --save @discordjs/voice

​

Problem

​

Solutions

1. Use URLs when possible: Direct YouTube URLs don’t require search API calls

# Preferred for frequent use
r!play https://youtube.com/watch?v=VIDEO_ID

# Uses API quota
r!play song name

2. Verify API key: Ensure your YouTube API key is valid
3. Check quota: Visit Google Cloud Console to check your API quota
4. Request quota increase: If needed, request higher quota limits from Google

​

Problem

​

Solutions

1. Verify credentials: Check .env file has correct Spotify Client ID and Secret

SPOTIFY_CLIENT_ID=your_client_id
SPOTIFY_CLIENT_SECRET=your_client_secret

2. Test credentials: Verify they work on Spotify Dashboard
3. Check Spotify status: Visit Spotify Status
4. Reinstall plugin:

npm uninstall @distube/spotify
npm install @distube/spotify

​

Problem

​

Causes

• Too many commands sent too quickly
• Multiple bots on same token (don’t do this)
• Bot in too many servers with same infrastructure

​

Solutions

1. Implement cooldowns: Add command cooldowns (if needed)
2. Avoid spam: Don’t send commands repeatedly
3. Check for loops: Ensure bot isn’t stuck in a command loop
4. Monitor console: Look for rate limit warnings

​

Problem

​

Solutions

1. Verify file location: .env must be in the root directory

RosyMusicBot_estable/
├── .env          ← Must be here
├── index.js
├── package.json
└── ...

2. Check file format: No spaces around =

# Correct
TOKEN=abc123

# Incorrect
TOKEN = abc123

3. No quotes needed: Don’t wrap values in quotes

# Correct
TOKEN=NzkyNzE1NDk0MDk2Njk0Mjgy

# Incorrect  
TOKEN="NzkyNzE1NDk0MDk2Njk0Mjgy"

4. Restart bot: Changes require bot restart

​

Problem

​

Solutions

1. Regenerate token:
   • Go to Discord Developer Portal
   • Select your application
   • Bot section → Reset Token
   • Copy new token to .env
2. Check for spaces: Ensure no extra spaces in token
3. Verify token format: Discord bot tokens are long alphanumeric strings

​

Problem

​

Solutions

1. Be more specific: Include artist name

# Better
r!play imagine dragons believer

# Less specific
r!play believer

2. Use direct URL: Most reliable method
3. Check play-dl: The bot uses play-dl for searching; ensure it’s installed

npm list play-dl

4. Try different search terms: Use alternative song titles

​

Problem

​

Explanation

​

Solutions

1. Select faster: Menu timeout is 20 seconds
2. Use direct URLs: Skip search entirely
3. Be ready: Know which result you want before searching