Unable to play any songs

[oroundtree]

Describe the bug
When starting ncspot I was only able to play some of the songs in my library. After clearing the cache I'm not able to play any of them, I can select a song but any attempt to play it will not do anything (timer will be stuck at 0:00)

To Reproduce
Steps to reproduce the behavior:

1. Clear ncspot cache
2. Attempt to play any song

Expected behavior
Selected song will begin to play

System (please complete the following information):

• OS: CachyOS
• Terminal: Kitty
• Version: ncspot 1.3.4-1.1
• Installed from: pacman

Backtrace/Debug log
See attached log

Additional context
I've been using ncspot for about a year now and this is the first time I've had any issue

ncspot2.log

[shaunsaladi]

Im getting the same thing, even with other terminal spotify players. It cannot play anything when the selected device is itself. When the selected device is itself, it trips out the songs and it just skips songs frequently.

[sudogringo]

Im having a similar problem. I think only music in my cache is playing right now. It may be a new change to the spotify api that librespot hasnt updated to.

[oroundtree]

I was able to find a temporary solution here which is to add the following lines to my /etc/hosts file and restart my network manager

0.0.0.0    audio-cf-del-874.spotifycdn.com
0.0.0.0    audio-fa-del-874.spotifycdn.com

I initially added the cf-del host and found that the fallback fa-del host was still failing and after adding it as well it works! The failing hosts might be different in your case but you should be able to find them using librespot --verbose and perusing the logs

[ThomasFrans]

This might be related to the following bug in librespot: librespot-org/librespot@db1ef7a

I get a 500 status code from the Spotify CDN, which is what is mentioned in that commit as well. Maybe it would be an idea to switch to the development branch of librespot (or at least that commit) until this fix is released?

[alaeddine119]

I had the same issue, but trying today it worked again. the issue probably from the spotify side.