silent sky
I can't connect to overseer through Plex. I tried to clear cache, stop docker service and even removed and build again the service but I still get this error :
2024-02-18T14:29:44.290Z [error][Plex.tv API]: Something went wrong while getting the account from plex.tv: getaddrinfo EAI_AGAIN plex.tv
2024-02-18T14:29:44.290Z [error][API]: Something went wrong authenticating with Plex account {"errorMessage":"Invalid auth token","ip":"::ffff:172.22.0.1"}
wild vessel
do you have the right plex app configured in your overseerr settings
silent sky
now i removed the docker
I need to install again but I can't cause there is the error with plex. So i cant se the overseer setting
I don't know if i am enough clear, let me know 🙂
solemn cedar
you're not enough clear
grim siren
FYI I am having the same issues. I currenlty can't disocver any media out of nowhere so I did a fresh install and this same thing happens to me when I try to login with plex.
silent sky
Yes it is exactly as @grim siren said !
I can't connect to oversear through Plex
It recognized my account ( through the pop-up) but I can't go to " configur Plex "
sly steeple
I appear to be having this same issue
2024-04-05T13:05:17.759Z [error][API]: Something went wrong authenticating with Plex account {"errorMessage":"Invalid auth token","ip":"::ffff:172.17.0.1"}```when attempting to sign in using my Plex account, on an existing install I've otherwise had working for many months, possibly years
DNS meme
Okay so I tried specifying an alternate DNS server for the container, which didn't make a difference
I then changed it back to the default, and now everything is working
go figure?
A temporary issue on Plex's side I think
silent sky
Well i fixed it 2 days ago
sly steeple
it's plex (again)
tidal condor
Just wanted to post same problem, then I realized it was some time since I restarted server where docker is running. I did restart and everything works now 🙂
silent sky
I just put on the docker compose config :
dns: 8.8.8.8
sly steeple
somethings breaking but it's not overseerr. some DNS issues or problems on plex's end