Tidal won't login after latest roon update [fixed in 1.3]

I have the same problem.

Also have same exact issue.

I had the same problem and after trying many things, I noticed when I typed my user name to login I was getting some underscores on some letters. I changed to caps lock (for user name only) and entered password and it worked. Strange…I know, but I was having the same problem on all the devices I tried to login in on…now I’m in.

1 Like

Great! It works! Thx @J_William_Truett!
Curiously, if i put my username (which is my email address) in all CAPITALS, i am allowed in!
This is really weird Roon, how is this even possible?
And, still no official feedback?

As another curiosity i lost contact with my Roon Server today, first time ever…
Took about five minutes, then all of a sudden it was avaliable again.

Hmm, this seems a strange release!

Tried the all caps approach, didn’t work for me. Just to be sure I wasn’t doing something entirely stupid, log onto to tidal via web and the app, no problem getting in.

@nibnis / @Peter_Muller / @Axel_Muecher / @soyka0120 ---- My apologies for the troubles here and thank you all for the reports.

I have touched base with my team regarding this issue and we are looking into it on our end. In the meantime may I kindly ask all of you for the following:

  1. Can you please provide the details of your setup as here.

  2. Has your core machine been rebooted?

  3. Have you tried clearing your TIDAL cache?

If you are still having this issue after trying the above please drop @support a line here and we will gather logs from you to take a closer look. Many thanks and once again, apologies for the inconvenience.

-Eric

Eric,

I’m posting here as opposed to @support since the problem was resolved after rebooting the core (although it took several tries). I’m running Roon Core on a sonictransporter i5 fed into a sonicorbiter to a PS Audio Directstream remotely controlled by MacBook Pro (alas, my iPad is too old).

1 Like

Hi @soyka0120 ---- Thank you for following up and sharing your observations with us! I am glad to hear things have stabilized for you!

-Eric

Eric also had the same problem as other users after latest update – could not login to Tidal. What worked for me is clearing the Tidal cache. CAPS-LOCK mystery trick did not work. I have Roon on QNAP->PS Audio Directream

I’m also on QNAP. For me CAPS-LOCK did the trick.

I’ve now had this issue two days in a row. In both cases I’ve received Tidal login errors when starting the Roon remote.

The first time around I stopped RoonServer, removed the RoonServer/Cache directory, and restarted. I was able to login to Tidal normally at that point and it continued to work all day.

This morning I was presented with the same Tidal login error so I went through the same process of removing the Cache directory. This time around I still received Tidal login errors after starting the server. Deleted the Cache directory a second time and was finally able to login.

I’ve never before had any issues with the Tidal integration in Roon and this behavior popped up since upgrading to build 165.

My core is RoonServer running on Ubuntu Server 16.04.1. I run a nightly Roon backup script which shuts down RoonServer and then backs up the database directory. In looking at the logs from the restart of RoonServer after the backup the following error is present:

11/26 01:00:57 Warn: [tidal/http] https://api.tidalhifi.com/v1/sessions/(masked)?token=(masked) failed (unexpected): System.FieldAccessException: Field System.Net.HttpWebRequest:ResendContentFactory' is inaccessible from methodSystem.Net.Http.HttpClientHandler/c__async0:MoveNext ()’

at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1[TResult].Start[TStateMachine] (TStateMachine& stateMachine) [0x00031] in <a8460a77e67a430a8486a9751162e5f4>:0 at System.Net.Http.HttpClientHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00024] in <41c316444c8a4380b9344ba09eeb18de>:0 at System.Net.Http.HttpMessageInvoker.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00000] in <41c316444c8a4380b9344ba09eeb18de>:0 at System.Net.Http.HttpClient.<SendAsync>__BaseCallProxy0 (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00000] in <41c316444c8a4380b9344ba09eeb18de>:0 at System.Net.Http.HttpClient+<SendAsyncWorker>c__async0.MoveNext () [0x00089] in <41c316444c8a4380b9344ba09eeb18de>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <a8460a77e67a430a8486a9751162e5f4>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <a8460a77e67a430a8486a9751162e5f4>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <a8460a77e67a430a8486a9751162e5f4>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <a8460a77e67a430a8486a9751162e5f4>:0 at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in :0
at Sooloos.Tidal.Proxy+c__async2`1[T].MoveNext () [0x0015e] in /home/roon/roon/Tidal/tidal_http.cs:208
11/26 01:01:00 Warn: Error in web request https://accounts5.roonlabs.com/accounts/3/machineallocate: NetworkError (Error: SecureChannelFailure (The authentication or decryption has failed.))
11/26 01:01:00 Warn: Error in web request https://accounts5.roonlabs.com/geoip/1/lookup: NetworkError (Error: SecureChannelFailure (The authentication or decryption has failed.))
11/26 01:01:00 Warn: [broker/accounts] failed to update machine allocation: Result[Status=NetworkError, ErrorText=Error: SecureChannelFailure (The authentication or decryption has failed.)]

There are no Tidal errors in the prior logfile immediately before RoonServer was stopped for backup.

I have no issues with Tidal via the web or ipad app. Also no issue on the audio devices which use the same token-based authentication method as Roon.

I haven’t rebooted the actual server, but that really shouldn’t be necessary on linux. I did try the all caps username, but that didn’t make a difference.

Flagging @support for follow-up

As an aside, after getting the login to work I tried stopping and re-starting RoonServer. Upon re-start I was presented with the same Tidal login error on the remote.

Stopped RoonServer again, removed the Cache directory, and started RoonServer. Everything is back to normal (I didn’t have to re-login to Tidal).

I man need to add removal of the Cache directory to my backup script :slight_smile:

Hi @AMP ----- Thank you for the follow up and my apologies for any confusion on my part. In your last post you mentioned:

“Stopped RoonServer again, removed the Cache directory, and started RoonServer. Everything is back to normal (I didn’t have to re-login to Tidal).”

Having things been stable or has this been temporary?

-Eric

Having things been stable or has this been temporary?

Intermittent is the best way to describe it. I checked the setup at the shop this morning and everything was fine. The backup ran overnight so RoonServer was stopped and restarted, but there were no Tidal login errors. I’ve stopped and started the server several times and haven’t had a Tidal issue.

At home I have a Synology running as a core that shares the same authorization as the setup at work. When I fired up Roon here this morning I got the typical screen saying that I had exceeded my number of authorizations. This is typical as I deauthorize the core at work when I’m using Roon at home. In this case, though, it said I had a total of “0” authorizations on my account (this number is usually “1”). The only way to clear the issue was to stop the RoonServer package on the Synology and re-start it.

This allowed me to deauthorize the work Core and connect to the one at home. Then the Tidal login error popped up again. Was able to clear it by deleting the Cache directory on the Core.

What’s strange here is that the authorize / deauthorize glitch (reporting 0 licenses on my account) has popped up a couple of times since 165 was released. Additionally when I deauthorize one Core the other continues to function for a very long time. I’ve even been able to re-start the deauthorized core and am still able to reconnect to it, browse, and play. In this case the Core at work has been deauthorized for about 15 minutes and it’s still functioning (as is the authorized core at home). Strange.

Something strange happened with 165…

Hi @Eric,

Well it continues to be predictably unpredictable…

The home core had the authorization overnight and both systems went through a shutdown / backup / restart operation during that time. No issues with the home core this morning (Tidal was authorized and working fine).

Reassigned the authorization to the shop core and got the “Tidal Login Failed” message. Stopped RoonServer and removed the Cache directory, but as with before I still got the error upon restarting RoonServer. Went through the process of removing the Cache directory again and Tidal was able to authenticate upon restart of the RoonServer process.

Hi @AMP ---- Thank you for the feedback! I would like to grab some logs from you and will contacting you via PM with instructions shortly.

-Eric

I’m getting the ‘Tidal Login Failed’ as well. When I try to re-login then from Services I get:

The Roon Server log shows:
11/29 13:59:36 Warn: [tidal/http]
https://api.tidalhifi.com/v1/login/username?token=Imi5DLPIAVRmszdL
failed (unexpected): System.FieldAccessException: Field
System.Net.HttpWebRequest:ResendContentFactory' is inaccessible from methodSystem.Net.Http.HttpClientHandler/

I can access Tidal OK from Firefox with same credentials.

Stopping/restarting Roon had no effect, but rebooting the server cleared the problem and Tidal login worked OK.

Hi @Tony_Devitt ------ Thank you for the feedback. Have you tried clearing your TIDAL cache yet?

-Eric

Also I cannot retrieve my roon account information, it says that an unexpected error has occurred. wish I knew how to go back to previous release…a

Same problem here