[GH-ISSUE #181] Spotify down and service fail #117

New issue

Closed

opened 2026-02-28 14:25:29 +03:00 by kerem · 1 comment

kerem commented

2026-02-28 14:25:29 +03:00

Owner

Originally created by @ceck90 on GitHub (Apr 16, 2025).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/181

Due to today Spotify down, go-libre spot service fail with error:

time="2025-04-16T13:15:10Z" level=fatal msg="failed running zeroconf" error="failed getting endpoints from resolver: invalid status code from apresolve: 502"

It is possible to handle this exception to avoid service fail and restart loop?

Originally created by @ceck90 on GitHub (Apr 16, 2025). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/181 Due to today Spotify down, go-libre spot service fail with error: time="2025-04-16T13:15:10Z" level=fatal msg="failed running zeroconf" error="failed getting endpoints from resolver: invalid status code from apresolve: 502" It is possible to handle this exception to avoid service fail and restart loop?

kerem closed this issue

2026-02-28 14:25:29 +03:00

kerem commented

2026-02-28 14:25:30 +03:00

Author

Owner

@devgianlu commented on GitHub (Apr 17, 2025):

go-librespot needs to connect to these services to function. If Spotify breaks something we must keep trying. You can adjust your systemd service to set a restart limit or delay.

@devgianlu commented on GitHub (Apr 17, 2025): go-librespot needs to connect to these services to function. If Spotify breaks something we must keep trying. You can adjust your systemd service to set a restart limit or delay.

kerem referenced this issue

2026-02-28 14:26:17 +03:00

[PR #117] [MERGED] fix: initialize vorbis stream on the first read #219