From ab125c48ac18540eaf7d54a4b6ae9e197492e819 Mon Sep 17 00:00:00 2001 From: Broque Thomas Date: Sat, 13 Sep 2025 09:41:56 -0700 Subject: [PATCH] Add Docker OAuth workaround instructions to README Added a section explaining how to complete Spotify OAuth authentication when accessing SoulSync remotely via Docker. This provides a workaround for Spotify's redirect URI restrictions and guides users through the necessary steps. --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index e253513a..ae55bb23 100644 --- a/README.md +++ b/README.md @@ -118,6 +118,19 @@ docker run -d -p 8008:8008 boulderbadgedad/soulsync:latest ``` - Uses separate database from GUI/WebUI versions +### Docker OAuth Fix (Remote Access) +If accessing SoulSync from a different machine than where it's running: + +1. Set your Spotify callback URL to `http://127.0.0.1:8888/callback` +2. Open SoulSync settings and click authenticate +3. Complete Spotify authorization - you'll be redirected to `http://127.0.0.1:8888/callback?code=SOME_CODE_HERE` +4. If the page fails to load, edit the URL to use your actual SoulSync IP: + - Change: `http://127.0.0.1:8888/callback?code=SOME_CODE_HERE` + - To: `http://192.168.1.5:8888/callback?code=SOME_CODE_HERE` +5. Press Enter and authentication should complete + +**Note**: Spotify only allows `127.0.0.1` as a local redirect URI, hence this workaround. You may need to repeat this process after rebuilding containers. + ## 🎯 Core Features **Search & Download**: Manual track search with preview streaming