fix(music): add spotify-tokener with Chromium for Partner API anonymous tokens
Spotify changed their API in Feb 2026 - playlists now require anonymous tokens via the Partner API. The default anonymous token endpoint is blocked from server IPs. Added a custom Dockerfile for spotify-tokener with Chromium installed, and configured LavaSrc to use Partner API with the tokener endpoint. Playlists now load successfully.
This commit is contained in:
parent
9aebef15e1
commit
af88cea301
3 changed files with 20 additions and 2 deletions
6
lavalink/Dockerfile.tokener
Normal file
6
lavalink/Dockerfile.tokener
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
FROM ghcr.io/topi314/spotify-tokener:master
|
||||
RUN apt-get update && \
|
||||
apt-get install -y --no-install-recommends chromium && \
|
||||
rm -rf /var/lib/apt/lists/*
|
||||
ENV SPOTIFY_TOKENER_CHROME_PATH=/usr/bin/chromium
|
||||
ENV CHROMIUM_FLAGS="--no-sandbox --disable-gpu --headless"
|
||||
Loading…
Add table
Add a link
Reference in a new issue