[GH-ISSUE #1070] Worked, but now constant 403 #488

Open
opened 2026-02-28 14:49:27 +03:00 by kerem · 4 comments
Owner

Originally created by @leobergamo on GitHub (Jan 28, 2023).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1070

Hello,

So I successfully installed spotify-tui yesterday. I used spotifyd as the backend. It worked, after some configuring flawlessly. Now, the following morning; I am receiving constant 403 errors from spotify-tui upon startup. I verified spotifyd still starts and runs as before without error, so my deduction is the fault lays somewhere in spotify-tui.

As a side note, I did notice prior, that when spotifyd is not ran in daemon mode with verbose output on; you could see interaction between it and spotify-tui on the console; now no such interaction occurs.

Could this be some sort of "disconnect" locally between spotify-tui and spotifyd ? I don't know, I am lost; I scoured spotify-tui's, spotifyd's and spotify's developer api forums to no avail.

Please advise...

Regards,

Leo C. Bergamo

P.S.

Great work on the TUI though!

Originally created by @leobergamo on GitHub (Jan 28, 2023). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/1070 Hello, So I successfully installed spotify-tui yesterday. I used spotifyd as the backend. It worked, after some configuring flawlessly. Now, the following morning; I am receiving constant 403 errors from spotify-tui upon startup. I verified spotifyd still starts and runs as before without error, so my deduction is the fault lays somewhere in spotify-tui. As a side note, I did notice prior, that when spotifyd is not ran in daemon mode with verbose output on; you could see interaction between it and spotify-tui on the console; now no such interaction occurs. Could this be some sort of "disconnect" locally between spotify-tui and spotifyd ? I don't know, I am lost; I scoured spotify-tui's, spotifyd's and spotify's developer api forums to no avail. Please advise... Regards, Leo C. Bergamo P.S. Great work on the TUI though!
Author
Owner

@nim65s commented on GitHub (Jan 28, 2023):

Hi,

Same here. I've been using this for months, and now it's only:

Error: Spotify API error code 403: Player command failed: Restriction violated

<!-- gh-comment-id:1407380710 --> @nim65s commented on GitHub (Jan 28, 2023): Hi, Same here. I've been using this for months, and now it's only: > Error: Spotify API error code 403: Player command failed: Restriction violated
Author
Owner

@leobergamo commented on GitHub (Jan 29, 2023):

Hi,

Same here. I've been using this for months, and now it's only:

Error: Spotify API error code 403: Player command failed: Restriction violated

Hello,

Yeah most likely some sort of API change on Spotify's end. Sadly I we'll have to wait to see if the problem is resolved.

<!-- gh-comment-id:1407639222 --> @leobergamo commented on GitHub (Jan 29, 2023): > Hi, > > Same here. I've been using this for months, and now it's only: > > > Error: Spotify API error code 403: Player command failed: Restriction violated Hello, Yeah most likely some sort of API change on Spotify's end. Sadly I we'll have to wait to see if the problem is resolved.
Author
Owner

@leberknecht commented on GitHub (Jan 30, 2023):

I had the same, i was able to solve it: in my case i was using a sub-account of my family account for the API access, and the solution was to add the email of the root account in the list of allowed user for the sub account (spotify-developer Dashboard => select your app => "users and access").

I stumbled over this by using spotipy python packages and testing the API with a minimal snippet from their examples like

from spotipy.oauth2 import SpotifyOAuth
from pprint import pprint

scope = "user-read-playback-state,user-modify-playback-state"
sp = spotipy.Spotify(client_credentials_manager=SpotifyOAuth(scope=scope, open_browser=False))

# Shows playing devices
res = sp.devices()
pprint(res)

and env like

SPOTIPY_REDIRECT_URI=http://localhost:8888/callback
SPOTIPY_CLIENT_ID=...
SPOTIPY_CLIENT_SECRET=...

Hope that helps somehow.

<!-- gh-comment-id:1408432386 --> @leberknecht commented on GitHub (Jan 30, 2023): I had the same, i was able to solve it: in my case i was using a sub-account of my family account for the API access, and the solution was to add the email of the root account in the list of allowed user for the sub account (spotify-developer Dashboard => select your app => "users and access"). I stumbled over this by using `spotipy` python packages and testing the API with a minimal snippet from their examples like ```python from spotipy.oauth2 import SpotifyOAuth from pprint import pprint scope = "user-read-playback-state,user-modify-playback-state" sp = spotipy.Spotify(client_credentials_manager=SpotifyOAuth(scope=scope, open_browser=False)) # Shows playing devices res = sp.devices() pprint(res) ``` and env like ``` SPOTIPY_REDIRECT_URI=http://localhost:8888/callback SPOTIPY_CLIENT_ID=... SPOTIPY_CLIENT_SECRET=... ``` Hope that helps somehow.
Author
Owner

@sewnie commented on GitHub (Feb 18, 2023):

or use https://github.com/aome510/spotify-player

<!-- gh-comment-id:1435484795 --> @sewnie commented on GitHub (Feb 18, 2023): or use https://github.com/aome510/spotify-player
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#488
No description provided.