linuxserver / docker-daapd

GNU General Public License v3.0
103 stars 37 forks source link

Spotify Playback fails #53

Closed bakerboy908 closed 1 year ago

bakerboy908 commented 2 years ago

linuxserver.io


Expected Behavior

Music should play back

Current Behavior

No playback with internal server error when ever trying to play Spotify

Steps to Reproduce

  1. Authorise spotify
  2. Try to play back music
  3. internal server error

Environment

OS: CPU architecture: x86_64 How docker service was installed:

Installed from docker hub

Command used to create docker container (run/create/compose/screenshot)

daapd: image: ghcr.io/linuxserver/daapd container_name: daapd network_mode: host environment:

github-actions[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

BernsteinA commented 2 years ago

thanks, I think we may need a longer log from you to diagnose this. anybody else using spotify successfully with the latest image? (@bverhagen ?)

bakerboy908 commented 2 years ago

owntone.log Here is a current log

bverhagen commented 2 years ago

Owntone (forked-daapd) has changed its spotify client implementation in their master branch, I am currently in that one for testing purposes. As soon as they create a new release, it will automagically be included here too.

In the meantime, you can do similar changes as I did here: https://github.com/bverhagen/docker-daapd for aarch64 (you will want to change these in the ordinary Dockerfile). Follow the instructions in the Readme for building the container image yourself.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

bverhagen commented 2 years ago

In the latest version of this image ( 28.2-ls53 ), this should work for AArch64.

PR #55 removes the temporary Librespot workaround.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.