Fixing the 7 Most Common Radio Streaming Errors: AutoDJ, Mount Points, Encoder Failures & More

Stream emergencies feel mysterious from inside and are almost never mysterious from outside. Across hundreds of diagnosed failures, the same seven errors account for nearly everything: a stale source connection squatting on your mount, AutoDJ silently not running, an encoder fighting its own password, listener slots exhausted, and the three flavors of "works for some listeners but not others." Here's each one, its signature, and its fix.

Error 1: "Mount Point In Use" / Source Rejected

Your encoder connects, gets kicked with "source already connected" or "mount in use." Signature: it happened right after a DJ software crash. The crashed connection didn't close cleanly, and the server still counts it as the live source — your reconnect is a duplicate, and duplicates get rejected.

1. 1Close your encoder software completely
2. 2In your panel (AzuraCast, Centova), stop and start the AutoDJ/service — this force-drops the stale source
3. 3No panel? Restart the Icecast/Shoutcast service over SSH, or ask your host to
4. 4Reconnect — the mount is free now

Error 2: Station Up, But Silent

Everything looks running, nothing plays. Check in this order — it's nearly always one of the first three:

1. 1Is the playlist actually populated with playable files? Some panels choke on odd MP3 tags — re-upload a known-good file and test
2. 2Is the AutoDJ service actually running? Panels have service status pages that lie by omission — check the service, not the dashboard
3. 3Is there a schedule gap? Many panels stop AutoDJ when no schedule entry matches the current time
4. 4Are you listening to the right mount? The web player and the AutoDJ sometimes point at different mounts
5. 5AzuraCast specifically: check the Liquidsoap log — a malformed playlist line fails silently and takes the automation with it

Error 3: Connect-Disconnect Loop

Encoder connects, drops after seconds, reconnects, drops, forever. This is almost never network trouble — it's authentication failing in a loop:

• Wrong password — or a password with characters the encoder mishandles; try a plain one
• Shoutcast v1 vs v2 protocol setting in the encoder pointing at the wrong version
• Username where the panel expects password-only (or the source username format)
• A panel IP allowlist blocking your own broadcast IP

Error 4: "Source at Maximum Listeners"

Your plan's listener slots are consumed — sometimes by listeners, often by things that aren't: website players stuck in reconnect loops, monitoring services polling too aggressively, bots hammering the stream URL. The source itself also counts as a slot on some plans. Look at your listener list before upgrading — if half your slots are eaten by one IP reconnecting every five seconds, that's a broken player, not a capacity problem. If the slots are genuinely full of humans: that's the good version of this problem, and the fix is a plan upgrade.

Error 5: Works for Some Listeners, Not Others

The most diagnostic-rich failure in streaming. Three usual suspects, each with a signature:

• "Works on my phone, not my laptop / at the office": port filtering — non-standard ports like 8000 get blocked by corporate and some carrier networks. Fix: reverse proxy on port 443
• "Works in the app, not the website": mixed content — an HTTP stream embedded on an HTTPS site is silently blocked by every modern browser. Fix: HTTPS the stream
• "Works on Android, not iPhone / in VLC but not on the Echo": codec — OGG and Opus play in desktop players and vanish on iOS and Alexa. Fix: add an MP3 or AAC mount

Error 6: Now-Playing Metadata Stuck

Audio is fine but the song title hasn't changed in an hour. Usually: ICY metadata updates disabled in the DJ software (SAM and Mixxx both have the switch), files with missing or malformed ID3 tags, or the panel's relay/update cycle stalled. Enable metadata, check tags, restart the panel's metadata service if it has one. Cosmetic-looking, but listeners use the now-playing display as proof the station is alive.

7. The Special Case: Everything Works Except Alexa

Browsers play it, VLC plays it, the phone plays it — the Echo is silent. This is Error 5's most common modern form, and it's almost always one of four:

1. 1The stream URL is HTTP — Amazon requires HTTPS; this is the majority of cases
2. 2The skill points at a redirect rather than the direct stream URL — Alexa follows redirects badly
3. 3The stream is OGG/Opus — Alexa plays MP3, AAC, and HLS only
4. 4The stream was down during certification testing — fix stability, resubmit after 24 clean hours

Notably, none of these are diagnosed by staring at the skill. They're diagnosed by looking at the stream — which is the theme of all seven errors in this guide. The stream tells the truth; check it first, and most "mysterious" failures identify themselves in ten minutes.