You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I followed instructions from the README file, and looked at other issues asking to test changing the server port.
I made my server port and redirection url port in the webapp match (using localhost:5009 for both), and when I do so, spotify just doesn't really redirects back to localhost:5009, and prints the following error on a blank page: INVALID_CLIENT: Invalid redirect URI.
I though this was some regex match on localhost to prevent such redirects, and edited my /etc/hosts file to make a random domain name redirect to localhost, without success.
Could you confirm that the tool is still working ? Is this a known issue ?
Thanks for your time !
The text was updated successfully, but these errors were encountered:
Hello, Invalid redirect URI would be because the link that the application wants to redirect to is different than the one setup in the Spotify Developer settings
Try tinkering with that
The current version of the application has been rather unmaintained for 2 years as it just *worked*, I have lost knowledge of the application and plannong to work on a new version soon tm to give appropriate support
Hi, I followed instructions from the README file, and looked at other issues asking to test changing the server port.
I made my server port and redirection url port in the webapp match (using localhost:5009 for both), and when I do so, spotify just doesn't really redirects back to localhost:5009, and prints the following error on a blank page: INVALID_CLIENT: Invalid redirect URI.
I though this was some regex match on localhost to prevent such redirects, and edited my /etc/hosts file to make a random domain name redirect to localhost, without success.
Could you confirm that the tool is still working ? Is this a known issue ?
Thanks for your time !
The text was updated successfully, but these errors were encountered: