starred/librespot

Fork 0

mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00

[GH-ISSUE #1245] Authentication on all desktop platforms is broken #569

New issue

Closed

opened 2026-02-27 19:31:20 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 19:31:20 +03:00

Owner

Originally created by @lmore377 on GitHub (Jan 19, 2024).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1245

Describe the bug
Attempting to start Spotify Connect from any desktop client results in 403 errors, similar to issue #1179. If started from android or iOS, authentication works fine. If librespot is given credentials with -u and -p then desktop clients work but only for the logged in user.

To reproduce
Steps to reproduce the behavior:

Launch librespot without -u or -p
Connect with any desktop client (Windows, Linux, macOS)
Click play on any song
Console fills with 403 and similar errors

Log
This log is from me connecting from a linux client but the output is almost identical to windows & macos. I obfuscated some IDs but the log is otherwise as-is. I ran librespot with -G -H to prevent any issues from caching.

linux.log

Host (what you are running librespot on):

OS: Debian 12
Platform: x86_64

Additional context
This issue is fixed by #1220 but I noticed that the PR seems stale. Could I create my own PR with the same changes?

Originally created by @lmore377 on GitHub (Jan 19, 2024). Original GitHub issue: https://github.com/librespot-org/librespot/issues/1245 **Describe the bug** Attempting to start Spotify Connect from any desktop client results in 403 errors, similar to issue #1179. If started from android or iOS, authentication works fine. If librespot is given credentials with `-u` and `-p` then desktop clients work but only for the logged in user. **To reproduce** Steps to reproduce the behavior: 1. Launch `librespot` without `-u` or `-p` 2. Connect with any desktop client (Windows, Linux, macOS) 3. Click play on any song 4. Console fills with 403 and similar errors **Log** This log is from me connecting from a linux client but the output is almost identical to windows & macos. I obfuscated some IDs but the log is otherwise as-is. I ran librespot with `-G -H` to prevent any issues from caching. [linux.log](https://github.com/librespot-org/librespot/files/13993995/linux.log) **Host (what you are running `librespot` on):** - OS: Debian 12 - Platform: x86_64 **Additional context** This issue is fixed by #1220 but I noticed that the PR seems stale. Could I create my own PR with the same changes?

kerem

2026-02-27 19:31:20 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 19:31:20 +03:00

Author

Owner

@roderickvd commented on GitHub (Jan 19, 2024):

Additional context This issue is fixed by #1220 but I noticed that the PR seems stale. Could I create my own PR with the same changes?

Of course, or maybe clone that user's branch, resolve the outstanding review comments and we'd be good to go!

@roderickvd commented on GitHub (Jan 19, 2024): > **Additional context** This issue is fixed by #1220 but I noticed that the PR seems stale. Could I create my own PR with the same changes? Of course, or maybe clone that user's branch, resolve the outstanding review comments and we'd be good to go!

kerem referenced this issue

2026-02-27 20:00:39 +03:00

[PR #569] [MERGED] Allow pipeline writer to spit out Ogg directly, including when seeking #970

kerem referenced this issue

2026-02-27 20:00:44 +03:00

[PR #604] [CLOSED] Release tremor fix immediately #994

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/librespot#569

No description provided.

Rows
Columns