[GH-ISSUE #374] Unable to start spotify_player connect closed via error #1136

Closed
opened 2026-03-14 13:37:17 +03:00 by kerem · 6 comments
Owner

Originally created by @xbunax on GitHub (Feb 17, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/374

Describe the bug
I'm unable to start the spotify_player with error

Error: Failed to initialize the Spotify data

Caused by:
    http error: request: error sending request for url (https://api.spotify.com/v1/me/player): error trying to connect: connection closed via error

Expected behaviour
unable to start the spotify_player . But the spotify web can access.

Log and backtrace

  • log file content
2024-02-17T03:44:14.963469Z  INFO spotify_player::state::data: Loading Playlists data from /Users/xbunax/.cache/spotify-player/Playlists_cache.json...
2024-02-17T03:44:14.964591Z  INFO spotify_player::state::data: Successfully loaded Playlists data!
2024-02-17T03:44:14.964607Z  INFO spotify_player::state::data: Loading FollowedArtists data from /Users/xbunax/.cache/spotify-player/FollowedArtists_cache.json...
2024-02-17T03:44:14.989362Z  INFO spotify_player::state::data: Successfully loaded FollowedArtists data!
2024-02-17T03:44:14.989379Z  INFO spotify_player::state::data: Loading SavedAlbums data from /Users/xbunax/.cache/spotify-player/SavedAlbums_cache.json...
2024-02-17T03:44:15.108036Z  INFO spotify_player::state::data: Successfully loaded SavedAlbums data!
2024-02-17T03:44:15.108065Z  INFO spotify_player::state::data: Loading SavedTracks data from /Users/xbunax/.cache/spotify-player/SavedTracks_cache.json...
2024-02-17T03:44:15.540637Z  INFO spotify_player::state::data: Successfully loaded SavedTracks data!
2024-02-17T03:44:18.076120Z  INFO spotify_player::auth: Successfully used the cached credentials to create a new session!
2024-02-17T03:44:18.086704Z  INFO spotify_player::token: Getting new authentication token...

  • nothing in the backtrace file

Please refer to this URL for more details.

Screenshots
image

Environment

  • OS: macOS 14.2
  • Application version: 0.16.3
  • Application features: Install from brew

Additional context

Originally created by @xbunax on GitHub (Feb 17, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/374 **Describe the bug** I'm unable to start the spotify_player with error ``` Error: Failed to initialize the Spotify data Caused by: http error: request: error sending request for url (https://api.spotify.com/v1/me/player): error trying to connect: connection closed via error ``` **Expected behaviour** unable to start the spotify_player . But the spotify web can access. **Log and backtrace** + log file content ``` 2024-02-17T03:44:14.963469Z INFO spotify_player::state::data: Loading Playlists data from /Users/xbunax/.cache/spotify-player/Playlists_cache.json... 2024-02-17T03:44:14.964591Z INFO spotify_player::state::data: Successfully loaded Playlists data! 2024-02-17T03:44:14.964607Z INFO spotify_player::state::data: Loading FollowedArtists data from /Users/xbunax/.cache/spotify-player/FollowedArtists_cache.json... 2024-02-17T03:44:14.989362Z INFO spotify_player::state::data: Successfully loaded FollowedArtists data! 2024-02-17T03:44:14.989379Z INFO spotify_player::state::data: Loading SavedAlbums data from /Users/xbunax/.cache/spotify-player/SavedAlbums_cache.json... 2024-02-17T03:44:15.108036Z INFO spotify_player::state::data: Successfully loaded SavedAlbums data! 2024-02-17T03:44:15.108065Z INFO spotify_player::state::data: Loading SavedTracks data from /Users/xbunax/.cache/spotify-player/SavedTracks_cache.json... 2024-02-17T03:44:15.540637Z INFO spotify_player::state::data: Successfully loaded SavedTracks data! 2024-02-17T03:44:18.076120Z INFO spotify_player::auth: Successfully used the cached credentials to create a new session! 2024-02-17T03:44:18.086704Z INFO spotify_player::token: Getting new authentication token... ``` + nothing in the backtrace file Please refer to [this URL](https://github.com/aome510/spotify-player?tab=readme-ov-file#logging) for more details. **Screenshots** <img width="734" alt="image" src="https://github.com/aome510/spotify-player/assets/50800571/f16aa825-9a3b-4764-b43e-d7f0b875eb84"> **Environment** - OS: macOS 14.2 - Application version: 0.16.3 - Application features: Install from brew **Additional context**
kerem 2026-03-14 13:37:17 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@aome510 commented on GitHub (Feb 20, 2024):

@xbunax Does it happen every time you opened the app? Do you have a VPN turned on or any network setting that may block API access to Spotify server?

<!-- gh-comment-id:1955135613 --> @aome510 commented on GitHub (Feb 20, 2024): @xbunax Does it happen every time you opened the app? Do you have a VPN turned on or any network setting that may block API access to Spotify server?
Author
Owner

@xbunax commented on GitHub (Feb 21, 2024):

@xbunax Does it happen every time you opened the app? Do you have a VPN turned on or any network setting that may block API access to Spotify server?

The web and app are both can be access. And other devices don't have this problem at the same network enviroment. I also change the client ID to my own ,but the problem is still. what' more , I go to the error url https://api.spotify.com/v1/me/player and it push back error status:401 message: no token provide

<!-- gh-comment-id:1955934516 --> @xbunax commented on GitHub (Feb 21, 2024): > @xbunax Does it happen every time you opened the app? Do you have a VPN turned on or any network setting that may block API access to Spotify server? The web and app are both can be access. And other devices don't have this problem at the same network enviroment. I also change the client ID to my own ,but the problem is still. what' more , I go to the error url **`https://api.spotify.com/v1/me/player`** and it push back error `status:401 message: no token provide`
Author
Owner

@aome510 commented on GitHub (Feb 24, 2024):

And other devices don't have this problem at the same network enviroment

Does this mean you can run spotify_player in other devices?

<!-- gh-comment-id:1962568547 --> @aome510 commented on GitHub (Feb 24, 2024): > And other devices don't have this problem at the same network enviroment Does this mean you can run `spotify_player` in other devices?
Author
Owner

@xbunax commented on GitHub (Feb 26, 2024):

And other devices don't have this problem at the same network enviroment

Does this mean you can run spotify_player in other devices?

yes,I can use it in powershell and wsl2.

<!-- gh-comment-id:1963602821 --> @xbunax commented on GitHub (Feb 26, 2024): > > And other devices don't have this problem at the same network enviroment > > Does this mean you can run `spotify_player` in other devices? yes,I can use it in powershell and wsl2.
Author
Owner

@xbunax commented on GitHub (Feb 28, 2024):

And other devices don't have this problem at the same network enviroment

Does this mean you can run spotify_player in other devices?

I find that I open the surge's tun mode ,spotify_player can work well, Finally. Thanks a lot.

<!-- gh-comment-id:1968086133 --> @xbunax commented on GitHub (Feb 28, 2024): > > And other devices don't have this problem at the same network enviroment > > Does this mean you can run `spotify_player` in other devices? I find that I open the surge's tun mode ,spotify_player can work well, Finally. Thanks a lot.
Author
Owner

@aome510 commented on GitHub (Feb 28, 2024):

And other devices don't have this problem at the same network enviroment

Does this mean you can run spotify_player in other devices?

I find that I open the surge's tun mode ,spotify_player can work well, Finally. Thanks a lot.

Glad to hear that. So it was because of a network block setting like I initially suspected

<!-- gh-comment-id:1969144838 --> @aome510 commented on GitHub (Feb 28, 2024): > > > And other devices don't have this problem at the same network enviroment > > > > > > Does this mean you can run `spotify_player` in other devices? > > I find that I open the surge's tun mode ,spotify_player can work well, Finally. Thanks a lot. Glad to hear that. So it was because of a network block setting like I initially suspected
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#1136
No description provided.