[GH-ISSUE #201] spotify_player asking for a username and password #103

New issue

Closed

opened 2026-03-02 23:44:34 +03:00 by kerem · 27 comments

kerem commented 2026-03-02 23:44:34 +03:00

Owner

Copy link

Originally created by @mariano-daniel on GitHub (May 22, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/201

I looked up the main page and documentation page and nowhere this is mentioned.

I tried the API client_id, my email username, the username that shows on my profile, none of them work.

What am I supposed to enter when it's asking for my username? 🤷🏻‍♂️

spotify_player
No cached credentials found, please authenticate the application first.
Username: xxxxx@icloud.com
Password for xxxxx@icloud.com: 
Failed to authenticate, 2 tries left
Username (default: xxxxxx@icloud.com): al3dtskdslj3b35s40
Password for al3dtskdslj3b35s40: 
Failed to authenticate, 1 tries left
Username (default: al3dtskdslj3b35s40): 

Originally created by @mariano-daniel on GitHub (May 22, 2023). Original GitHub issue: https://github.com/aome510/spotify-player/issues/201 I looked up the main page and documentation page and nowhere this is mentioned. I tried the API client_id, my email username, the username that shows on my profile, none of them work. What am I supposed to enter when it's asking for my username? 🤷🏻‍♂️ ``` spotify_player No cached credentials found, please authenticate the application first. Username: xxxxx@icloud.com Password for xxxxx@icloud.com: Failed to authenticate, 2 tries left Username (default: xxxxxx@icloud.com): al3dtskdslj3b35s40 Password for al3dtskdslj3b35s40: Failed to authenticate, 1 tries left Username (default: al3dtskdslj3b35s40): ```

kerem 2026-03-02 23:44:34 +03:00

• closed this issue
• added the
  bug
  label

kerem commented 2026-03-02 23:44:35 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 22, 2023):

I'm not sure if you have the same thing but in my case, Spotify username should be able to find on the Account Overview website. Here is mine for reference (username is the first one and email is the second one):

<!-- gh-comment-id:1557700643 --> @aome510 commented on GitHub (May 22, 2023): I'm not sure if you have the same thing but in my case, Spotify username should be able to find on the [Account Overview website](https://www.spotify.com/account/overview/). Here is mine for reference (`username` is the first one and `email` is the second one): <img width="861" alt="Screenshot 2023-05-22 at 2 27 38 PM" src="https://github.com/aome510/spotify-player/assets/40011582/a18ae161-a278-4cd2-ad8c-b7fec68f1ce1">

kerem commented 2026-03-02 23:44:35 +03:00

Author

Owner

Copy link

@mariano-daniel commented on GitHub (May 22, 2023):

Hello Thang Pham! Yep, that’s the one I’ve used and it did not work. Did it
work for you?

Regards ,

On Mon, 22 May 2023 at 15:29 Thang Pham @.***> wrote:

I'm not sure if you have the same thing but in my case, Spotify username
should be able to find on the Account Overview website
https://www.spotify.com/account/overview/. Here is mine for reference (
username is the first one and email is the second one):
[image: Screenshot 2023-05-22 at 2 27 38 PM]
https://user-images.githubusercontent.com/40011582/240000231-a18ae161-a278-4cd2-ad8c-b7fec68f1ce1.png

—
Reply to this email directly, view it on GitHub
https://github.com/aome510/spotify-player/issues/201#issuecomment-1557700643,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPFFQYE55UK3KVHCNNPVL3XHOWAXANCNFSM6AAAAAAYJ4OPNU
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1557878746 --> @mariano-daniel commented on GitHub (May 22, 2023): Hello Thang Pham! Yep, that’s the one I’ve used and it did not work. Did it work for you? Regards , On Mon, 22 May 2023 at 15:29 Thang Pham ***@***.***> wrote: > I'm not sure if you have the same thing but in my case, Spotify username > should be able to find on the Account Overview website > <https://www.spotify.com/account/overview/>. Here is mine for reference ( > username is the first one and email is the second one): > [image: Screenshot 2023-05-22 at 2 27 38 PM] > <https://user-images.githubusercontent.com/40011582/240000231-a18ae161-a278-4cd2-ad8c-b7fec68f1ce1.png> > > — > Reply to this email directly, view it on GitHub > <https://github.com/aome510/spotify-player/issues/201#issuecomment-1557700643>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AOPFFQYE55UK3KVHCNNPVL3XHOWAXANCNFSM6AAAAAAYJ4OPNU> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

kerem commented 2026-03-02 23:44:35 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 22, 2023):

Hello Thang Pham! Yep, that’s the one I’ve used and it did not work. Did it
work for you?

Just tried and it still works for me. Can you also provide the logs in ~/.cache/spotify_player` if any?

<!-- gh-comment-id:1557891675 --> @aome510 commented on GitHub (May 22, 2023): > Hello Thang Pham! Yep, that’s the one I’ve used and it did not work. Did it work for you? Just tried and it still works for me. Can you also provide the logs in ~/.cache/spotify_player` if any?

kerem commented 2026-03-02 23:44:35 +03:00

Author

Owner

Copy link

@mariano-daniel commented on GitHub (May 23, 2023):

spotify-player-23-05-22-02-05.log

Hello @aome510 ! Logs attached. unfortunately they don't seem to be very verbose, just say bad credentials. But i'm entering the same info when I'm login into my spotify profile, but using the username you mentioned on your screenshot (but for me, of course)

<!-- gh-comment-id:1558292837 --> @mariano-daniel commented on GitHub (May 23, 2023): [spotify-player-23-05-22-02-05.log](https://github.com/aome510/spotify-player/files/11538092/spotify-player-23-05-22-02-05.log) Hello @aome510 ! Logs attached. unfortunately they don't seem to be very verbose, just say bad credentials. But i'm entering the same info when I'm login into my spotify profile, but using the username you mentioned on your screenshot (but for me, of course)

kerem commented 2026-03-02 23:44:35 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 23, 2023):

hmmm, that's really weird. At this point, I actually don't know the cause. Can you double check if the same combination of username and password works in the official Spotify website?

<!-- gh-comment-id:1558315421 --> @aome510 commented on GitHub (May 23, 2023): hmmm, that's really weird. At this point, I actually don't know the cause. Can you double check if the same combination of `username` and `password` works in the official Spotify website?

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@mariano-daniel commented on GitHub (May 23, 2023):

hmmm, that's really weird. At this point, I actually don't know the cause. Can you double check if the same combination of username and password works in the official Spotify website?

Yep, it works when I login to the site, not when I try the program. I can email you a video with tests.

Thanks!

<!-- gh-comment-id:1558468853 --> @mariano-daniel commented on GitHub (May 23, 2023): > hmmm, that's really weird. At this point, I actually don't know the cause. Can you double check if the same combination of `username` and `password` works in the official Spotify website? Yep, it works when I login to the site, not when I try the program. I can email you a video with tests. Thanks!

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@adworacz commented on GitHub (May 24, 2023):

I'm running into this as well - I created a new client ID in my spotify account (although I have no idea what to set the redirect URL to, and there's nothing mentioned in the config.md documentation about what to use), so I just used http://localhost:8080/.

I've tried twice now to enter my credentials, and I'm getting timeouts of some kind:

2023-05-24T16:55:26.147375Z  INFO spotify_player::auth: Creating a new session with new authentication credentials
2023-05-24T16:57:49.906749Z  WARN spotify_player::auth: Failed to authenticate: Cannot create session: Connection timed out (os error 110)

<!-- gh-comment-id:1561602588 --> @adworacz commented on GitHub (May 24, 2023): I'm running into this as well - I created a new client ID in my spotify account (although I have no idea what to set the redirect URL to, and there's nothing mentioned in the `config.md` documentation about what to use), so I just used `http://localhost:8080/`. I've tried twice now to enter my credentials, and I'm getting timeouts of some kind: ``` 2023-05-24T16:55:26.147375Z INFO spotify_player::auth: Creating a new session with new authentication credentials 2023-05-24T16:57:49.906749Z WARN spotify_player::auth: Failed to authenticate: Cannot create session: Connection timed out (os error 110) ```

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 24, 2023):

Yep, it works when I login to the site, not when I try the program. I can email you a video with tests.

Can u email me an email if possible?

I created a new client ID in my spotify account (although I have no idea what to set the redirect URL to, and there's nothing mentioned in the config.md documentation about what to use), so I just used http://localhost:8080/.

Did u put client_id = "http://localhost:8080/"? You don't need a redirect URL for spotify_player unlike spotify-tui. spotify-player relies on username/password to authenticate. client_id is only needed if you want to use https://github.com/aome510/spotify-player#spotify-connect.

It's recommended to specify your own Client ID to avoid possible rate limits and to allow a full Spotify connect support.

From config.md document, it's not required to specify your own client ID though.

<!-- gh-comment-id:1561677693 --> @aome510 commented on GitHub (May 24, 2023): > Yep, it works when I login to the site, not when I try the program. I can email you a video with tests. Can u email me an email if possible? > I created a new client ID in my spotify account (although I have no idea what to set the redirect URL to, and there's nothing mentioned in the config.md documentation about what to use), so I just used http://localhost:8080/. Did u put `client_id = "http://localhost:8080/"`? You don't need a redirect URL for `spotify_player` unlike `spotify-tui`. `spotify-player` relies on username/password to authenticate. `client_id` is only needed if you want to use https://github.com/aome510/spotify-player#spotify-connect. > It's recommended to specify [your own Client ID](https://developer.spotify.com/documentation/web-api/concepts/apps) to avoid possible rate limits and to allow a full [Spotify connect](https://www.spotify.com/us/connect/) support. From `config.md` document, it's **not required** to specify your own client ID though.

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@adworacz commented on GitHub (May 25, 2023):

Spotify requires that you specify a redirect URL when creating the client ID, otherwise it errors:

Did u put client_id = "http://localhost:8080/"?

No I didn't. I put the client ID generated via the Spotify Developer website. And I only tried to generate a client ID after the first attempt at using username/password failed.

The same timeout occurs if I comment out the client_id entry in app.toml.

<!-- gh-comment-id:1562101949 --> @adworacz commented on GitHub (May 25, 2023): Spotify requires that you specify a redirect URL when creating the client ID, otherwise it errors:  > Did u put client_id = "http://localhost:8080/"? No I didn't. I put the client ID generated via the Spotify Developer website. And I only tried to generate a client ID after the first attempt at using username/password failed. The same timeout occurs if I comment out the `client_id` entry in `app.toml`.

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 25, 2023):

@adworacz thanks for the clarification. Can you try running RUST_LOG=debug spotify_player and send me a corresponding log?

Related issue: https://github.com/librespot-org/librespot/issues/1010. Look like this happens because librespot couldn't connect to a specific AP.

<!-- gh-comment-id:1563123577 --> @aome510 commented on GitHub (May 25, 2023): @adworacz thanks for the clarification. Can you try running `RUST_LOG=debug spotify_player` and send me a corresponding log? Related issue: https://github.com/librespot-org/librespot/issues/1010. Look like this happens because `librespot` couldn't connect to a specific AP.

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@adworacz commented on GitHub (May 25, 2023):

I'd wager you're correct on that linked issue.

Here's the pertinent logs I see when using RUST_LOG=debug

2023-05-25T16:25:31.793573Z  INFO spotify_player::auth: Creating a new session with new authentication credentials
2023-05-25T16:25:46.650291Z DEBUG hyper::client::connect::dns: resolving host="apresolve.spotify.com"
2023-05-25T16:25:46.691555Z DEBUG hyper::client::connect::http: connecting to 34.98.74.57:80
2023-05-25T16:25:46.736232Z DEBUG hyper::client::connect::http: connected to 34.98.74.57:80
2023-05-25T16:25:46.736799Z DEBUG hyper::proto::h1::io: flushed 47 bytes
2023-05-25T16:25:46.829042Z DEBUG hyper::proto::h1::io: parsed 5 headers
2023-05-25T16:25:46.829083Z DEBUG hyper::proto::h1::conn: incoming body is content-length (169 bytes)
2023-05-25T16:25:46.829113Z DEBUG hyper::proto::h1::conn: incoming body completed
2023-05-25T16:25:46.829175Z DEBUG hyper::client::pool: pooling idle connection for ("http", apresolve.spotify.com:80)
2023-05-25T16:25:46.829266Z  WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gue1.spotify.com:4070
2023-05-25T16:25:46.829273Z  WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:80
2023-05-25T16:25:46.829280Z  INFO librespot_core::session: Connecting to AP "ap-guc3.spotify.com:4070"
2023-05-25T16:27:57.722605Z  WARN spotify_player::auth: Failed to authenticate: Cannot create session: Connection timed out (os error 110)

<!-- gh-comment-id:1563192202 --> @adworacz commented on GitHub (May 25, 2023): I'd wager you're correct on that linked issue. Here's the pertinent logs I see when using `RUST_LOG=debug` ``` 2023-05-25T16:25:31.793573Z INFO spotify_player::auth: Creating a new session with new authentication credentials 2023-05-25T16:25:46.650291Z DEBUG hyper::client::connect::dns: resolving host="apresolve.spotify.com" 2023-05-25T16:25:46.691555Z DEBUG hyper::client::connect::http: connecting to 34.98.74.57:80 2023-05-25T16:25:46.736232Z DEBUG hyper::client::connect::http: connected to 34.98.74.57:80 2023-05-25T16:25:46.736799Z DEBUG hyper::proto::h1::io: flushed 47 bytes 2023-05-25T16:25:46.829042Z DEBUG hyper::proto::h1::io: parsed 5 headers 2023-05-25T16:25:46.829083Z DEBUG hyper::proto::h1::conn: incoming body is content-length (169 bytes) 2023-05-25T16:25:46.829113Z DEBUG hyper::proto::h1::conn: incoming body completed 2023-05-25T16:25:46.829175Z DEBUG hyper::client::pool: pooling idle connection for ("http", apresolve.spotify.com:80) 2023-05-25T16:25:46.829266Z WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gue1.spotify.com:4070 2023-05-25T16:25:46.829273Z WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:80 2023-05-25T16:25:46.829280Z INFO librespot_core::session: Connecting to AP "ap-guc3.spotify.com:4070" 2023-05-25T16:27:57.722605Z WARN spotify_player::auth: Failed to authenticate: Cannot create session: Connection timed out (os error 110) ```

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@adworacz commented on GitHub (May 25, 2023):

Ahhhh now this is interesting - it seems to be related to my work VPN.

If I'm off VPN, I can login just fine and start playing music. If I'm on VPN, I can't start spotify-player at all, even after having successfully authenticated while off VPN.

This is interesting, since I don't have these issues with spotify-tui + spotifyd while on VPN.

<!-- gh-comment-id:1563197026 --> @adworacz commented on GitHub (May 25, 2023): Ahhhh now this is interesting - it seems to be related to my work VPN. If I'm off VPN, I can login just fine and start playing music. If I'm on VPN, I can't start spotify-player at all, even after having successfully authenticated while off VPN. This is interesting, since I don't have these issues with `spotify-tui` + `spotifyd` while on VPN.

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 25, 2023):

I also guess that it's a VPN issue or something related.

This is interesting, since I don't have these issues with spotify-tui + spotifyd while on VPN.

I think spotify_player uses the same setup as spotifyd to create a session so I don't know how spotifyd works but spotify_player does not.

<!-- gh-comment-id:1563317291 --> @aome510 commented on GitHub (May 25, 2023): I also guess that it's a VPN issue or something related. > This is interesting, since I don't have these issues with spotify-tui + spotifyd while on VPN. I think `spotify_player` uses the same setup as `spotifyd` to create a session so I don't know how `spotifyd` works but `spotify_player` does not.

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 25, 2023):

Look like the only difference I can find is that spotifyd specifies a default ap_port=443: github.com/Spotifyd/spotifyd@1c149822b1/src/config.rs (L855-L860).

Can you try if specifying ap_port = 443 in app.toml works?

<!-- gh-comment-id:1563322326 --> @aome510 commented on GitHub (May 25, 2023): Look like the only difference I can find is that `spotifyd` specifies a default `ap_port=443`: https://github.com/Spotifyd/spotifyd/blob/1c149822b13ba0b542f27aca353ee85fd78f97d4/src/config.rs#L855-L860. Can you try if specifying `ap_port = 443` in `app.toml` works?

kerem commented 2026-03-02 23:44:36 +03:00

Author

Owner

Copy link

@adworacz commented on GitHub (May 25, 2023):

Can you try if specifying ap_port = 443 in app.toml works?

Worked like a charm!!

I can login, listen to music, the whole nine yards!

<!-- gh-comment-id:1563483156 --> @adworacz commented on GitHub (May 25, 2023): > Can you try if specifying ap_port = 443 in app.toml works? Worked like a charm!! I can login, listen to music, the whole nine yards!

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@mariano-daniel commented on GitHub (May 25, 2023):

Yep, it works when I login to the site, not when I try the program. I can email you a video with tests.

Can u email me an email if possible?

I didn't quite get this request. What should I put in the email?

<!-- gh-comment-id:1563586504 --> @mariano-daniel commented on GitHub (May 25, 2023): > > Yep, it works when I login to the site, not when I try the program. I can email you a video with tests. > > Can u email me an email if possible? I didn't quite get this request. What should I put in the email?

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 26, 2023):

I didn't quite get this request. What should I put in the email?

I thought you're going to send an email with the video. FYI, my email: phamducthang1234@gmail.com

<!-- gh-comment-id:1563718070 --> @aome510 commented on GitHub (May 26, 2023): > I didn't quite get this request. What should I put in the email? I thought you're going to send an email with the video. FYI, my email: phamducthang1234@gmail.com

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@mariano-daniel commented on GitHub (May 28, 2023):

I didn't quite get this request. What should I put in the email?

I thought you're going to send an email with the video. FYI, my email: phamducthang1234@gmail.com

Email sent! Thank you.

<!-- gh-comment-id:1565778467 --> @mariano-daniel commented on GitHub (May 28, 2023): > > I didn't quite get this request. What should I put in the email? > > I thought you're going to send an email with the video. FYI, my email: [phamducthang1234@gmail.com](mailto:phamducthang1234@gmail.com) Email sent! Thank you.

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 28, 2023):

@mariano-daniel thanks for the video. Look like the login is failed because you're not in premium account. A premium account is required to use spotify_player.

<!-- gh-comment-id:1565786029 --> @aome510 commented on GitHub (May 28, 2023): @mariano-daniel thanks for the video. Look like the login is failed because you're not in premium account. A premium account is **required** to use `spotify_player`.

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@mariano-daniel commented on GitHub (May 28, 2023):

@mariano-daniel thanks for the video. Look like the login is failed because you're not in premium account. A premium account is required to use spotify_player.

But why would it throw bad credentials though? Shouldn't at least me log me in and then throw an error?

<!-- gh-comment-id:1565786564 --> @mariano-daniel commented on GitHub (May 28, 2023): > @mariano-daniel thanks for the video. Look like the login is failed because you're not in premium account. A premium account is **required** to use `spotify_player`. But why would it throw bad credentials though? Shouldn't at least me log me in and then throw an error?

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@aome510 commented on GitHub (May 28, 2023):

But why would it throw bad credentials though?

Exactly =)). It used to throw a better error: https://github.com/aome510/spotify-player/issues/29#issuecomment-966393666

This seems to change because I updated the printing mechanism for error from debug to normal.

The reason is that the third-party library that spotify_player relies mostly for handling Spotify stuff doesn't support it: https://github.com/librespot-org/librespot/issues/862

I'll close this issue for now. Feel free to re-open it if you encounter similar issues.

<!-- gh-comment-id:1565788105 --> @aome510 commented on GitHub (May 28, 2023): > But why would it throw bad credentials though? Exactly =)). It used to throw a better error: https://github.com/aome510/spotify-player/issues/29#issuecomment-966393666 This seems to change because I updated the printing mechanism for error from `debug` to `normal`. The reason is that the third-party library that `spotify_player` relies mostly for handling Spotify stuff doesn't support it: https://github.com/librespot-org/librespot/issues/862 I'll close this issue for now. Feel free to re-open it if you encounter similar issues.

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@yashrajbains commented on GitHub (Aug 14, 2024):

