BUTT Encoder Keeps Disconnecting? (August 2026) Here’s How to Fix It

If your BUTT encoder keeps disconnecting, the problem almost always traces back to one of five things: incorrect server credentials, a misconfigured audio device, network or firewall interference, codec mismatch, or signal detection settings that are too aggressive. The fastest fix is to verify your server address, port, and password, then confirm your audio input device is actually delivering signal before BUTT tries to connect.

BUTT (Broadcast Using This Tool) is a free, open-source streaming encoder that sends live audio from your computer to Icecast, SHOUTcast, or WebRTC servers. When it works, it works beautifully. When it doesn’t, the connection drops after anywhere from a few seconds to several minutes of streaming, leaving your listeners with silence or your station’s auto DJ fallback.

I have helped dozens of internet radio broadcasters troubleshoot exactly this problem over the past few years, and I’ve compiled everything that actually works into this guide. We will walk through every common cause of BUTT disconnections, from the quick two-minute fixes to the deeper configuration changes that most guides skip entirely.

What Is BUTT Encoder and Why Does It Keep Disconnecting?

BUTT encoder is a lightweight audio streaming application developed by Daniel Noethen that captures sound from your microphone, line input, or system audio, encodes it using your chosen codec, and sends it to a remote broadcasting server. It is widely used for internet radio, DJ live sets, podcast streaming, and online broadcasting.

When BUTT keeps disconnecting, it means the connection between your computer and the streaming server is being interrupted repeatedly. The disconnect can happen because the server rejects your credentials, because no audio signal is reaching the encoder, or because something in your network path is dropping the connection.

Here are the most common causes of BUTT disconnections, ranked by how frequently they show up in forums and support requests:

• Wrong server settings: Incorrect address, port, password, or mount point for Icecast or SHOUTcast servers.

• No audio signal detected: BUTT fails the handshake or disconnects when it cannot detect audio input on the selected device.

• Network or firewall blocks: Firewalls, antivirus software, or router settings blocking the outbound connection port.

• Codec and bitrate mismatch: Server expects a different codec or bitrate than what BUTT is configured to send.

• Signal detection threshold: BUTT’s signal detection feature drops the connection when audio drops below the threshold.

• Windows power management: The operating system puts the sound card or network adapter to sleep mid-stream.

• Outdated BUTT version: Older versions have known bugs related to VBR encoding and reconnection behavior.

• Server-side limits: Your Icecast or SHOUTcast server has connection limits, timeout settings, or competing sources.

One Reddit user on r/radio described the frustration perfectly: they had been using BUTT for two years without issues, then suddenly it would connect for one second before dropping to the auto DJ for ten seconds, cycling endlessly. That pattern points to a signal detection or server-side source switching issue, which we will cover in detail below.

Check Your Server Settings First (Port, Password, and Address)

The most common reason BUTT cannot maintain a connection is a server configuration error. Before touching any audio or network settings, double-check every field in your BUTT server settings against what your hosting provider gave you.

Here is exactly what to verify, field by field:

1. Type: Select Icecast or SHOUTcast depending on your server. Picking the wrong one will cause an immediate or delayed connection failure.

2. Server address: Enter the hostname or IP address exactly as provided. Do not include the http:// prefix or a trailing slash.

3. Port: Most Icecast servers use port 8000, but your provider may assign a different port. Verify this carefully.

4. Password: Use your DJ or source password, not your admin password. These are often different on Icecast servers.

5. Mount point: For Icecast, this usually looks like /stream, /live, or /mount. For SHOUTcast, this field is not used.

6. Icecast user: Leave as “source” unless your provider specifies otherwise. This is a frequent stumbling block for LibreTime and Airtime users.

One LibreTime forum user reported that their port seemed to get stuck in an open position, preventing reconnection. The server thought the old connection was still alive, so it refused the new one. If this happens to you, ask your hosting provider to manually kill the old connection from the server side, or wait a few minutes for the server timeout to release it before reconnecting.

If you see a “404 not found” or “Connection refused” error in BUTT’s connection log, it almost always means one of these fields is wrong. Verify the port and password first, since those are the two most commonly misconfigured values.

Fix Audio Device Configuration Issues in BUTT

BUTT needs a live audio signal on its input device to establish and maintain a connection. If no audio is flowing, BUTT may fail the initial handshake or disconnect after a few seconds. Radio.co’s help documentation specifically notes that you need to be playing audio or have a live feed to connect successfully.

Here is how to configure your audio settings correctly in BUTT’s Audio tab:

1. Audio device: Select your actual input device (microphone, USB interface, or virtual cable). If BUTT shows “Could not open audio device,” another application may be blocking exclusive access.

