I’m experiencing an issue with the Plex sign-in that states “We were unable to complete this request.” when attempting to sign-in to Ombi or Tautulli (uses the Plex login).
There have been a few reports of others experiencing this issue on the Tautulli and Ombi Discord servers.
I did some digging into Plex OAuth and found that it still works when using a value of Plex Web for the following OAuth URL parameter:
context[device][product]=Plex Web
It does not seem like any other URL parameter affects OAuth.
We can patch our apps to identify ourselves as Plex Web, but obviously this isn’t the proper way to fix this. We should be identifying our individual apps with our own product name.
I believe this is an accidental bug in Plex’s authentication. I don’t believe there is any malicious intent.
Edit: The context[device][product] URL parameter is passed to the X-Plex-Product header in the request PUT https://plex.tv//api/v2/pins/link.
In other words, PUT https://plex.tv//api/v2/pins/link requires the exact header X-Plex-Product: Plex Web, otherwise it returns 403 Forbidden.
There is no such thing. There is the admin account which is already required if you enable OAuth for Tautulli. Also, you can just enter your Plex.tv username/password into the “Login with Tautulli” fields. It will still work.
Surely this works to the detriment of Plex overall. Since they are forcing 3rd party dev’s that want to support the great product that Plex is by helping the community to perform shady tactics in order to get their applications to work. It puts a bad light on all non-official development and casts us with the same shadow.
But then that would mean that they wouldn’t have more bugs every build. It’d be like they were becoming better each build… What would the world do if both Plex and Emby improved with each new build!!!
Sarcasm aside, I believe strongly in unit testing and hope Plex does consider adding more unit tests (assuming they already have some in place, if not then now is a great time to start).
All things considered the bug seems to have been fixed fairly quickly. I’ll be waiting for the release.