From ccfca52e8d9ad1aeab657bfaadfe9885cd213b64 Mon Sep 17 00:00:00 2001 From: ejurgensen Date: Tue, 12 Jan 2021 23:20:22 +0100 Subject: [PATCH] [docs] Update README.md: troubleshooting Spotify OAuth redirect --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 4081636f..e2256ea7 100644 --- a/README.md +++ b/README.md @@ -494,6 +494,13 @@ Once the above is in order you can login to Spotify via the web interface. The procedure for logging in to Spotify is a two-step procedure due to the current state of libspotify, but the web interface makes both steps available to you. +Note that the address [http://forked-daapd.local:3689](http://forked-daapd.local:3689) +must be working on your local network to complete the Spotify OAuth web login. +The address is announced automatically via mDNS, but if that for some reason +doesn't work then configure it via router or .hosts file. You can remove it +again after completing the login. This is needed because the redirect_uri +parameter of the Spotify token request is to this address. + Spotify no longer automatically notifies clients about playlist updates, so you have to trigger updates manually. You can for instance set up a cron job that runs `/usr/bin/curl http://localhost:3689/api/update`