#Overseerr fails to authenticate Plex sign-in

1 messages Β· Page 1 of 1 (latest)

grand oyster
#

I've set up a Cloudflare tunnel on my unRaid machine so that I could securely proxy my Overseerr container.
For the most part everything seems to be working. Except that when we try to sign in to Overseerr with our Plex account we get hit with a failure to authenticate.
I'm assuming that there's a setting in Overseerr that I'm missing. Like maybe the "Enable Proxy Support" option?
I don't know. So before I start changing anything I wanted to ask for some help and feedback.
Thanks!

grand oyster
#

Also!
This failure only shows up when trying to sign in on mobile.
Signing into Overseerr with Plex on desktop works just fine.

peak path
#

Needs logs to even begin to help πŸ˜„

grand oyster
grand oyster
#

@peak path πŸ‘‹

grand oyster
peak path
#

Please follow the steps there to share it. Use a gist πŸ˜„

grand oyster
#

Woops. I just saw the download zip and immediately went for it πŸ˜…

peak path
#
2023-06-22T10:20:53.833Z [error][Plex.tv API]: Something went wrong while getting the account from plex.tv: Socket connection timeout 
#

you're having issues connecting to plex.tv

grand oyster
#

Seems very broad. I don't understand what the problem could be because I was able to sign in at my desktop. It's just a mobile issue. How should I troubleshoot that?

peak path
#

It only fails on mobile? Thats odd. That error is happening on the server side so it shouldnt matter if its mobile or desktop

grand oyster
#

Which is why I'm confused and am here. πŸ™‚

grand oyster
#

@peak path I've been searching around a lot and I see that a lot of people have had this issue before. But all of the posts are locked behind the shut down subreddit...

grand oyster
#

@peak path I've also found that it's not only on mobile.
I had a friend try to do the sign in at their desktop and got the same error.
Looking at the logs in Overseerr it's saying that there's an "Invalid auth token" along the Socket connection timeout.

grand oyster
#

@peak path So I removed all instances of Overseerr from authorized devices in my Plex server, signed out from everywhere, and tried signing back in. And now I'm running into the same problems everywhere. I'm basically locked out now.

#

...Should I just restart and try again?

rustic perch
#

I'm having the same issue currently, "invalid auth token" in my logs both on local network as well as through a CF tunnel

rustic perch
#

can confirm this is an overseerr issue as rolling back to 1.32.5 fixes it

peak path
#

Nothing auth related was changed in 1.33 so that’s unlikely the reason it’s fixed.

rustic perch
#

could be an issue with the binhex overseerr container then. Seems the only people ive found online with this issue are using Unraid, so most likely using that container. Myself, OP and BrynPalmer from the unraid forums all are running Unraid
https://forums.unraid.net/topic/122509-support-binhex-overseerr/?do=findComment&comment=1274741

peak path
#

I run overseerr on unraid but I use our main image. I suggest you do the same πŸ˜„

grand oyster
#

I assume that would hotio, right?

peak path
#

Our official image is sctx/overseerr

#

Im not saying to avoid binhex, but I am saying that it's hard to support other images because if they break things its out of our control.

#

hotio is pretty dang stable though I think πŸ™‚ LSIO too afaik

grand oyster
peak path
#

Ah right on unraid the official image is under diamkill. Been meaning to take over that but havent had the time. But you can just update your existing setup to use our image for the repository and adjust the mounted config directory and that should get you where you need to be.

grand oyster
#

I think I know what you're saying..

..but I don't know how to do things πŸ˜…

peak path
#

If thats confusing, just use the diamkill one. πŸ˜„

grand oyster
grand oyster
#

Because, without knowing any different, basically all of my containers are binhex.

peak path
#

Basically you would just update your existing app on the docker page in unraid to point to my repo instead, but you would also have to change the mounted config path to /app/config instead of what is normally just /config

grand oyster
peak path
#

yes

grand oyster
#

@peak path Could you explain the reason to move the config path to /app/config?

peak path
#

in our official image the internal container path for the config directory is /app/config

grand oyster
peak path
#

yes

grand oyster
#

I'm just keeping notes so I know what all I'll be changing for the other apps as well.
You've been an amazing help

#

And my original issue with not being able to log in has been fixed, and my users are able to make requests now.

grand oyster
# peak path yes

I have a quick question about changing the repository.

So all of my *arr apps are from the binhex image. And all the config folders start with binhex. Could I just change the names of the folders and keep the same path with the new repository image, so that I can maintain my configs?