Flute Music

Troubleshooting Guide

Fix common Flute Music Bot issues

Use this page when you face no sound, lag, command errors, wrong results, or stuck queue problems in Discord.

Start with the symptom that matches your server, then run the recovery steps in order.

Written and tested by Reddy, Flute owner ยท Reviewed July 21, 2026

No sound in voice channel

Check if Flute has Connect and Speak permissions in the same voice channel as the requester.

Make sure your Discord user is not server-muted and the bot volume is normal with fvolume 80.

  • Run fnowplaying to confirm a track is actually active.
  • Look for channel-specific permission denies on the voice channel.
  • Disconnect and invite the bot again if it joined the wrong room.

Command not responding

Verify the channel allows Flute to read messages, send messages, embed links, and use application commands.

Run fhelp to test a simple bot response before testing music playback.

  • Use the default prefix f if slash commands are not visible yet.
  • Check whether another moderation bot is deleting bot responses.
  • Try the command in a different channel where Flute has full access.

Queue stuck or skipping unexpectedly

Use fstop, then start again with fplay.

Reset effects using fclearfilters if audio pipeline feels unstable.

  • Use fqueue to check whether there are still tracks waiting.
  • Use fremove number for a broken queue item instead of clearing everything.
  • Use fshuffle only after confirming the queue has the right tracks.

Wrong song results

Search with cleaner keywords: artist + title.

Use a direct URL when exact match is required.

  • Avoid one-word searches for popular song titles.
  • Add artist name, remix name, or language when results are similar.
  • Clear the wrong result with fskip or fremove number.

Lag, buffering, or delayed responses

Temporary lag can come from Discord voice routing, music source rate limits, network spikes, or a busy server queue. First lower the number of active effects, then test one short track before rebuilding a long queue.

  • Run fclearfilters and fcleareffects to remove extra audio processing.
  • Use fstop and start with a single track if the queue has many old entries.
  • Check the website live status section to see if the bot is publishing fresh stats.

Premium or 24/7 mode not working

Premium checks depend on Discord login, payment status, and the server/user relationship stored by the bot. If a payment was recent, open the dashboard after login and confirm the plan state before retrying the command.

  • Run fpremium in Discord to see current premium status.
  • Use the dashboard to verify the account connected to Discord.
  • Ask support with Discord user ID and payment time if activation does not appear.

Fast recovery checklist

1

Confirm permissions

Check Connect, Speak, Send Messages, Embed Links, and Use Application Commands.

2

Test a simple command

Run fhelp. If this fails, fix text permissions before testing music.

3

Restart playback state

Run fstop, then use fplay artist title with a clear search term.

4

Remove audio effects

Run fclearfilters and fcleareffects if sound is distorted or silent.

What to send support

If the issue remains after the checklist, join the support server and include useful details so the problem can be reproduced quickly. Clear information avoids repeated questions and helps separate permission issues from playback provider issues.

  • Your Discord server ID and the channel where the command was used.
  • The exact command you ran, for example fplay artist title.
  • The visible error message or a screenshot of the bot response.
  • Whether the problem happens with every song or only one source/link.
  • Whether premium, 24/7 mode, filters, or playlist commands were involved.

Need full command reference?

Use setup and command guides to avoid repeat issues.

Open Commands Guide Open Setup Guide