Plex.TV Metadata API error : Request failed with status code 404

[adzero]

Description

Plex watchlist API has changed recently and do not work anymore in Overseer and other apps.

In Overseer, errors with label Plex.TV Metadata API and message Failed to retrieve watchlist items are found in the log journal.

{
 "errorMessage": "Request failed with status code 404"
}

Problem already raised in other projects :

• Pulsarr > Fixed with this PR
• Kometa

Version

1.34.0

Steps to Reproduce

1. Enable automatic watchlist add on your main account
2. Wait a few minutes
3. Watch log journal and look for errors with label Plex.TV Metadata API and message Failed to retrieve watchlist items

Screenshots

No response

Logs

2025-08-15T07:42:50.803Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items{"errorMessage":"Request failed with status code 404"}

Platform

desktop

Device

Computer

Operating System

Windows 10

Browser

Firefox

Additional Context

No response

Code of Conduct

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

[gauthier-th]

It's fixed in develop See #4220

[Jeremy-Lemoine]

Hello, how to get this fixed into a docker image like sctx/overseerr for instance? The image seems to be based on 1.34.0 version which is not up to date.

Would it be possible to make a release version 1.34.1 with this fix please?

[buzdriver]

Hi, Yes need this as well, breaks the biggest function of Overseer imo. /BR

I wasn't running develop - works now

lscr.io/linuxserver/overseerr:develop

[An0malija]

me to fix asap please

[sabooya]

Please tag a new patch release 1.34.1 with this fix please?

[jadedeane]

Hi, Yes need this as well, breaks the biggest function of Overseer imo. /BR

I wasn't running develop - works now

lscr.io/linuxserver/overseerr:develop

Really?

linuxserver/overseerr:develop@sha256:34df625879b2509daaefeeb431e48e31de1f41efd01bf4f1aaf6276497482d33 (Overseerr b1c6e2fdbde49859a661767e9b414555aa7abc31):

[error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 404"}

[buzdriver]

Hi, Yes need this as well, breaks the biggest function of Overseer imo. /BR I wasn't running develop - works now lscr.io/linuxserver/overseerr:develop

Really?

linuxserver/overseerr:develop@sha256:34df625879b2509daaefeeb431e48e31de1f41efd01bf4f1aaf6276497482d33 (Overseerr b1c6e2f):

[error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 404"}

https://github.com/linuxserver/docker-overseerr/pkgs/container/overseerr

ghcr.io/linuxserver/overseerr:develop-version-b1c6e2fdbde49859a661767e9b414555aa7abc31

Yes - not sure which version you're trying

/BR

[baltata]

So saaaad ! It ruined the whole purpose of this kind of set up !

[sleighton]

So saaaad ! It ruined the whole purpose of this kind of set up !

Easy enough to fix, either pull the develop version and use it or edit the plextv.js file in the container yourself to fix the two instances of the url.

[An0malija]

Eh not easy.....for.me on share app hosting installing jelyseerr was the easiest options mybe the only one.. Its the same as overseer and works heheh sorrry

[baltata]

So saaaad ! It ruined the whole purpose of this kind of set up !

Easy enough to fix, either pull the develop version and use it or edit the plextv.js file in the container yourself to fix the two instances of the url.

Not that easy, on shared seedboxes, I do not even have access to docker...

[tatundria]

Still not working for me on develop version b1c6e2fdbde49859a661767e9b414555aa7abc31

2025-08-26T13:34:28.331Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items{"errorMessage":"Request failed with status code 404"}

How can I fix it?

[Jjmboni]

So saaaad ! It ruined the whole purpose of this kind of set up !

Easy enough to fix, either pull the develop version and use it or edit the plextv.js file in the container yourself to fix the two instances of the url.

It was easy to fix! Considering I installed Overseerr three years ago and don't remember the install command and that's the only way to update without re-setting EVERYTHING UP, this is the quickest fix. I'm adding steps:

Consider backing up your container. I didn't; went full commando lol. In my Windows Docker, the file is located in the container in app / dist / api / plextv.js Edit the file (Windows Docker has an Edit button) Look for "https://metadata.provider.plex.tv" near the bottom. Change to "https://discover.provider.plex.tv".
There are two lines with this url, right near each other. Change both. Save Changes. RESTART the Container.

Overseerr now properly reads my watchlist.

[darkfeeling1212]

bonjour, Le docker Overseer est sur NAS Synology comment accéder container pour faire la modification que tu propose ?

[andino66]

I seem to be seeing this error on the new 1.34.0 update as well.

[buzdriver]

I seem to be seeing this error on the new 1.34.0 update as well.

Follow @Jjmboni guide or switch to developer branch snd it should be solved. /BR

[simplyrahul]

By when can we expect a fix in stable version? On a seedbox. Cannot edit the json api file or move to develop version?

[Seshat42]

Please.....this is part of the core functionality .....> Please tag a new patch release 1.34.1 with this fix please?

[ZoltrixGFC]

So saaaad ! It ruined the whole purpose of this kind of set up !

Easy enough to fix, either pull the develop version and use it or edit the plextv.js file in the container yourself to fix the two instances of the url.

It was easy to fix! Considering I installed Overseerr three years ago and don't remember the install command and that's the only way to update without re-setting EVERYTHING UP, this is the quickest fix. I'm adding steps:

Consider backing up your container. I didn't; went full commando lol. In my Windows Docker, the file is located in the container in app / dist / api / plextv.js Edit the file (Windows Docker has an Edit button) Look for "https://metadata.provider.plex.tv" near the bottom. Change to "https://discover.provider.plex.tv". There are two lines with this url, right near each other. Change both. Save Changes. RESTART the Container.

Overseerr now properly reads my watchlist.

Thanks for the tip. I'm running it in an LXC container, but this pointed me in the right direction.

[tatundria]

Please, can anyone help me on how to fix this issue on a TNAS (Terramaster) drive with Docker Manager? This is the most important feature and the reason why I installed Overseerr in the first place.

[andino66]

Fixed it.... I installed Jellyseerr... Everything is working fine now...

Way to lose a user..

[baltata]

Fixed it.... I installed Jellyseerr... Everything is working fine now...

Way to lose a user..

Same here, pretty much the same thing, but it works...

[ZoltrixGFC]

Probably not a bad idea actually, especially with the recent cyber breach with Plex (again)...

[simplyrahul]

Fixed it.... I installed Jellyseerr... Everything is working fine now...

Way to lose a user..

I did the same. I was a new user, was choosing overseerr, then came to know jellyseerr is an alternative. This is a core required feature, not sure why it is not being pushed. Not everyone can install development version.

[BrandonMFong]

Installed Jellyseerr. Works exactly the same and has this feature enabled

[b-hayes]

been debugging this problem every now and then for a couple of month now. Glad to know IM not going crazy and its an api change. Keen for an update.

[K7TDM]

Please tag a new release for the autobuilds! I can't manually fix it on my TrueNAS. Please and thank you.

[brandmail]

I use the developers version via docker-compose, that fixed the problem for now untill the official new release

[An0malija]

jelyseerr is the way to go fuck it

[rychannel]

Obviously not an option for everyone, but since I use pi.hole for my DNS, I just created a CNAME record for metadata.provider.plex.tv and pointed it at discover.provider.plex.tv

Seems to work, still get an error in the logs but Radarr is downloading the movie that was requested.