-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
Tracks skip or crash with CDN Expiration warning in log #737
Comments
Just for reference in case others are seeing it as a related problem: It appears Spotify is also screwing with their CDNs and there is at least one which is using the wrong cert for the host name (or returning its actual name instead of the load balanced one): Hostname audio4-gm-fb.spotifycdn.com not verified: Not sure how to fix this one, hopefully they notice and clean up the mess. |
Yes, my playlist stops playing every song or so. Logs show SSL verification errors. Indeed same audio4-gm host as in above post.
|
I use Spocon with Owntone and have been have been trying to track down why it's randomly pausing. Do you think this issue is the same? spocon/spocon#62 I posted a log and there are some failed CDN things in there. |
Describe the bug
Tracks stop playing suddenly and playback either stops or moves to the next track. In the logs, an error is noted "Couldn't extract expiration"
To Reproduce
It is intermittent, as only some of the CDN URL's seem to be using this format. It typically takes no less than 3-4 songs to encounter, but has been as long as 20.
Expected behavior
Expiration value should be parsed correctly and chunk should not be prevented from loading
Screenshots/Stracktraces/Logs
2023-10-20 09:01:26,819 WARN CdnManager:187 - Couldn't extract expiration, invalid parameter in CDN url: https://audio4-gm-fb.spotifycdn.com/audio/0f...cf?Expires=1697904086~FullPath~hmac=fTI...Q=
Version/Commit
1.6.4-SNAPSHOT from dev branch
I've submitted a PR that updates the CDN manager code and have been running it locally without issue:
#736
The text was updated successfully, but these errors were encountered: