Just swapped router, watchlist error | Seerr | Page 1

pliant copper Aug 22, 2025, 7:04 PM

#

I did change the IP address it's going to and radar/sonarr confirm when testing and it's able to see Plex as it successfully went through the library however it is failing on watchlist. There anything I need to adjust?

hexed linden Aug 22, 2025, 7:06 PM

#

Plex changed the watchlist URL, it has been fixed in develop
So you have to change to develop tag to get the fix

pliant copper Aug 22, 2025, 7:23 PM

#

Thanks for the quick response. Is there a writeup anywhere for this? Not seeing a develop tag

pliant copper Aug 22, 2025, 7:24 PM

#

hexed linden Plex changed the watchlist URL, it has been fixed in develop So you have to chan...

Is that under a certain tab? Not finding it.

#

Is this in Plex or overseer?

hexed linden Aug 22, 2025, 7:27 PM

#

What's your setup ? Docker ?

pliant copper Aug 22, 2025, 7:27 PM

#

Yeah

#

Something I have to do via docker rather than the GUI?

hexed linden Aug 22, 2025, 7:29 PM

#

You should use sct/overseerr:develop then

#

For your docker image

pliant copper Aug 22, 2025, 7:31 PM

#

hexed linden You should use `sct/overseerr:develop` then

Thanks.... It's been a long time since I messed with this so going to have to figure it out. Seems I'm using :latest

#

Heh yeah...set this up 3 years ago

#

I guess the one question I have.... If I load a new image...will it overwrite my configs and need to set it all up again?

hexed linden Aug 22, 2025, 7:34 PM

#

pliant copper I guess the one question I have.... If I load a new image...will it overwrite my...

It shouldn't change anything no

pliant copper Aug 22, 2025, 7:36 PM

#

hexed linden It shouldn't change anything no

Appreciate it...been out of the docker business since I messed with this so going to need to spend more time with this than what I currently have at the moment to figure out how to pull the new image whether it's a console command or going to git and pulling the image that way...been forever heh. Appreciate the help if ya have any other guidance that would be cool but I know some of its on me to re learn it heh.

hexed linden Aug 22, 2025, 7:49 PM

#

If you change the docker image tag, docker will always try to pull it
However if you do not change it, you will have to pull it manually
Either by doing docker compose pull in the directory where the compose file is or docker pull image:tag

#

Either way, you can do docker pull sct/overseerr:develop to be sure

#

And restart your container

pliant copper Aug 22, 2025, 7:56 PM

#

hexed linden Either way, you can do `docker pull sct/overseerr:develop` to be sure

You rock sir.

pliant copper Aug 22, 2025, 8:06 PM

#

hexed linden Either way, you can do `docker pull sct/overseerr:develop` to be sure

guessing this is because im not in the right folder?

#

though....i'd think if it was pulling from a git or something i'd reference elsewhere

#

heh i thought i was on the home stretch there

#

is the image in the mount location? that would make sense to me for mounting an image:

#

wrecked

hexed linden Aug 22, 2025, 8:09 PM

#

Looks like you are not using docker after all because the command is not known

pliant copper Aug 22, 2025, 8:09 PM

#

when i go to 5055:5055 it loads docker and i log in and everything

#

maybe im not typing in the command correctly?

#

or have the right perms

hexed linden Aug 22, 2025, 8:11 PM

#

What if you do /usr/bin/docker

pliant copper Aug 22, 2025, 8:11 PM

#

not found....i probably set it up jank back in the day :/

#

this is why i got frustrated with docker heh

#

i am running on an old version with tons of vulnerabilities

fair heart Aug 22, 2025, 8:12 PM

#

Yeah, Docker can be a beast to learn. Do you have a docker-compose.yaml by chance? Or Portainer?

pliant copper Aug 22, 2025, 8:12 PM

#

i do have portainer

#

that was one of the things that made it "easier"

#

so they said

fair heart Aug 22, 2025, 8:13 PM

#

It’s especially beastly if you’re using windows, because Docker Desktop on windows is barely the same program as on Linux.

#

Yeah, that may help actually

#

So in portainer, go ahead and navigate to the stack that is running Overseerr

pliant copper Aug 22, 2025, 8:13 PM

#

lol 345 vulnerabilities with portainer

fair heart Aug 22, 2025, 8:14 PM

#

Lmao yeah

pliant copper Aug 22, 2025, 8:14 PM

#

oof damn man im getting pulled into a meeting....i thought i could jump on this quick again but it just keeps beating me

#

i appreciate both your insight....but im gunna have to tackle this after

fair heart Aug 22, 2025, 8:15 PM

#

I feel that, I just remoted into my server from work so I wouldn’t need to walk you through it blind lol

pliant copper Aug 22, 2025, 8:15 PM

#

the wife was wanting to dl something and her watchlist wasnt working....so of course it was needed right then lol

#

yeah i hear windows sucks for this... but it was the best i had

fair heart Aug 22, 2025, 8:16 PM

#

While you’re in the meeting, I’ll post some rough a>z steps to hopefully walk you through it.

#

Since you’re already using Portainer, I guess let’s try using that. I’m hoping you set it up via that, because that will essentially have a docker-compose.yaml as the backend. And if you can use a docker-compose, that usually makes things easier. Especially on Windows…

So from Portainer’s main screen, go ahead and Live Connect to the instance. I’m betting you only have one. If you only used the default setup, it’s probably named “local” or something similar.

That will take you to your dashboard. From there, navigate to your stacks. Hopefully you have (at least) one running? One of them will be managing Overseerr. If you have more than one, just click through them and look at the “Containers” section until you find the right one.

Once you’ve found the right stack, use the Stop Stack button to turn it off.

Once it’s stopped, flip over to the Editor mode at the top. With some luck, this will have a block of yaml-formatted text. This is your docker-compose.yaml, and this basically tells Docker what kinds of arguments you want to use when running the individual containers in the stack.

You’ll likely find something that looks similar to this:

    overseerr:
        image: sctx/overseerr:latest
        container name: overseerr 
        ports: 5055:5055
        restart: unless-stopped```

#

That image: sctx/overseerr:latest is the important bit here

#

Because that’s what image you’re pulling, and it’s set to the latest branch. Change that to sctx/overseerr:develop instead.

#

Finally, there’s an “Update the stack” button below the yaml code block. Hit it, and be sure you tick the “re-pull image and redeploy” option. This will tell Docker to download the new develop image before starting the stack. That “Update the stack” button will likely spin for a little while, while the new image downloads. But once it’s done, you should get a nice happy “Stack successfully started” message.

#

Your settings should remain in-tact, assuming your volumes are properly set. If they get wiped, it’s because you have an issue with your volumes, which will need to be addressed eventually. That can also be done via the same yaml code block.

#

If you get to the Editor mode and don’t find any text there, it means you launched it outside of Portainer; Portainer can see stacks that are running even if they weren’t launched with it. But I’m hoping that if you have portainer set up, it’s because whatever guide you followed had you use it for docker-compose.

#

The reason so many Windows installations default to Portainer is because Windows doesn’t let you run multi-line commands via cli. On Linux, you can run a command with multiple lines, meaning you can just keep all of your arguments directly in command line. But on Windows, you need to use docker-compose to get the same capability, because Windows runs each line independently of the last.

pliant copper Aug 22, 2025, 10:26 PM

#

Aaaand it's going to be a bit before I get to this now...wife's orders am I right? Lol...she might be going out with friends tonight and if I can get out of that I'll be able to have the house to myself to give this a go 🙂

fair heart Aug 22, 2025, 11:38 PM

#

Lmao I feel that, my honey-do list for this weekend is a mile long. But luckily, that wall of text isn’t going anywhere.

pliant copper Aug 23, 2025, 3:32 AM

#

welp...we ended up dringing almos 2 bottles of wine and a large dominoes pizza and watching this jenny and georgia show....sometimes ya just gotta be there for the wife lol

#

ill get to this and i thnk you for the input...a lot more than what i expected!! 🙂

shut finch Aug 23, 2025, 5:45 AM

#

pliant copper

Youre inside the container

#

Docker things must be run on host

fair heart Aug 23, 2025, 7:35 PM

#

Hah, somehow I didn’t even think to check which command line they were running things in. Yeah, if you’re going to use CLI to update a container, docker pull needs to be run in cmd or powershell, not in the container directly. But again, if you used Portainer to set things up as a docker-compose.yaml, you’ll probably just want to continue using that.

pliant copper Aug 23, 2025, 11:45 PM

#

fair heart Hah, somehow I didn’t even think to check which command line they were running t...

Ok team! Im back for round 2!! 🙂

#

crack knuckles wish me luck. reading everything now

#

well... this isnt a good start... lol

#

#

i dont know if i should block out the stuff at top so i did

#

going to try and restart. the only reason i went this way was since overseer had to run on docker so had to learn it all then

#

was hopeful to be a set and forget lol

pliant copper Aug 24, 2025, 12:13 AM

#

i think i did it boys!! with your help and the help of Google Gemini i was able to get into develop!

#

pull sctx/overseerr:develop

docker stop overseerr

docker rm overseerr

docker run -d --name=overseerr -e LOG_LEVEL=debug -p 5055:5055 -v /path/to/your/config:/app/config --restart unless-stopped sctx/overseerr:develop

#

thats what i ran and im setting it up now 🙂

fair heart Aug 24, 2025, 12:23 AM

#

You’ll need to change that “/path/to/your/config” part to an actual file path. That’ll be the file path for wherever your old settings folder was located. If you leave it as-is, you’ll likely be pointing to a folder that doesn’t exist, and your settings won’t be saved if the container reboots.

#

So on mine it’d be something like “/c/Docker/Overseerr”.

#

But you’ll want it to be pointed to whatever your old folder was, so you don’t need to set everything back up again. Your settings were all saved to a folder somewhere before, so you just need to find that old folder.

#

And for that Portainer screenshot, you’d want to connect to Portainer, not access it via the Docker CLI. If it’s running as an extension, you’ll likely have a Portainer section on your sidebar in Docker Desktop.

pliant copper Aug 24, 2025, 12:29 AM

#

yeah i realized it didnt have all my settings so i just wingesd it setting it all up again... a pain but im getting there

#

i did it all in cmd. not sure where the old folder was. knowing the code for me is frustrating. i would have never figured that all out without gemini

#

i like the concept of docker... but ever time i get into it, its frustrating for me

#

i dont have a programming background... shoulda learned linux/python years ago when i was younger heh

#

was able to connect to sonarr/radarr via api so now just running all the jobs to ensure it passes through to sabnzb

#

havnt gotten something to go through so tinkering with it... thats typically how i learn things but docker just never could click for me

fair heart Aug 24, 2025, 12:35 AM

#

Yeah, I was hoping Portainer would already have a docker-compose saved, so you could use that as a starting point. YAML is extremely easy to read and debug, even for non-coders. If you want to potentially save some time in the future, you could look into creating a docker-compose.yaml file with those settings. Then updating in the future would be cd [wherever your docker-compose.yaml is saved] (to navigate to the correct folder) followed by docker-compose pull (to pull the updated image(s) and docker-compose up -d (to start the images after they’re pulled.)

pliant copper Aug 24, 2025, 12:36 AM

#

hate myself for thinking this way but i feel like there should just be an update image button in the gui lol

fair heart Aug 24, 2025, 12:37 AM

#

I mean, there is if you use Portainer lol

pliant copper Aug 24, 2025, 12:37 AM

#

yeah i setup portainer and yaml sounds familiar. pretty sure that was with the guide i used. but i even just updated portainer and was still getting the 504 so i went the route of updating overseer directly

fair heart Aug 24, 2025, 12:38 AM

#

#

504 or 404? Cuz they’re two vastly different errors lol

#

I thought you were getting a 404 before, because the image was programmed to use the outdated URL

pliant copper Aug 24, 2025, 12:39 AM

#

lemme give a look because for some reason everything is connected but not feeding to Radar/Sonarr to then push to sabnzb

#

soprry getting 502 now with the latest update it seems

fair heart Aug 24, 2025, 12:41 AM

#

502 could be DNS or firewall errors? Which URL are you using to try to connect to them?

#

Are you using something like localhost:[port]?

pliant copper Aug 24, 2025, 12:42 AM

#

it shows 8000:8000 and 9443:9443

fair heart Aug 24, 2025, 12:43 AM

#

Right, and what URL(s) is/are Overseerr pointed to?

pliant copper Aug 24, 2025, 12:43 AM

#

http://localhost:5055 is what i have for overseer

#

im not finding something similar for portainer

#

since i cant go to a url like overseer with portainer

fair heart Aug 24, 2025, 12:44 AM

#

Sorry, I meant in the Overseerr settings. Like where you connect it to Sonarr/Radarr

pliant copper Aug 24, 2025, 12:45 AM

#

#

that goes through and conencts

fair heart Aug 24, 2025, 12:45 AM

#

Ah okay

pliant copper Aug 24, 2025, 12:45 AM

#

but doesnt seem like its sending anything yet and there are things it pulled form the wishlist from plex

fair heart Aug 24, 2025, 12:46 AM

#

Anything in your Logs page about that? Is that where you’re seeing the 502 errors?

pliant copper Aug 24, 2025, 12:46 AM

#

oh no the 502 is from portainer in docker

fair heart Aug 24, 2025, 12:46 AM

#

Ohhh

pliant copper Aug 24, 2025, 12:46 AM

#

my bad

#

yeah 2 issues

#

ideally, if i could do portainer and figure the path out and pull my old config that would be best

fair heart Aug 24, 2025, 12:47 AM

#

I deadass thought Overseerr was throwing a 502 error when trying to connect to Sonarr/Radarr lmao

pliant copper Aug 24, 2025, 12:47 AM

#

because for some reason in overseer its not passing it along to radarr/sonarr

#

hahaha naaaah all good

#

its hard to troubleshoot sometimes when you dont see it in front of ya

fair heart Aug 24, 2025, 12:47 AM

#

Does Portainer show up as an extension in Docker? Like on your Docker Desktop sidebar, do you have an Extensions drop-down?

pliant copper Aug 24, 2025, 12:49 AM

#

#

hope i dont have anything i shouldnt show in there lol

#

i have portainer as a container from an image....i think....

fair heart Aug 24, 2025, 12:52 AM

#

Ah okay. Cuz there’s basically two versions of Portainer. One is an extension of Docker Desktop, and only accessible from Docker Desktop directly via the sidebar Extensions menu. While the other is accessible via browser instead.

#

I don’t know enough about the two to be able to tell the different at a glance though.

pliant copper Aug 24, 2025, 12:52 AM

#

heh better than me 😉

#

lemme look to see if anything has pushed yet

#

maybe i needed auto approve...

#

hmmm it sees the wishlist items in thre... but doesnt seem to be auto requesting them

#

#

i think thats the root of the issue

#

im going to run through the jobs and see if anything picked it up

#

got it!

#

so i had to go into my individuals plex user settings in overseer to adjust to auto approve requests

#

sent to radarr and sonarr and went to SAB NZB

#

we are good again!! 🙂

fair heart Aug 24, 2025, 1:21 AM

#

Woo! You’ll still need to adjust that settings directory at some point, or else your container won’t save its settings whenever it reboots. So you’ll likely need to redo the settings again if you ever turn your computer off.

pliant copper Aug 24, 2025, 1:23 AM

#

fair heart Woo! You’ll still need to adjust that settings directory at some point, or else ...

what.....uhhhgggg

#

i thought i was home free

#

do i have to do that with portainer?

#

The Key Component: The -v Flag
The magic command for this is the -v flag. It stands for "volume" and is used to map a directory on your host machine to a directory inside the Docker container.

The format is: -v /host/path/to/save/data:/container/path/for/data

/host/path/to/save/data: This is the directory on your computer where you want the settings to be saved. You can create this directory anywhere you like, for example: ~/docker/overseerr/config on a Linux or macOS machine, or C:\docker\overseerr\config on Windows.

/container/path/for/data: This is the internal directory within the Overseerr container where the application stores its settings. For the sctx/overseerr image, the correct path is /app/config.

How to Fix Your Setup
You need to stop and remove your current container and then re-create it with the correct volume mapping. Your data will be re-created in the new, persistent location.

Stop and remove the current Overseerr container.

docker stop overseerr

docker rm overseerr

#

Create a directory on your host machine to store the data.

This step is optional, as Docker will create it if it doesn't exist, but it's good practice to create it manually and know its exact location.

For example, on a Linux server: mkdir -p ~/overseerr/config

Run the new docker run command with the volume mapping.

You'll need to use your specific host path. The command you used before will now have the -v flag added.

Bash

docker run -d
--name=overseerr
-e LOG_LEVEL=debug
-p 5055:5055
-v /path/to/your/overseerr/config:/app/config
--restart unless-stopped
sctx/overseerr:develop
IMPORTANT: Replace /path/to/your/overseerr/config with the actual path on your host machine. For example, ~/overseerr/config or /mnt/user/appdata/overseerr.

After you run this command, a new container will be created. It will start with a fresh configuration, but now any changes you make will be written to the config directory on your host machine. This means your settings will persist forever, even if the container is stopped, removed, or updated in the future.

#

oh jeez

#

wants me to delete and restart lol....

#

dammit i did it and it lost all my settings...

#

well maybe itll save them this time

#

had a feeling that was going to happen anyways...

fair heart Aug 24, 2025, 1:40 AM

#

Yeah, that’s cuz of the file path I mentioned earlier. You’ll need to set that to an actual folder path, not just leave it as “path/to/your/directory” or whatever it was.

pliant copper Aug 24, 2025, 1:41 AM

#

i had gemini walk me thought it

#

#

so maybe itll save from now on

#

wasnt too hard to configure now that i had just done it lol

fair heart Aug 24, 2025, 1:43 AM

#

That’s the hope, yeah.

pliant copper Aug 24, 2025, 1:44 AM

#

i guess the test would be to restart docker yeah?

fair heart Aug 24, 2025, 1:44 AM

#

Or just restart that container

pliant copper Aug 24, 2025, 1:44 AM

#

yeah ha i was just about to type that

#

ill give that a try

#

we good! 🙂

#

thank you so much for the help through this

#

without your guidance and Gemini this would have been more of a nightmare lol

#

i got gemini with my pixel 9 last year for free and getting the pixel 10 for another year free of it

#

for advanced formulas in excel and this stuff its amazing

fair heart Aug 24, 2025, 6:31 AM

#

Yeah, it can be handy for basic (but also arcane, if you don’t know what you’re doing) stuff like this. If I have time tomorrow, I might actually throw together a docker-compose.yaml for you with those parameters you posted. It will help you update in the future, and it will help with future troubleshooting if you ever need to ask for help again.

fair heart Aug 24, 2025, 7:04 AM

#


version: '3'  #Probably not strictly necessary, but defining the version can be nice if future compose updates change something.

services:
  overseerr:  #create the overseerr service
    image: sctx/overseerr:develop #using the “develop” branch, but could be changed back to “latest” if future updates fix the 404 error
    container_name: overseerr #name the container “overseerr” because Docker will randomly assign one if you don’t specify a name
    environment:  #things in this section tell the container special instructions
      - LOG_LEVEL=debug #Can be handy for future troubleshooting.
      - TZ=America/Chicago #you can change this to your local time zone
    ports:
      - 5055:5055 #map port 5055 to this container. You can change the second number to something else, if you need to in the future.
    volumes:
      - /c/docker/overseerr/config:/app/config #mapped your settings folder to the listed location. 
    restart: unless-stopped  #automatically restart the container if it stops on its own. Without this, you’ll need to manually restart the container every time you reboot the computer

Create a blank .txt file, and rename it to “docker-compose.yaml”. Copy and paste this in. Save it somewhere. Maybe in C:\docker\overseerr so it’s right next to your config folder? I commented it with notes, (anything after the # is a comment, and is ignored by the program running it) so hopefully it all makes sense.

You may also want to consider making a readme.txt in that folder too, so you can leave any notes/breadcrumbs for your future self when you come back to this in another year. Maybe note the following commands for future updates:
cd C:\docker\overseerr (This will change your active directory in cmd. I’m assuming you saved the docker-compose file in that folder)
docker-compose pull overseerr (this will pull an updated image for your container named “overseerr”)
docker-compose up -d (this will run the docker-compose.yaml file in your active directory.)

pliant copper Aug 25, 2025, 12:32 PM

#

fair heart ```yaml version: '3' #Probably not strictly necessary, but defining the versio...

Thanks a ton for this. Will need to find some time to look at this. Yesterday my buddy and I were running some Ethernet for a Unifi E7 AP. New to the Unifi environment and going to be installing cameras when my siding is ripped off due to hail damage....so many projects :/

pliant copper Sep 5, 2025, 7:11 PM

#

uhhhggggg so i keep getting this ever since i updated and i did the update and now it doesnt seem like i have any containers and when i go to volumes in docker it just hangs....

#

in the bottom it says not connected to Hub

#

i wonder what could have gone wrong....

#

strangly enough its gotta be there because i can access Overseer and things just went through....soooo....

fair heart Sep 6, 2025, 3:11 AM

#

I mean, dumb question but have you tried doing what the error message says to do? Shut down WSL, then update it.

pliant copper Sep 7, 2025, 7:16 PM

#

fair heart I mean, dumb question but have you tried doing what the error message says to do...

Not dumb at all heh. I did do the update and restart docker... Would that shut down wsl in turn or would I need to run a command for that?

fair heart Sep 8, 2025, 2:59 AM

#

pliant copper Not dumb at all heh. I did do the update and restart docker... Would that shut...

No, Docker is written to use a Linux file system, not Windows. WSL is basically what Docker uses to access that Linux file system. Docker is dependent on it, so you’ll need to shut down docker, then use the wsl --shutdown and wsl --update commands. And I think after that finishes, you’ll need to reboot Windows.

