Tidal Connect Failures

TubularBells · December 17, 2025, 12:19pm

It looks like the Token Authentication error was triggered on the 16th:

Dec 16 20:11:14 rivoplus vtcs[25351]: [2025-12-16 20:11:14.446] [tisoc] [warning] [PlaybackEngineTidal.cpp:251] url fetch error: 0, 400, {"status":400,"error":"invalid_grant","sub_status":11003,"error_description":"The token has expired. (Expired on time)"}

But then you’re also getting a lot of these:

Dec 17 18:14:15 rivoplus vtcs[25351]: [2025-12-17 18:14:15.084] [tisoc] [warning] [PlaybackControllerImpl.cpp:520] Illegal state:1
Dec 17 18:14:15 rivoplus vtcs[25351]: [2025-12-17 18:14:15.085] [tisoc] [warning] [PlaybackControllerImpl.cpp:213] Ignore play request because playback state is not STARTED. state_=2, playstate_=1, player_state_=0
...
Dec 17 18:14:16 rivoplus vtcs[25351]: [2025-12-17 18:14:16.493] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
Dec 17 18:14:16 rivoplus vtcs[25351]: [2025-12-17 18:14:16.494] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_BAD_HEADER
Dec 17 18:14:16 rivoplus vtcs[25351]: [2025-12-17 18:14:16.494] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
...
Dec 17 18:20:54 rivoplus vtcs[25351]: [2025-12-17 18:20:54] [error] handle_transport_init received error: TLS handshake timed out
Dec 17 18:20:54 rivoplus vtcs[25351]: [2025-12-17 18:20:54] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
Dec 17 18:20:54 rivoplus vtcs[25351]: [2025-12-17 18:20:54.553] [tisoc] [error] [WebsocketServerTls.cpp:103] Connection failed. Session State: 3, Error Code: 5, Message: TLS handshake timed out
Dec 17 18:20:57 rivoplus vtcs[25351]: [close:85] Entering
Dec 17 18:20:57 rivoplus vtcs[25351]: [feedThread:276] Exiting
Dec 17 18:20:57 rivoplus vtcs[25351]: [close:100] Exiting
Dec 17 18:20:57 rivoplus vtcs[25351]: [2025-12-17 18:20:57.367] [tisoc] [warning] [PlaybackControllerImpl.cpp:213] Ignore play request because playback state is not STARTED. state_=2, playstate_=1, player_state_=0
...
Dec 17 18:20:57 rivoplus vtcs[25351]: [2025-12-17 18:20:57.937] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC

Are these linked to a failed or closed connection with Tidal’s servers during playback, maybe also linked to instance authorization?

@devgianlu @Darmur

devgianlu · December 17, 2025, 2:52pm

Thank you for the feedback, this seems indeed not resolved. I’ll get back with the TIDAL guys.

GSiguy · December 18, 2025, 6:34am

@TubularBells I am so sorry but I am not versed in all that is stated in the log. I do not know how to decipher it.

I am not sure about your question when you ask me whether it is “linked to a failed or closed connection with Tidal’s servers during playback, maybe also linked to instance authorization?” Could you explain this to me simply?

Marc050 · December 18, 2025, 9:01am

Yeah it just did the 19 songs and sod it thing again

devgianlu · December 18, 2025, 10:14am

TIDAL confirmed the issue is indeed not resolved, I’ll keep you updated.

TubularBells · December 18, 2025, 4:50pm

Hi @GSiguy. Sorry for the confusion, the questions were aimed at the Volumio Dev team tagged in the reply and not you.

I’m not versed in any of this either, but it looks like this involves an authentication problem with Tidal’s servers specifically for Tidal Connect that’s periodically closing connections and the inability to play content because of this. That’s why there’s “lost sync” and corrupted data (“bad header”) errors, as well as TLS handshake and token expiry errors in the log. Hope this helps.

TubularBells · December 18, 2025, 4:53pm

Thanks for the update, @devgianlu ! Though I think it’s affecting Tidal Connect only, I’ll continue testing throughout the day with the native Volumio UI access to Tidal to see if this behaviour pops up there as well - just in case. It hasn’t so far.

devgianlu · December 18, 2025, 5:21pm