2. Channel: Set to Stereo for music streaming or Mono for talk radio. If you are getting dropouts, try toggling between Mono and Stereo to force BUTT to reinitialize the audio device.

3. Sample rate: Set to 44100 Hz for most setups. Mismatched sample rates between BUTT and your audio device cause intermittent disconnections.

4. Signal detection: If enabled, BUTT will disconnect when audio drops below a threshold. Disable this temporarily while troubleshooting.

The audio settings toggle trick is one of the most reliable workarounds in the BUTT community. A SourceForge user discovered that when their level meters went dark and BUTT stopped streaming, simply toggling the Channel setting between Mono and Stereo caused BUTT to reconnect immediately. This works because it forces BUTT to reinitialize the PortAudio backend and re-open the device.

If BUTT shows connected but no audio is actually reaching your listeners, the problem is your input device selection. Check that the correct device is selected and that your audio source (DJ software, microphone, instrument) is actually sending signal. Watch the VU meters in BUTT’s main window to confirm audio is flowing.

On Windows, exclusive mode can cause conflicts. Right-click your speaker icon, open Sound settings, select your recording device, click Properties, and uncheck “Allow applications to take exclusive control of this device” under the Advanced tab.

Resolve Network and Firewall Problems Blocking BUTT

Even with perfect server and audio settings, your network can block BUTT’s outbound connection. Firewalls, antivirus software, and router configurations are frequent culprits, especially after system updates that reset firewall rules.

Here is how to identify and fix network-level issues:

1. Test with firewall disabled: Temporarily disable your Windows Defender Firewall, third-party firewall, or antivirus web shield. If BUTT stays connected, you have found the problem. Re-enable your firewall and create a specific exception for BUTT.

2. Add a firewall exception: In Windows Defender Firewall, go to “Allow an app through firewall” and add BUTT to both private and public network exceptions.

3. Check router port blocking: Some routers or ISPs block outbound traffic on non-standard ports. If your server uses port 8000 or another uncommon port, verify your router is not blocking it.

4. Test on a different network: Connect through a mobile hotspot or a different Wi-Fi network. If BUTT works there, the problem is your primary network’s configuration.

5. Check for VPN interference: VPNs can route streaming traffic through servers that block or throttle non-standard ports. Disconnect your VPN and test again.

For Linux users running BUTT on a server, the UFW firewall is a common blocker. Run sudo ufw allow [your-port]/tcp to open the connection port. The LibreTime forum identified UFW as the cause of a user’s intermittent connection issues, where BUTT would connect for about four minutes and then drop.

Network latency and packet loss also contribute to disconnections. If your internet connection is unstable, BUTT’s auto-reconnect feature may be constantly cycling. Run a speed test and a ping test to your streaming server to check for high latency or packet loss. Ideally, your ping to the server should be under 100ms with zero packet loss.

Adjust Codec and Bitrate Settings for Stable Streaming

Codec and bitrate settings must match what your server expects. If your Icecast or SHOUTcast server is configured for MP3 at 128 kbps and you send AAC+ at 64 kbps, the server may reject the stream after the handshake, causing BUTT to appear connected briefly before disconnecting.

Here is how to configure codec settings for maximum stability:

1. Match the server codec: Check with your hosting provider which codecs your server supports. Common options are MP3, AAC+ (also called HE-AAC or FDK-AAC), Vorbis, and Opus.

2. Match the bitrate: Set BUTT’s bitrate to exactly what your server expects. For MP3, 128 kbps or 192 kbps are standard for music. For AAC+, 64 kbps delivers quality similar to 128 kbps MP3.

3. Set the correct sample rate: Most servers expect 44100 Hz. If you set 48000 Hz and the server expects 44100 Hz, some servers will accept the stream but listeners will experience artifacts.

4. Avoid VBR mode if unstable: Variable Bitrate mode can cause issues with some servers. The official BUTT changelog notes a bug in older versions where VBR mode used the min bitrate value for the upper limit instead of the max bitrate. Update to the latest version if you use VBR.

5. Check channels setting: Set to Stereo for music, Mono for voice. Mismatched channel counts between BUTT and the server can cause connection drops.

If you recently changed your server plan or switched hosting providers, re-confirm your codec settings. Server configurations change, and what worked on your old provider may not match the new one.

Configure Signal Detection and Auto-Reconnect Settings

BUTT has a built-in signal detection feature that monitors your audio input. If the audio level drops below a threshold for too long, BUTT will disconnect from the server automatically. This prevents dead air when your audio source fails, but if the threshold is set too high or your audio has quiet passages, BUTT will keep disconnecting during low-volume moments.

Here is how to configure these settings properly:

1. Disable signal detection while troubleshooting: Open BUTT settings, go to the Streaming tab, and uncheck “Signal detection” entirely. If BUTT stays connected, this was your problem.

2. Lower the threshold: If you want to keep signal detection on, lower the threshold slider so quiet passages do not trigger a disconnect. Test with your typical audio levels.

3. Enable auto-reconnect: Make sure auto-reconnect is enabled. This feature automatically re-establishes the connection if it drops, minimizing downtime.

4. Set auto-reconnect interval: A 5 to 10 second reconnect interval works well. Too short and the server may not have released the old connection yet; too long and your listeners experience extended silence.

5. Keep streaming during silence: If your broadcast has intentional quiet moments, disable signal detection entirely and rely on your server’s auto DJ fallback instead.

The “connected for one second then drops” pattern reported by the Reddit user is a classic signal detection issue. BUTT connects, detects that the audio level is below threshold, and immediately disconnects. The server’s auto DJ then kicks in, and the cycle repeats every few seconds.

Common BUTT Error Messages and How to Fix Each One

Here are the error messages you are most likely to see in BUTT’s connection log, along with what each one means and how to fix it:

“Connection refused” means BUTT reached the server but the server actively rejected the connection. Check your port number, password, and server type (Icecast vs SHOUTcast). This is the single most common error, and the cause is almost always a wrong port or password.

“Could not open audio device” means BUTT cannot access your microphone or input device. Close other applications that might be using the audio device, check your operating system’s microphone privacy settings, and verify the correct device is selected in BUTT’s Audio tab.

“404 not found” on Icecast means your mount point is incorrect or does not exist on the server. Verify the mount point with your hosting provider and make sure you are connecting to the right server instance.

“Login failed” or “Invalid password” means your credentials are wrong. Double-check that you are using the source or DJ password, not the admin password. For Icecast, the username is typically “source.”

“Handshake failed” means BUTT connected but could not complete the protocol negotiation. This usually indicates a codec mismatch or a server type mismatch (trying to connect to Icecast with SHOUTcast settings or vice versa).

“Server is full” or “Mount in use” means another source is already connected to the same mount point. This happens when a previous BUTT instance is still connected or did not disconnect cleanly. Wait a few minutes for the server timeout to release the connection, or ask your provider to clear it.

Windows 10 and Windows 11 Specific BUTT Issues

Windows updates have a well-documented history of breaking BUTT. An internet-radio.com forum user reported that after installing a Windows 10 update, everything else worked fine but BUTT refused to connect at all. This happens because updates can reset audio driver permissions, change firewall rules, and alter power management settings.

Here is how to fix Windows-specific BUTT problems:

1. Check Windows microphone privacy settings: Go to Settings, Privacy, Microphone, and make sure “Allow apps to access your microphone” is enabled and BUTT is in the allowed list.

2. Disable audio exclusive mode: Open Sound settings, find your recording device, click Properties, go to the Advanced tab, and uncheck exclusive mode.

3. Prevent Windows from putting your sound card to sleep: Open Device Manager, find your audio device under Sound controllers, right-click, select Properties, go to the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.” One forum user identified this as the cause of their random disconnections.

4. Update your audio drivers: Download the latest drivers from your audio interface manufacturer. Generic Windows drivers can cause intermittent audio device access issues.

5. Re-add BUTT to firewall exceptions: After a Windows update, remove and re-add the BUTT firewall exception. Updates can corrupt existing rules.

6. Run BUTT as administrator: Right-click the BUTT executable and select “Run as administrator.” This resolves permission issues that prevent BUTT from accessing audio devices and network ports.

If none of these steps work, try a clean reinstall. Download the latest version from the official BUTT website at danielnoethen.de, completely remove the old installation, and install fresh. This eliminates corrupted configuration files that can cause persistent connection issues.

Frequently Asked Questions

Conclusion

Fixing a BUTT encoder that keeps disconnecting comes down to working through the causes methodically: start with server credentials, then audio device settings, then network and firewall configuration, then codec and bitrate matching, and finally signal detection and power management. The vast majority of disconnection problems are solved within the first two or three steps.

If you have tried every fix in this guide and BUTT still keeps disconnecting, the issue is likely server-side. Contact your streaming host and ask them to check their logs for your connection attempts. Their server logs will show exactly why the connection is being dropped, whether it is a source conflict, a timeout setting, or a configuration issue on their end.

Always run the latest version of BUTT from the official site, since Daniel Noethen regularly fixes connection-related bugs in updates. A quick update has solved more BUTT streaming problems than any other single action.