pliant copper Sep 9, 2025, 11:37 AM

#

Did that and it said it was already running the latest wsl version. i still restarted just to make sure and it just spins on volumes and doesnt show any containers or images in docker... yet i can still open the web gui on http://localhost:5055/ to access Overseer. i mean... its working...but if ever i have to make any adjustments/updates via docker again i wouldnt be able to. very weird they arent showing up but i can use Overseer, Sonarrr and Radarr.

fair heart Sep 9, 2025, 2:52 PM

#

That is weird. You may want to consider saving your docker-compose.yml and reinstalling Docker. Because there’s definitely some weirdness going on. One way to check docker directly would be to open cmd and use docker ps to get a list of your currently running containers. It could just be Docker Desktop that’s bugged, (DD is basically just a front end for the underlying docker engine that can be accessed via cmd) while the actual engine is running fine.

pliant copper Sep 9, 2025, 7:30 PM

#

fair heart That *is* weird. You may want to consider saving your docker-compose.yml and rei...

Sounds good. I'll look to save that and maybe look into seeing if there's any other components that need to be updated.

pliant copper Sep 9, 2025, 7:55 PM

#

i did update to the latest docker version and i see everything now 🙂

#

hopefully i dont have the mess with this for a while now haha. the only reason i got into docker was because Overseer required it. i tried to adopt it for other things but i kept hitting into brick walls... but loved overseer too much so had to keep it haha. would love if there was a non docker based version of Overseer like how i used to run Sonarr/Radarr but since its working im not going to complain. i appreciate all the effort that goes into this and you all as a community who has helped someone whos not well versed in this area 😉

#

hopefully my challenges can go towards someone else resolving theirs 🙂

fair heart Sep 10, 2025, 12:43 AM

#

pliant copper hopefully i dont have the mess with this for a while now haha. the only reason ...

Glad to hear it got resolved. Yeah, Docker is a beast, and there can be a huge learning curve. But it’s also one of the most reliable ways to get your program to as many different devices as possible, because Docker handles all of the environment and dependencies. Like making a program that works on Mac, Windows, and Linux would usually require two or three entirely separate programs. But with Docker, it works on all of them.

#Just swapped router, watchlist error