Yes, it affects only Tidal Connect.

Marc050 · December 19, 2025, 8:45am

It is now playing song 20, i’ll wait for 21 before posting.

21 playing. Looks like Tidal finally solved it. Let’s hope they’ll keep it that way.

I am still getting this every 12 to 13 minutes though:

Dec 19 10:15:33 magister ntpd[10585]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Dec 19 10:15:33 magister ntpd[10585]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized

https://logs.volumio.org/rivoplus/cJwh4St.html

Marc050 · December 21, 2025, 8:33pm

I am getting the feeling they solved it by extending the time/number of songs. Now it stops about every 4 hours

TubularBells · December 21, 2025, 10:41pm

Hi @Marc050 , is that 4 hour window consistent for you?

If so, it’s not solved but rather just spacing the occurrence out while, we can hope, they address whatever is the root cause for it.

Marc050 · December 21, 2025, 11:13pm

I haven’t timed but I’d say it is pretty consistent.

devgianlu · December 22, 2025, 10:43am

I got confirmation that they extended it to 4 hours while they work on proper fix.

GSiguy · December 23, 2025, 1:43pm

Tidal Connect kicked my Volumio Rivo+ out again. “Server Error” was the pop up.

Here is my log:-
http://logs.volumio.org/rivoplus/AEhJk0z.html

GSiguy · December 27, 2025, 11:03am

Kicked out of Tidal Connect again.

http://logs.volumio.org/rivoplus/4C9OgKQ.html

GSiguy · December 29, 2025, 8:56am

Just got bounced out again.

This time I could not even reselect Volumio RIvo Plus (VR+) in the Tidal App to get back in. I had to go to Volumio’s IP address, go to 'Playback Options" and re-save the “Output Device” before Tidal Connect could connect back to the VR+.

http://logs.volumio.org/rivoplus/7xnHLvt.html

TubularBells · December 29, 2025, 1:27pm

Hi @GSiguy,

Upon reading your logs:

The same error from above continues where the player looses sync/connection.

Dec 29 13:36:22 rivoplus vtcs[32098]: [2025-12-29 13:36:22.655] [tisoc] [error] [SpkconServer.cpp:375] recv error. socket disconnected
Dec 29 13:36:22 rivoplus vtcs[32098]: [2025-12-29 13:36:22.656] [tisoc] [warning] [SessionManagerImpl.cpp:240] Illegal State: IDLE

Dec 29 13:36:30 rivoplus vtcs[32283]: [2025-12-29 13:36:30.678] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC

It is further detailed with another log instance like this:

Dec 29 16:52:23 rivoplus vtcs[32283]: [2025-12-29 16:52:23.833] [tisoc] [warning] [SessionManagerImpl.cpp:240] Illegal State: IDLE
Dec 29 16:52:23 rivoplus vtcs[32283]: [2025-12-29 16:52:23.834] [tisoc] [error] [SpkconServer.cpp:380] recv error. client fd=8 errorno=104 error=Connection reset by peer
Dec 29 16:52:23 rivoplus vtcs[32283]: [2025-12-29 16:52:23.834] [tisoc] [error] [SpkconServer.cpp:375] recv error. socket disconnected
Dec 29 16:52:23 rivoplus vtcs[32283]: [2025-12-29 16:52:23.835] [tisoc] [error] [SpkconServer.cpp:472] socket write error. fd=3 errorno=32 error=Broken pipe

So it looks like Tidal is closing the connection sporadically. I wonder what the team knows about this so far.

While not related to Tidal, this error surprised me:

Dec 29 16:52:26 rivoplus mpd[30531]: Dec 29 16:52 : decoder: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg

Did you install TiMidity++ or a MIDI playback plugin?

GSiguy · December 30, 2025, 4:05am

The only plugins i have installed is as follows:-

GSiguy · December 30, 2025, 5:16am

Today i am repeatedly and frequently getting kicked out
http://logs.volumio.org/rivoplus/MVITQcF.html

GSiguy · December 30, 2025, 9:08am

It is extremely unstable today. I keep getting booted out of Tidal Connect every few minutes…
http://logs.volumio.org/rivoplus/tgizRRH.html