search

RandomNinjaAtk / docker-lidarr-extended

lidarr-extended :: Lidarr application packaged with multiple scripts to provide additional functionality
GNU General Public License v3.0
275 stars 24 forks source link

[Bug]: Reauthorization to Tidal seems to be acting up #125

Closed Repooc closed 1 year ago

Repooc commented 1 year ago

Describe the bug Seems that login isnt working for Tidal now or something else is going on...

To Reproduce Steps to reproduce the behavior:

  1. Start the container
  2. See url to authorize Tidal
  3. Authorize Tidal
  4. it appears to search then seems to have to repeat authorization and something fails, im not sure ... sometimes it appears to start "searching" but ends up wanting me to reauthorize again

Expected behavior Authorize tidal, it works for the week before having to do it again

Log Data image

Docker Info:

Additional context On a side note, I swore I was in a discord server of yours for all your projects, not sure if I left or if you closed it but I can't seem to find any invite link for one now if there is one... Please share a link if you still have one and accepting people in to it.

Repooc commented 1 year ago

Just a thought, maybe Tidal is throttling my account or something...

RandomUser345 commented 1 year ago

Havin same issues: but what works for me is following: connect to the bash in the container, execute tidal-dl there, switch api key to 1 (master only), authorize with link, switch back to the original api key to 4 (normal/hifi/master), authorize with link. Then it usually works for the 7 days the token is valid.

RandomNinjaAtk commented 1 year ago

I'm not personally seeing any issue. But maybe something changed.

Also, I removed the workaround for the token because it was no longer needed.

There is no discord server.

RandomUser345 commented 1 year ago

Had this issue from the start... but I figured I'm the only one. Maybe its a ARM64 problem: thats why it's not very common?

RandomNinjaAtk commented 1 year ago

Maybe the client doesn't support arm? Idk.

In my own setup, I'm not having any issues with the client. My only guess is the test album/song is not available in your geographic location, which is causing the authentication issue. If it was working previously, is there something you changed? Or has it never worked?

RandomNinjaAtk commented 1 year ago

It's possible that 1.0.295 may resolve this, but you'd have to test to know if it helped....

RandomNinjaAtk commented 1 year ago

I'm unable to reproduce this problem. So its likely a problem that is specific to your configuration/setup. You should try the latest release, because one of my theory may have resolved it, but you'd have to test to see if that is the case. You should also see if you can use the client successfully outside of this container.

Repooc commented 1 year ago

I am not experiencing the issue at the current moment but i have not been looking into it the past couple days but could have been from ur fix. Thank you for looking into it though.