Spotify to Icecast: restore playback on legacy Linux streamers
Spotify Connect stopped working on your older streamer? Your DAC and network player may still perform perfectly. Spotycast Classic moves the Spotify-facing endpoint to a separate Debian/Linux host, then publishes a stable Icecast HTTP radio URL that compatible players can open without relying on outdated firmware.
How Spotify to Icecast works
The legacy device no longer needs its own working Spotify Connect integration. A maintained Linux bridge receives Spotify-controlled playback and makes the audio available through a conventional HTTP stream on your LAN.
Why use an Icecast bridge instead of replacing your streamer?
Keep capable audio hardware
A functioning streamer, DAC or renderer can remain part of your system even when its Spotify plugin is no longer maintained.
Recover a familiar radio input
Roon Live Radio and other HTTP-compatible receivers can reuse an Icecast stream URL without native Spotify firmware support.
Isolate the software problem
The Spotify-facing component runs on a separate maintained Linux host, keeping device compatibility and audio playback concerns distinct.
A bridge is appropriate after checking that the failure is not simply a local network, multicast discovery or output-device problem. Start with Spotify Connect troubleshooting before replacing an otherwise repairable configuration.
Which players can open the Icecast URL?
Compatibility depends on the receiving protocol and supported codec of your particular player, not only on its brand.
Roon
Add your configured Icecast mountpoint as a radio source through Roon Live Radio, subject to supported stream formats.
LMS / Lyrion
Use a network radio URL with a compatible LMS/Squeezebox player to reach the Icecast endpoint on the local network.
Volumio and moOde
Use a supported radio or HTTP stream input instead of depending on a failed native Spotify integration.
Install and verify the Spotify to Icecast bridge
Use the Spotycast installation guide for your release and configuration. These checks help identify which part of the chain needs attention.
- Deploy the bridge on a supported Linux hostFollow the documented installation process on Debian/Linux. Keep the bridge distinct from an old streamer whose Spotify integration is no longer supported.
- Check the actual service or container statusFor systemd, use
systemctl status <service>andjournalctl -u <service> -n 80 --no-pager. For Docker, checkdocker psanddocker logs --tail 80 <container>. Names vary by installation. - Verify the Icecast URL and formatConfirm the Icecast hostname, port, mountpoint and codec in your installed configuration. Do not assume another installation’s example URL will work unchanged.
- Test end-to-end playbackSelect the bridge in Spotify, then open the configured HTTP radio endpoint in your receiver. If the device is visible but silent, distinguish audio-routing problems from network or codec support.
http://your-server:28000/spotify.aacThe port, mountpoint and AAC extension shown here are examples, not universal Spotycast defaults. Use the URL produced by your installation.Audio quality, buffering and the Classic/Premium difference
Spotify to Icecast / HTTP radio
- Spotify Connect input through spotifyd
- Liquidsoap routing and an Icecast HTTP endpoint
- Compressed Spotify source, up to approximately 320 kbps depending on configuration
- Radio-stream buffering and receiver-dependent latency
Dedicated renderer backend
- Soloist and PipeWire architecture
- Dedicated compatible Roon, LMS, MPD or OpenHome backends
- Potentially lossless-capable path, subject to Spotify availability and end-to-end support
- Additional installation and API-key requirements
Premium is not simply a higher-bitrate Icecast stream. Neither edition guarantees bit-perfect output, zero latency or universal hardware compatibility.