[GH-ISSUE #1053] INVALID_CLIENT: Invalid redirect URI #474

Closed
opened 2026-02-28 14:49:22 +03:00 by kerem · 8 comments
Owner

Originally created by @Autobeing on GitHub (Dec 13, 2022).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1053

I reinstalled Spotify-TUI and now when trying to start spt after correctly inserting Spotify creds and setting up redirect URI, I get this error every time from the link that opens in the browser and can't give permission to access the extension.

I have tried different ports, recreating the extension and tried connecting on three different computers. In the client.yml file the device_id is not filled in, I have never needed to set that up manually before and don't know what should be there, is there something I'm missing?

Originally created by @Autobeing on GitHub (Dec 13, 2022). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1053 I reinstalled Spotify-TUI and now when trying to start spt after correctly inserting Spotify creds and setting up redirect URI, I get this error every time from the link that opens in the browser and can't give permission to access the extension. I have tried different ports, recreating the extension and tried connecting on three different computers. In the client.yml file the device_id is not filled in, I have never needed to set that up manually before and don't know what should be there, is there something I'm missing?
kerem closed this issue 2026-02-28 14:49:23 +03:00
Author
Owner

@cyberfeign commented on GitHub (Dec 13, 2022):

I have the same issue! Did something change with how authentication works?

<!-- gh-comment-id:1347989719 --> @cyberfeign commented on GitHub (Dec 13, 2022): I have the same issue! Did something change with how authentication works?
Author
Owner

@mcopik commented on GitHub (Dec 16, 2022):

Same issue here - fresh install of spt, I followed default configuration steps, and I ended up with this error.

<!-- gh-comment-id:1355198250 --> @mcopik commented on GitHub (Dec 16, 2022): Same issue here - fresh install of spt, I followed default configuration steps, and I ended up with this error.
Author
Owner

@mcopik commented on GitHub (Dec 16, 2022):

@cyberfeign @Autobeing I resolved my issue - it seems that the callback URI was not added correctly in my Spotify settings. You must click both 'Add' and 'Save' in the settings window.

<!-- gh-comment-id:1355237277 --> @mcopik commented on GitHub (Dec 16, 2022): @cyberfeign @Autobeing I resolved my issue - it seems that the callback URI was not added correctly in my Spotify settings. You must click both 'Add' and 'Save' in the settings window.
Author
Owner

@Autobeing commented on GitHub (Dec 16, 2022):

I have verified the callback URI multiple times, and have tried with different ports. So it is not the same fix in my case, unfortunately.

<!-- gh-comment-id:1355249618 --> @Autobeing commented on GitHub (Dec 16, 2022): I have verified the callback URI multiple times, and have tried with different ports. So it is not the same fix in my case, unfortunately.
Author
Owner

@cyberfeign commented on GitHub (Dec 16, 2022):

I checked my URI and it seems to be correctly set up as well. I haven't been able to use spt at all for a month or so, really miss it.

<!-- gh-comment-id:1355262223 --> @cyberfeign commented on GitHub (Dec 16, 2022): I checked my URI and it seems to be correctly set up as well. I haven't been able to use spt at all for a month or so, really miss it.
Author
Owner

@lindblandro commented on GitHub (Dec 18, 2022):

Followed the instructions for a fresh install and encountered this. Adding http://localhost:8888/callback to redirect uri allowlist in the newly created spotify-tui application settings in spotify dashboard solved the "Invalid redirect URI" issue for me. Don't know if Spotify has changed this part of their authorization flow recently, but the installation instructions must be updated.

<!-- gh-comment-id:1356740753 --> @lindblandro commented on GitHub (Dec 18, 2022): Followed the instructions for a fresh install and encountered this. Adding `http://localhost:8888/callback` to redirect uri allowlist in the newly created spotify-tui application settings in spotify dashboard solved the "Invalid redirect URI" issue for me. Don't know if Spotify has changed this part of their authorization flow recently, but the installation instructions must be updated.
Author
Owner

@Autobeing commented on GitHub (Dec 18, 2022):

My URI has always been http://localhost:8888/callback, or with a different port, which I then of course changed in the spt config as well. Still does not work for me and I get the error regardless.

<!-- gh-comment-id:1356742134 --> @Autobeing commented on GitHub (Dec 18, 2022): My URI has always been `http://localhost:8888/callback`, or with a different port, which I then of course changed in the spt config as well. Still does not work for me and I get the error regardless.
Author
Owner

@Autobeing commented on GitHub (Dec 18, 2022):

I think there was something wrong with my Spotify account. I made a new one to get way from Facebook, and when I tried doing it exactly the same way with the new one, it worked. I am certain I set everything up correctly every time. No idea what could have been the issue with the account.

<!-- gh-comment-id:1356851680 --> @Autobeing commented on GitHub (Dec 18, 2022): I think there was something wrong with my Spotify account. I made a new one to get way from Facebook, and when I tried doing it exactly the same way with the new one, it worked. I am certain I set everything up correctly every time. No idea what could have been the issue with the account.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#474
No description provided.