404 after playing one song #95
Comments
|
PS: it semms to work better, when Librespot has been started at console. |
|
ok, got the same problem when trying to start a new song. Hutspot writes Error 404, but Librespot doesn't show any reaction, it continues to a play current song without any logging. I guess thats a problem between Hutspot and Librespot. |
|
Could you check, when the error occurs, what is shown on the Devices page? Is Librespot still present and active? |
|
After restarting Hutspot and trying a little bit, Librespot got the error Invalid Session with "code 104, Connection reset by peer". No, Librespot wasn't present & active (it was grey). I will check journal again when I can connect by SSH (skimming over the logs at time of last directly use on my device, doesn't show me anything relevant.) |
|
Make sure you have only one librespot instance running (ps aux | grep librespot). You say 'Librespot got the error Invalid Session with "code 104, Connection reset by peer".' what does it mean? How does librespot 'got the error'? |
|
I will. "code 104, Connection reset by peer" was in the Librespot's output, when started at the console (before I could see that Librespot was streaming the file it played). The message was part of a JSON message, so I guess it was by/from the Spotify server. |
|
Next try: It worked for some songs. But then, when changing song, 404 Error is shown in Hutspot and Librespot continue playing (does not show errors). Journal:: Feb 25 18:54:20 Sailfish [13508]: [D] :244 - number of ArtistAlbums: 32 I attached journal and console output. |
|
The log shows hutspot has restarted. Did you do that? What phone do you use it on? |
|
I hit CTRL+C... I am using Sony Xperia X. |
|
@wdehoog: Maybe I missunderstood you. I think that you mean that Librespot restarted, when the connection got lost. I played around with Hutspot/Librespot and reinstalled the latest versions of Hutspot and Librespot. First it worked quite well, but after about 10 or 15 songs, it happend again: Hutspot/Librespot plays only one song. Then I had to restart Librespot from the settings page, and it worked for the next song only (but the next song is no that one I choose). Update: It is quite interesting: I wanted to test again connected with SSH and Update 2: I found some problems (issues) on Librespots Github site. Maybe it is this: librespot-org/librespot#291 |
|
Losing network connection is problematic. Hutspot can detect it and quit. Auto reconnect/start or whatever is needed is not implemented. |
|
The issue you refer to is about another problem. The version of Librespot on openrepos.net already contains this fix. |
|
Ok, thx |
|
Does not look good. Librespot cannot recover from a broken network connection see librespot-org/librespot#134. I suppose we can't do more then stop the librespot service, wait for a network connection, reconnect to spotify, start Librespot and reregister with it. Which in the end gives not much more then just quit and let the user restart hutspot. |
|
That seems to be the root cause, yes. (And maybe even high latency in mobile networks) |
Dear all,
After playing a song using Librespot, playing stops (404 error). Then I have to stop and restart Librespot for the next song. (latest versions).
Haven't success to start and authorize Librespot manually yet.
By the way: if in the settings automatically start/stop at launch/stop of Hutspot is enabled, I have to restart Librespot manually for success.
The text was updated successfully, but these errors were encountered: