I’m seeing places where TIDAL integration occurs, failing on my plex server with 403 errors to https://music.provider.plex.tv.
Example log line: HTTP 403 response from GET https://music.provider.plex.tv/library/metadata/5b91d5ae709c780032669183/similar?excludeFields=summary&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
If I curl this url with the Plex Token for my current webplayer session it works fine. (Obtained through the “View XML” link on a library item)
If I curl this url with the PlexOnlineToken value in the Preferences.xml I get a 403.
If so and since its a 403 that it seems its no longer accepting the token (somehow expired); which is odd but one way to quick fix it might be to un-sign/re-sign the server has it will get a new token!
Just to put a bow on this: after un-claiming and re-claiming the server, then re-upgrading my Music library to Plex Music, I lost all of the fancy radio stations and metadata that comes from the Tidal integration. Re-linking Tidal restored them.
It seems like what’s needed for a more lasting fix is for PMS to detect when its token is no longer valid. I would have expected it to do something about the 403’s it was getting rather than silently ignoring them. (Also, a way to “renew” the PMS claim without unclaiming it would be welcomed. Unclaiming also forced me to individually reshare libraries.)
But its seems like the actual issue was that tidal needed re-linking, we had so other reports of folks needing to re-link (after you’re post) but what odd is that it was working else where. Or maybe I misunderstood that? If so I’m sorry!
The fact that un-claiming removes the share is a security feature. But I can see you’re point for having another way for this specific case.
To be honest reading back I wrongly assumed that this was working in some places and not others, Probably just re-linking TIDAL would have fixed it
That’s actually not the case; it was much narrower. The only endpoint that was getting 403’s with that particular PlexToken was music.provider.plex.tv. I manually tested that token against several different endpoints I saw in the logs using curl. Relinking Tidal did not fix it, neither did unlinking and linking Tidal. I did that several times over the last several weeks: prior, during, and after the Tidal outage. The fix was reclaiming PMS THEN relinking Tidal. Before relinking Tidal but after reclaiming, PMS acted as if I didn’t have a Tidal subscription.
@mikec_pt Let me know if you’d like more info, or if you’d like me to gather the last few PMS logs for you. And no worries about resharing; I knew that would be a thing.
