[GH-ISSUE #615] Player not starting... #359

Closed
opened 2026-03-02 23:46:52 +03:00 by kerem · 7 comments
Owner

Originally created by @gand0rf on GitHub (Nov 26, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/615

So, long story short. Upgraded system, moved files over to nvme, and have been working on getting things set back up. Got spotify_player working again a couple of days ago. Get a message from Spotify this morning that they noticed "sus" activity and changed my password for me. Got my password updated. Now spotify player will not start even after re-registering with my account.

Error:

Error: initialize new Spotify session

Caused by:
    0: new streaming connection
    1: initialize spirc
    2: Permission denied { Login failed with reason: Bad credentials }

I have been working on trying to figure this out. going so far as to create a new app on spotify to get a new client ID.
I also tried using the ID form the docs, but nothing. Looked around for a bit but didn't find anything that helped.

OS: Xubuntu 24.04
Version: 0.20.1

Originally created by @gand0rf on GitHub (Nov 26, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/615 So, long story short. Upgraded system, moved files over to nvme, and have been working on getting things set back up. Got spotify_player working again a couple of days ago. Get a message from Spotify this morning that they noticed "sus" activity and changed my password for me. Got my password updated. Now spotify player will not start even after re-registering with my account. Error: ``` Error: initialize new Spotify session Caused by: 0: new streaming connection 1: initialize spirc 2: Permission denied { Login failed with reason: Bad credentials } ``` I have been working on trying to figure this out. going so far as to create a new app on spotify to get a new client ID. I also tried using the ID form the docs, but nothing. Looked around for a bit but didn't find anything that helped. OS: Xubuntu 24.04 Version: 0.20.1
kerem 2026-03-02 23:46:52 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@aome510 commented on GitHub (Nov 27, 2024):

try to re-authenticate the application with spotify_player authenticate or delete the cached credentials.json in ~/.cache/spotify_player then re-run the app

<!-- gh-comment-id:2504090595 --> @aome510 commented on GitHub (Nov 27, 2024): try to re-authenticate the application with `spotify_player authenticate` or delete the cached `credentials.json` in `~/.cache/spotify_player` then re-run the app
Author
Owner

@evolutionxbox commented on GitHub (Nov 29, 2024):

I've done this and I still see there error. I also do not have a ~/.cache/spotify_player folder.

OS: macOS Sonoma 14.6.1
Version: 0.20.1

<!-- gh-comment-id:2507577191 --> @evolutionxbox commented on GitHub (Nov 29, 2024): I've done this and I still see there error. I also do not have a `~/.cache/spotify_player` folder. OS: macOS Sonoma 14.6.1 Version: 0.20.1
Author
Owner

@gand0rf commented on GitHub (Nov 29, 2024):

@aome510 Just wanted to touch base. I haven't had a chance to try this out myself. Been traveling for work this week. But I installed player in my worklaptops wsl term, and it loads just fine. Except for there is no spotify deamom for it to connect to, but I was just testing the launching and connecting it to my account. Should get back home tonight to see if this works for me.

<!-- gh-comment-id:2507584348 --> @gand0rf commented on GitHub (Nov 29, 2024): @aome510 Just wanted to touch base. I haven't had a chance to try this out myself. Been traveling for work this week. But I installed player in my worklaptops wsl term, and it loads just fine. Except for there is no spotify deamom for it to connect to, but I was just testing the launching and connecting it to my account. Should get back home tonight to see if this works for me.
Author
Owner

@aome510 commented on GitHub (Nov 29, 2024):

I've done this and I still see there error. I also do not have a ~/.cache/spotify_player folder.

OS: macOS Sonoma 14.6.1 Version: 0.20.1

that's weird. What is the result of spotify_player --help?

<!-- gh-comment-id:2508015760 --> @aome510 commented on GitHub (Nov 29, 2024): > I've done this and I still see there error. I also do not have a `~/.cache/spotify_player` folder. > > OS: macOS Sonoma 14.6.1 Version: 0.20.1 that's weird. What is the result of `spotify_player --help`?
Author
Owner

@gand0rf commented on GitHub (Nov 30, 2024):

@aome510 That fixed it!! Thank you. Done on my end. Not sure if you want to leave this open for evolutionxobx's issue or not.

<!-- gh-comment-id:2508754691 --> @gand0rf commented on GitHub (Nov 30, 2024): @aome510 That fixed it!! Thank you. Done on my end. Not sure if you want to leave this open for evolutionxobx's issue or not.
Author
Owner

@aome510 commented on GitHub (Nov 30, 2024):

I think it might be something unrelated. Will close this for now

<!-- gh-comment-id:2508769714 --> @aome510 commented on GitHub (Nov 30, 2024): I think it might be something unrelated. Will close this for now
Author
Owner

@evolutionxbox commented on GitHub (Dec 3, 2024):

@aome510 I'll create a new ticket if I can, because no matter how many times I run spotify_player authenticate (and follow the link) no credentials.json is created.

Sorry @aome510, I hadn't started the Spotify daemon either. Thanks @gand0rf 👍

<!-- gh-comment-id:2514651410 --> @evolutionxbox commented on GitHub (Dec 3, 2024): ~@aome510 I'll create a new ticket if I can, because no matter how many times I run `spotify_player authenticate` (and follow the link) no `credentials.json` is created.~ Sorry @aome510, I hadn't started the Spotify daemon either. Thanks @gand0rf 👍
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-player#359
No description provided.