Playback help
Secure playback & FAQ
Mixed-content-safe listening, session protection, and what to do when playback fails.
Technical transparency
dRadio is built to make station pages actually playable in modern browsers. Many stations still publish legacy
http:// stream URLs, and browsers may block those streams when you’re browsing a secure https:// site.
Mixed-content-safe playback
Where needed, dRadio routes legacy streams through a secure HTTPS gateway so the player can start without mixed-content errors. Direct HTTPS station streams still play directly when they are already browser-safe; the gateway is a compatibility layer, not a replacement for healthy station infrastructure.
Playback badges on station pages
Station pages use compact trust badges to explain the selected stream: Recently checked means a fresh stream check passed, Direct secure stream means the station already exposes HTTPS audio, and Secured by dRadio means the secure gateway can protect playback for a legacy HTTP stream.
Session-based protection
Playback is started via a short-lived, listener-specific session. Sessions use expiring signed URLs and a small first-party proof cookie, so copied play URLs cannot be reused as an open proxy.
Privacy note
When a stream is proxied, the upstream broadcast server sees the dRadio gateway IP address rather than your client IP. Stations that support secure HTTPS streams directly may play without proxying.
Corrections & station owner requests
Station metadata changes over time. If you own or represent a station, use the station correction and claim request flows from the station page. Listener-facing health totals are summarized on the directory stats page, and the station directory can be filtered to currently playable stations.
Browse by playback confidence
Use these crawlable shortcuts to find stations that are more likely to start cleanly, then return here when you want the technical details.
Troubleshooting FAQ
Common playback issues and quick fixes.
Why won’t a station play?
- The station may be offline or rate-limiting connections.
- The station may have changed its stream URL.
- Your listening session may have expired.
- A browser extension may be blocking the player request.
What does “session expired” mean?
Listening sessions are time-limited. Click Listen again, or refresh the page, to start a new session.
Why does it work here but not on other directories?
Many directories link directly to legacy HTTP streams. dRadio supports mixed-content-safe playback where needed.
Can an ad blocker break playback?
Some aggressive blockers can misclassify audio gateways or API requests. Allow this site and retry.
What do the playback badges mean?
- Recently checked: the selected stream has a fresh healthy check.
- Direct secure stream: the station already serves HTTPS audio directly.
- Secured by dRadio: dRadio can use its HTTPS gateway for a legacy HTTP stream.
Mobile playback stops when I lock my phone
Some mobile power-saving modes suspend background tabs. Keep the browser/player active where possible.