Hey there! Following through this thread as I am encountering the same exact issue. Though my issue isn't resolved after specifying ap_port = 443 in app.toml

Any ideas?

<!-- gh-comment-id:2288047649 --> @yashrajbains commented on GitHub (Aug 14, 2024): Hey there! Following through this thread as I am encountering the same exact issue. Though my issue isn't resolved after specifying `ap_port = 443` in `app.toml` Any ideas?

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@sewnie commented on GitHub (Sep 23, 2024):

Why isn't this clarified or documented in the README going over how exactly to use it? Would be nice for it to be painless in spotify-player, whether it be done automatically, written out, or a warning to be shipped to new logins.

<!-- gh-comment-id:2368062964 --> @sewnie commented on GitHub (Sep 23, 2024): Why isn't this clarified or documented in the README going over how exactly to use it? Would be nice for it to be painless in spotify-player, whether it be done automatically, written out, or a warning to be shipped to new logins.

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@sewnie commented on GitHub (Sep 23, 2024):

You mean a new update, not version. I am on the latest git commit of spotify_player and i still have to do this.

<!-- gh-comment-id:2368071370 --> @sewnie commented on GitHub (Sep 23, 2024): You mean a new update, not version. I am on the latest git commit of spotify_player and i still have to do this.

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@sewnie commented on GitHub (Sep 23, 2024):

$ ~/src/librespot-auth/target/debug/librespot-auth --name "kosoku"
Open Spotify and select output device: kosoku
Credentials saved: credentials.json
$ ~/src/spotify-player/target/debug/spotify_player
Error: Failed to initialize the Spotify data

Caused by:
    Token is not valid
$ pwd
/home/sewn/.cache/spotify-player

still no docs on how to use this side by side with spotify-player

<!-- gh-comment-id:2368696765 --> @sewnie commented on GitHub (Sep 23, 2024): ``` $ ~/src/librespot-auth/target/debug/librespot-auth --name "kosoku" Open Spotify and select output device: kosoku Credentials saved: credentials.json $ ~/src/spotify-player/target/debug/spotify_player Error: Failed to initialize the Spotify data Caused by: Token is not valid $ pwd /home/sewn/.cache/spotify-player ``` still no docs on how to use this side by side with spotify-player

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@nikero41 commented on GitHub (Oct 26, 2024):

I still have the same issue on 2 laptops running mac and linux.
I have the correct client_id and even tried the ap_port = 443 put still its not working

here are the logs:

2024-10-26T12:25:32.515688Z DEBUG hyper::proto::h1::io: flushed 47 bytes
2024-10-26T12:25:32.537093Z DEBUG hyper::proto::h1::io: parsed 7 headers
2024-10-26T12:25:32.537199Z DEBUG hyper::proto::h1::conn: incoming body is content-length (169 bytes)
2024-10-26T12:25:32.537284Z DEBUG hyper::proto::h1::conn: incoming body completed
2024-10-26T12:25:32.537311Z DEBUG hyper::client::pool: pooling idle connection for ("http", apresolve.spotify.com:80)
2024-10-26T12:25:32.537430Z  WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:4070    
2024-10-26T12:25:32.537444Z  WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:443    
2024-10-26T12:25:32.537454Z  WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:80    
2024-10-26T12:25:32.537466Z  WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gue1.spotify.com:443    
2024-10-26T12:25:32.537479Z  WARN librespot_core::apresolve: Failed to resolve Access Point: Unable to resolve any viable access points.    
2024-10-26T12:25:32.537487Z  WARN librespot_core::apresolve: Using fallback "ap.spotify.com:443"    
2024-10-26T12:25:32.537495Z  INFO librespot_core::session: Connecting to AP "ap.spotify.com:443"    
2024-10-26T12:25:32.732270Z  WARN spotify_player::auth: Failed to authenticate: Login failed with reason: Bad credentials

