-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent PermissionDenied StatusCode(403) Errors #1381
Comments
And if you retry the same file it works? |
Correct. Without making any changes to my setup, the same track now plays:
|
Sorry, trying to understand, do you have to restart librespot to get it working again or is it the same session? If you don't restart librespot, does everything fail after this or is it still intermittent? |
Also, are you able to try the latest code rather than the 0.5.0 release? This part of the code has changed. |
No restart of anything involved. If I wait a bit and try the exact same uri again, it will eventually start working again. I'm running the 0.5.0 from crates.io but I can try to compile the dev branch and see if that makes a difference. I didn't see any commits that I thought would affect this issue so I hadn't tried a dev branch build. |
Perhaps it's working again once the access token expires and we get a new one. Can you see that happening in your debug log? 4580dab is a different method to obtain access tokens, it's likely relevent. |
Ah, I took that to mean that the login5 process was changed and wouldn't affect my OAuth process, didn't look/understand close enough. I'm compiling the dev version now and will try that out. Here are complete logs from the past hour where the command
|
I'm on mobile so not ideal to read through the logs. Am I right that:
|
I think that's just librespot marking it like that in response to the failure ( What's happened to the |
These are the logs I got even with - -verbose. I think that's because of the way I'm getting the logs from the Docker container. But, good news, after compiling the dev branch on Friday and running that build for the last couple of days, I haven't had any auth issues. |
Cool. Gonna consider this as fixed then! Feel free to reopen when it reoccurs. |
Look for similar bugs
None recently and not using the new OAuth in v0.5.0
Description
Playback intermittently fails with the error:
Unable to load audio item: Error { kind: PermissionDenied, error: StatusCode(403) }
Sometimes things are fine for 2+ days before failure and other times failure occurs immediately after launching librespot.
I authenticated using the new OAuth process last week and have exclusively used the cached credentials.json file since then with no need to re-auth.
Version
0.5.0 built from crates.io
How to reproduce
I have not been able to determine a reliable way to reproduce the behavior.
For reference, I am launching librespot with the following:
librespot --cache /authcache --disable-discovery --name "Spotty" --bitrate 320 --backend pipe --verbose
Log
Host (what you are running
librespot
on):Additional context
The text was updated successfully, but these errors were encountered: