Support & Feedback
If you encounter a bug, have a question, or want to request a feature, please use GitHub Issues. This keeps support transparent, traceable, and easier to improve over time.
Before opening a new issue, check the troubleshooting guides below. Many common incidents are already covered: device discovery, no audio, dropouts, metadata updates, and Spotify Connect instability.
Start here before opening an issue
Spotycast sits between Spotify, your Debian host, Icecast, and your playback stack. A useful support request usually starts by locating which layer is failing: Spotify Connect discovery, audio routing, Icecast publication, player playback, or metadata propagation.
Device not showing
Use this path if the Spotycast endpoint does not appear in Spotify or disappears after reboot.
No audio
Use this path if the stream URL exists but the player receives silence or nothing playable.
Dropouts or buffering
Use this path if playback starts but cuts, stutters, stalls, or becomes unstable over time.
Useful documentation links
These pages cover the core Spotycast workflow and help clarify whether the issue is installation-related, architecture-related, edition-related, or player-specific.
Installation guide
Use this as the single source of truth for deploying Spotycast on Debian.
How it works
Review the Spotify → Spotycast → Icecast → player chain before reporting architecture questions.
FAQ
Check scope, usage expectations, local-network assumptions, and common product boundaries.
What to include in a good bug report
A good issue should make the problem reproducible. Please include enough context to identify whether the failure comes from the host, the Spotycast service, Icecast, Liquidsoap, Spotify Connect discovery, or the consuming player.
- Spotycast edition: Free or Premium
- Installation environment: Debian version, VM, bare metal, NAS, Docker or other deployment mode
- Playback target: Roon, LMS / Lyrion, Volumio, moOde, VLC, browser, or another client
- What works and what fails: device visible, stream URL reachable, audio present, metadata correct, etc.
- Recent changes: update, reboot, container restart, network change, router change, or player update
- Relevant logs from the services involved
journalctl -u spotifyd -n 200 --no-pager journalctl -u liquidsoap -n 200 --no-pager journalctl -u icecast2 -n 200 --no-pager curl http://YOUR_HOST:YOUR_PORT/status-json.xsl
Feature requests
Feature requests are welcome, especially when they describe a real playback scenario rather than only a technical preference. The most useful requests explain the current limitation, the player involved, and the expected behavior.
Good feature request
“I use Spotycast with Roon and LMS. I need two endpoint profiles because one player prefers compatibility while the other benefits from a higher-end stream path.”
Less useful request
“Add more options.” Without environment, player, logs, or target behavior, it is hard to design something robust.
Premium access or purchase issue?
For Premium installation-key or customer-access questions, start from the Premium pages so the issue is framed correctly. GitHub remains useful for technical defects, but purchase or access context should be handled carefully and without posting private keys publicly.
Ready to open an issue?
Once you have checked the relevant guide and collected the basic context, open a GitHub issue. Clear issues make Spotycast easier to maintain and help other users facing the same Linux, Icecast, Roon, LMS, or Volumio edge cases.