mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 01:15:55 +03:00
[GH-ISSUE #455] Unable to connect to client through CLI #1191
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#1191
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 @dxnnv on GitHub (May 25, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/455
Describe the bug
All
.\spotify-player.exe <command>commands returnError: try to connect to a client Caused by: An existing connection was forcibly closed by the remote host. (os error 10054)To Reproduce
Install Rust
Install the v0.18.2 binary for Windows
(Also tested this by installing with scoop, same behavior)
Extract the binary, open powershell/cmd and run
.\spotify-player.exeto add credentialsRun any subcommand
Expected behaviour
The subcommand gets executed as expected, sending the request to spotify api.
Log and backtrace
Backtrace was empty, log provided
Screenshots
Screenshot
Environment
v0.18.2Additional context
Seemed to work fine via the GUI in ps/cmd, was able to connect to the client and use controls just fine. Only happens when using CLI. Also tried with providing my own clientId for a valid application (also worked with GUI but not CLI)
@aome510 commented on GitHub (May 31, 2024):
I don't have access to windows machine, so it's hard for me to debug this kind of issue. Seeking for help 👀
@adriankarlen commented on GitHub (Sep 10, 2024):
I am getting the same issue on windows.
@hakuoku commented on GitHub (Dec 1, 2024):
It also occurs to me.
@jayz25 commented on GitHub (Jan 12, 2025):
Hello, does anyone have a solution for this issue? I am also getting the same issue on my Windows machine.
Thanks.