mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #374] Unable to start spotify_player connect closed via error #1136
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1136
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Expected behaviour
unable to start the spotify_player . But the spotify web can access.
Log and backtrace
Please refer to this URL for more details.
Screenshots

Environment
Additional context
@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?
@xbunax commented on GitHub (Feb 21, 2024):
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/playerand it push back errorstatus:401 message: no token provide@aome510 commented on GitHub (Feb 24, 2024):
Does this mean you can run
spotify_playerin other devices?@xbunax commented on GitHub (Feb 26, 2024):
yes,I can use it in powershell and wsl2.
@xbunax commented on GitHub (Feb 28, 2024):
I find that I open the surge's tun mode ,spotify_player can work well, Finally. Thanks a lot.
@aome510 commented on GitHub (Feb 28, 2024):
Glad to hear that. So it was because of a network block setting like I initially suspected