<!-- gh-comment-id:2439563095 --> @nikero41 commented on GitHub (Oct 26, 2024): I still have the same issue on 2 laptops running mac and linux. I have the correct `client_id` and even tried the `ap_port = 443` put still its not working here are the logs: ``` 2024-10-26T12:25:32.515688Z DEBUG hyper::proto::h1::io: flushed 47 bytes 2024-10-26T12:25:32.537093Z DEBUG hyper::proto::h1::io: parsed 7 headers 2024-10-26T12:25:32.537199Z DEBUG hyper::proto::h1::conn: incoming body is content-length (169 bytes) 2024-10-26T12:25:32.537284Z DEBUG hyper::proto::h1::conn: incoming body completed 2024-10-26T12:25:32.537311Z DEBUG hyper::client::pool: pooling idle connection for ("http", apresolve.spotify.com:80) 2024-10-26T12:25:32.537430Z WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:4070 2024-10-26T12:25:32.537444Z WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:443 2024-10-26T12:25:32.537454Z WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gew4.spotify.com:80 2024-10-26T12:25:32.537466Z WARN librespot_core::apresolve: Ignoring blacklisted access point ap-gue1.spotify.com:443 2024-10-26T12:25:32.537479Z WARN librespot_core::apresolve: Failed to resolve Access Point: Unable to resolve any viable access points. 2024-10-26T12:25:32.537487Z WARN librespot_core::apresolve: Using fallback "ap.spotify.com:443" 2024-10-26T12:25:32.537495Z INFO librespot_core::session: Connecting to AP "ap.spotify.com:443" 2024-10-26T12:25:32.732270Z WARN spotify_player::auth: Failed to authenticate: Login failed with reason: Bad credentials ```

kerem commented 2026-03-02 23:44:37 +03:00

Author

Owner

Copy link

@sewnie commented on GitHub (Oct 26, 2024):

https://github.com/aome510/spotify-player?tab=readme-ov-file#important-notice

<!-- gh-comment-id:2439565162 --> @sewnie commented on GitHub (Oct 26, 2024): https://github.com/aome510/spotify-player?tab=readme-ov-file#important-notice

kerem referenced this issue 2026-03-02 23:49:12 +03:00

[PR #159] [MERGED] Implement spotify-player's CLI commands #647

kerem referenced this issue 2026-03-02 23:49:21 +03:00

[PR #244] [MERGED] Add player event hook command #680

kerem referenced this issue 2026-03-14 12:47:41 +03:00

[GH-ISSUE #103] feature suggestions/requests #976

kerem referenced this issue 2026-03-14 12:52:50 +03:00

[GH-ISSUE #123] feature request: notifications for tracks #989

kerem referenced this issue 2026-03-14 12:55:14 +03:00

[GH-ISSUE #135] spotify-player via bash/CLI #995

kerem referenced this issue 2026-03-14 15:21:54 +03:00

[PR #159] [MERGED] Implement spotify-player's CLI commands #1584

kerem referenced this issue 2026-03-14 15:23:49 +03:00

[PR #244] [MERGED] Add player event hook command #1618

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

phase2

fix-broken-pipe

v0.0.0

v0.23.0

v0.22.1

v0.22.0

v0.21.3

v0.21.2

v0.21.1

v0.21.0

v0.20.7

v0.20.6

v0.20.5

v0.20.4

v0.20.3

v0.20.2

v0.20.1

v0.20.0

v0.19.1

v0.18.2

v0.18.1

v0.18.0

v0.17.2

v0.17.1

v0.17.0

v0.16.3

v0.16.2

v0.16.1

v0.16.0

v0.15.2

v0.15.1

v0.15.0

v0.14.1

v0.14.0

v0.13.1

v0.13.0

v0.12.1

v0.12.0

v0.11.1

v0.11.0

v0.10.0

v0.9.8

v0.9.6

v0.9.5

v0.9.4

v0.9.3

v0.9.2

v0.9.0

v0.8.0

v0.7.0

v0.6.0

v0.5.2

v0.5.1

v0.5.0

v0.4.0

v0.3.0

v0.2.0

v0.1.1

v0.1.0

Labels

Clear labels   

bug

  

documentation

  

enhancement

  

good first issue

  

help wanted

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

third-party

  

third-party

  

wontfix

No labels

bug

documentation

enhancement

good first issue

help wanted

pull-request

question

third-party

third-party

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#103

No description provided.