As I understand what’s happened, ( I may not be 100% accurate here so please be kind)
There was a change in the Tidal - PMS mechanism somewhere
-or-
A behavior / error condition was overlooked.
It resulted in an “Unauthorized” return code to Plex.tv (somewhere into the account)
They (the Plex.tv) team have identified and, I believe, taken care of the problem.
What’s unknown is how many individual accounts might be impacted because most of the Tidal accounts show a normal status. \
This is why they’re addressing them individually for now (the number of impacted customers to be only a few) and it’s far easier to fix those few than write sometime to address the entire customer database
Again, This is how I understand it. When they are back in the office Monday, they will most likely follow up with this and another thread where there is a reported case.
If I am incorrect, they will explain more authoritatively.
Im brand new to Plex - wanted to test the waters before diving into a NAS system so I installed PMS 1.17.0.1841 on my iMac Pro. Had issues with not claiming server - same screen shot shown above. Since Plex is fixing individually how do I let them know I have this issue? Is posting sufficient? I did not opt for Tidal but did look at it while exploring the features and was surprised to see it run on my mac since I did not subscribe to it.
Hi
I have managed to fix the “Iternal Server Error.Something went wrong at our end”
Go to your account(top right corner)
In top left corner just under account select Online Media Sources
Scroll to Tidal
Select edit and disable
At least my server is accessable again.
Will enable Tidal once they have fixed the bug.
Hope this is usefull to some.
PS if you cant get into your account from you server login via another device using the Plex app
@ChuckPa I’m having the same issues now with “ something wrong on our end” … I recently signed up for tidal a month ago… now I cannot claim my server instead getting error message…
@ChuckPa I’m having similar Tidal integration issues. I get “There was an unexpected error loading this library” when trying to browse the Tidal library in the Plex Web App and the iOS App behaves as if I don’t have a Tidal subscription active. Can you, or someone, take a look at my account and see if it has any of these same issues or symptoms of this problem?
Sorry got home early. I turned Verbose logging off and attempted to test the issue again. It seems like it has partially resolved itself. I am able to see my Tidal Library now, but when I attempt to play anything, it is still showing as “Tidal Preview” though the web app. However, the iOS app still behaves as though I don’t have an active Tidal subscription.
In iOS, I see the “Unsure? Preview 60 million+ ho-def tracks” banner ad at the top and cannot see my library in the app.
Dan,
I can’t help with the iOS logs. THere’s a lot of unknowns and errors there I do not understand. I support Linux but given there are screaming networking errors
Dec 21, 2019 21:03:01.902 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:01.908 [0x170c0f000] DEBUG - Request: [127.0.0.1:61450 (Loopback)] GET /:/eventsource/notifications (3 live) GZIP
Dec 21, 2019 21:03:01.908 [0x170c0f000] DEBUG - Content-Length is -1 (of total: -1).
Dec 21, 2019 21:03:02.007 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.090 [0x170d27000] DEBUG - Request: [127.0.0.1:61452 (Loopback)] PUT /media/providers/remote/status?online=1 (3 live) GZIP
Dec 21, 2019 21:03:02.090 [0x170237000] DEBUG - Completed: [127.0.0.1:61452] 200 PUT /media/providers/remote/status?online=1 (3 live) GZIP 0ms 166 bytes
Dec 21, 2019 21:03:02.109 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.214 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.224 [0x16f183000] DEBUG - Request: [127.0.0.1:61454 (Loopback)] GET /media/providers?includeStorage=1 (3 live) GZIP
Dec 21, 2019 21:03:02.224 [0x16f183000] DEBUG - Asked for unknown type: -1
Dec 21, 2019 21:03:02.224 [0x16f183000] DEBUG - Asked for unknown type: -1
Dec 21, 2019 21:03:02.225 [0x1702c3000] DEBUG - Completed: [127.0.0.1:61454] 200 GET /media/providers?includeStorage=1 (3 live) GZIP 2ms 2777 bytes
Dec 21, 2019 21:03:02.237 [0x170b83000] DEBUG - Request: [127.0.0.1:61456 (Loopback)] DELETE /library/caches (4 live) GZIP
Dec 21, 2019 21:03:02.238 [0x1702c3000] DEBUG - Completed: [127.0.0.1:61456] 200 DELETE /library/caches (4 live) GZIP 0ms 166 bytes
Dec 21, 2019 21:03:02.317 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.422 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.527 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.633 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.738 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.843 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:02.948 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:03.055 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:03.161 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
Dec 21, 2019 21:03:03.266 [0x16f06b000] ERROR - Network Service: Error in browser handle read: 57 (Socket is not connected) socket=77
I need to ask what’s happening with the unit at that time?
@ChuckPa As far as I know, the only thing occurring on the server itself was attempting to browse the Tidal library. Does the Tidal piece actually do anything through the server component? Or is my client just communicating directly with the Tidal service?
There is another thread going where lots of other people are complaining of Tidal integration issues. Is this all part of a bigger issue?
