Plex watchlist api error

[blixten85]

Description

2025-09-29T00:25:10.152Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items{"errorMessage":"Request failed with status code 404"}

Version

1.34.0

Steps to Reproduce

Plex.TV Metadata API Failed to retrieve watchlist items

Screenshots

No response

Logs

Platform

smartphone

Device

iPhone 16

Operating System

iOS 26.1

Browser

Safari

Additional Context

No response

Code of Conduct

• [x] I agree to follow Overseerr's Code of Conduct

[sazaog]

same issue. Everything is running in docker.

[MattXcz]

Same issue - develop version

[patrickschaper]

same as #4224 I guess and will therefore be fixed with #4220

[blixten85]

same as #4224 I guess and will therefore be fixed with #4220

Swapping to develop will fix this? And why is it not pushed to latest?

[blixten85]

Nope. Same shit 2025-10-01T13:22:17.398Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items{"errorMessage":"Request failed with status code 404"}

b1c6e2fdbde49859a661767e9b414555aa7abc31```

[sleighton]

@blixten85 Did you restart the container?

[blixten85]

@blixten85 Did you restart the container?

Yes ofc, twice. Also shut it down, pruned and pulled it again. I think the fix is either not pushed to develop and latest. And plex also had a breach 1-2? weeks ago Maybe that plays its role too?

[sleighton]

@blixten85 Or you are using a non-fixed container. There are multiple versions, sctx, linuxserver and binhex and not all develop tags are updated for the fix. That bit me a month ago, I finally just did the sed fix to the image to fix it all locally.

[MattXcz]

@sleighton I use proxmox lxc version from community-scripts. But urls are correct

[blixten85]

I’m using this one. From this repository

image: sctx/overseerr:develop

[sleighton]

@MattXcz There's a special way to fix that one. Try searching the issues for proxmox and see if you can find it.

Try this link https://github.com/sct/overseerr/issues/4230#issuecomment-3229102720

[sleighton]

@blixten85 I use that one, I had to manually patch mine to get it to work.

docker exec -u 0 <container_name> sh -c "sed -i 's/metadata.provider.plex.tv/discover.provider.plex.tv/g' /app/dist/api/plextv.js"

Also note that if you haven't relogged into Overseerr and refreshed the server token since the recent plex password fiasco, you need to do so to eliminate all errors.

[blixten85]

Is there no maintainer of this program?

[sleighton]

@blixten85 They fixed it back in August, the issue is that the docker images have not been generated and pushed out. Not sure if the devs that fix the code here on github are the same devs that create the various versions of the docker images (binhex, sctx and linuxserver that I know of plus proxmox and various NAS builds) but I suspect they are not.

[blixten85]

Ok, does any of the docker builds have a fix? This didn’t solve my problem. I have restarted docker. Logged out and in, no change

[blixten85]

The file seems to contain two of these 'https://discover.provider.plex.tv',

[MattXcz]

Tried relogin too, nothing changed. My files only contains 'https://discover.provider.plex.tv/', no metadata.... Still error 404

[sleighton]

If your files reflect the correct url then the problem is not the image, it's something else (assuming you are running the correct image, you might check to make sure you don't have multiple overseer's that happened to me when I tried to use the linuxserver version when I had been on the sctx version, any time I ran I was really running the sctx version, I had to delete the sctx container and images then it would run the linuxserver one.)

[blixten85]

I just installed it. But I can try that lsio one. Doing what you suggested

[JNR8]

@blixten85 They fixed it back in August, the issue is that the docker images have not been generated and pushed out. Not sure if the devs that fix the code here on github are the same devs that create the various versions of the docker images (binhex, sctx and linuxserver that I know of plus proxmox and various NAS builds) but I suspect they are not.

So there was fix a few months ago, but no release since March? Not easy to update your installaiton with fix if an update with the fix is not released.

[MattXcz]

I changed to develop version - but there is one catch - you need to rebuild the app ! In proxmox LXC :

service overseerr stop
cd /opt/overseerr
#(here change the files or switch to develop branch)
pnpm install --frozen-lockfile
pnpm build
service overseerr start

[Masong19hippows]

Having this same issue. Weird part is that I already fixed it. Noticed this about a month ago and updated my docker container to a specific develop version tag.

I then noticed today that it was only working for my account, but other accounts were still unable to sync with the same error. I then saw all of the docker containers for updates yesterday, including develop and latest. So I pulled the image, but now nobody's accounts are syncing. I also changed back to the original develop image tag I specified, and still nobody is able to sync anymore.

Using lscr.io but will probably change tomorrow to see what I can figure out.

[thedroidkid]

Having the same issue. Its driving me nuts its the one way my wife would add stuff and it would auto download for her.

[blixten85]

Having the same issue. Its driving me nuts its the one way my wife would add stuff and it would auto download for her.

You can do it via radarr and import plex watchlist and plex friends watchlist. It updates every 6 hours. You can set that to search on add, movie and/or collection. So you just add things in the plex app and then you wait. Use trash guide on notifiarr.com if you want more fine-tuned releases (it uses custom formats to match and evaluate whats what).

[theomajigga]

Having this same issue. Weird part is that I already fixed it. Noticed this about a month ago and updated my docker container to a specific develop version tag.

I then noticed today that it was only working for my account, but other accounts were still unable to sync with the same error. I then saw all of the docker containers for updates yesterday, including develop and latest. So I pulled the image, but now nobody's accounts are syncing. I also changed back to the original develop image tag I specified, and still nobody is able to sync anymore.

Using lscr.io but will probably change tomorrow to see what I can figure out.

Mine is the exact opposite. Works for everyone else, my user gets a 404.

[Masong19hippows]

docker exec -u 0 <container_name> sh -c "sed -i 's/metadata.provider.plex.tv/discover.provider.plex.tv/g' /app/dist/api/plextv.js"

found the issue. The container via lscr.io has a diffrent app path than others. Just need to modify the sed command to find the right file.

docker exec -u 0 <container_name> sh -c "sed -i 's/metadata.provider.plex.tv/discover.provider.plex.tv/g' /app/overseerr/dist/api/plextv.js"

[sazaog]

Just installed jellyseerr and everything working fine fallenbagel/jellyseerr:latest

[arlarzelere3]

docker exec -u 0 <container_name> sh -c "sed -i 's/metadata.provider.plex.tv/discover.provider.plex.tv/g' /app/dist/api/plextv.js"

found the issue. The container via lscr.io has a diffrent app path than others. Just need to modify the sed command to find the right file.

docker exec -u 0 <container_name> sh -c "sed -i 's/metadata.provider.plex.tv/discover.provider.plex.tv/g' /app/overseerr/dist/api/plextv.js"

Ran the command and watchlist sync is working now

[Tenosiey]

I would like to second this, cant really access the docker files, since I run TrueNAS Apps for overseer.

[t3pco]

Release would be great :) Workaround is fine, but not persistant