I just built this Plex server and added my media libraries to it from my network storage. These are the exact same libraries with the same filenames that were added to my old Plex installation, where metadata worked fine. On the new server, the Plex metadata agents are failing to match anything at all. Even when I go to fix matches, I am getting no results.
As a test, I switched my Movies library to The Movie Database, and refreshed the metadata which successfully pulled in data for my whole library (but of course, now I have the “upgrade libraries” nag in Plex).
Additionally, the Plex DVR guide data is showing up as “not found” even though I had live TV guide data on my old server just fine.
Id make sure you are using the most current Scanner and Plex Agent. Im seeing a lot of logs from the older agents. Id also make sure you disable prefer local metadata.
As mentioned, I switched one of my libraries to the older agent intentionally because it actually works, unlike the newer one. | already made sure I disabled prefer local metadata. I switched all libraries back to the new provider and once again, it cannot find anything at all.
No VPN. My DNS is a bog standard unbound resolver, with the exception for a couple of local zones, which are domains I own and would have no impact on Plex functionality.
The only thing network related that I can think of is that I have fiber internet from a smaller ISP, and I seem to frequently find sites that block the IP range I’m in (or flag it for bot mitigation… and sometimes they think I’m in the UK not the US)
I won’t pretend to know what a recursive DNS is.
I only know regular DNS lookups. Which always require your own DNS resolver to ask some other DNS server higher up in the hierarchy to provide the answer, when a different domain than your own local one is queried.
Then you fundamentally do not understand DNS at all. A recursive DNS server is what handles what you refer to as “regular DNS lookups”. DNS is a wholly open system, literally anyone can run their own recursive server. All the Google/Cloudflare/ISP etc DNS servers are just recursive servers that you have no control over (and that those companies often use to track your activity for marketing purposes, but that’s a rant for another day).
If you are confident that your DNS resolver is indeed returning a correct result for metadata.plex.tv, then the metadata bug is probably not DNS related.
However, when I check meta.plex.tv I get records back as expected (also checked a few other domains listed on status.plex.tv and they all return records as well, DNS does not appear to be the issue here)
Okay, so what is the next steps here? Is there any way to open a support ticket or something and get this looked at further?
I mean, the TV and Movie metadata isn’t the end of the world, since I can just switch back to the old metadata providers which are actually working. I can probably do the same with my Music. It is annoying that there’s no way to turn off the nag messages to “upgrade libraries” though.
Does the DVR Guide also operate through the same metadata service? Because I still cannot add my tuner, due to the DVR Guide saying it can’t find data for my location (even though it was working fine on my old Plex server). Since it can’t find the guide data, it won’t even let me add my tuner to Plex, and I can’t find any way around it unless I have an XMLTV guide subscription which I don’t really want.
I am not exactly a Linux expert, but a first look at your logs telly me this, which is puzzling: [192.168.192.232:48976 (WAN)] PUT /myplex/refreshReachability (12 live) TLS GZIP Signed-in Token (ardichoke) (Firefox)
It is classifying a private network address as “WAN”.
Are you running PMS in a container?
Nope, running on bare hardware. Probably misconfigured the LAN Networks setting, I used the subnet prefix notation (force of habit, most things in my industry use prefix notation these days), I take it that setting wants subnet mask notation only.
I don’t know what exactly you’re referring to with this.
I know that Plex accepts both this 192.168.1.100/255.255.255.0 and CIDR notation 192.168.1.100/24.
If you put in more than one range, make sure to not insert a space character after the comma.
/24 (or whatever number of subnet mask bits) is also referred to as prefix notation, it’s shorthand for CIDR prefix.
I did put in two networks, comma separated, no spaces. Do you know offhand if the server needs to be restarted to pick up this setting? I went back and redid the configuration, but it still is showing connections in those ranges as WAN.
Sorry, I wasn’t specific enough. Yes, I put the two networks into the “LAN Networks” field.
Yes, I activated this as well, although it shouldn’t apply to my setup as my client can talk to the Plex server directly and doesn’t go through my WAN IP.
Alright… well… I solved my initial issue. The latest release of PMS is just broken when it comes to the Plex metadata agent. I downgraded from 1.26.0.5715 (the current version when you go to downloads on the main website) to 1.25.9.5721 (the current version in the apt repo). After downgrading, the plex metadata agents and the DVR guide are all working now, so this all seems to be an issue with that specific version. This does make me wonder though, why is that still the version being pushed on the main website?
I am experiencing problems with updating metadata on version 1.25.9.5721.
When i want to add or update metadata for music files by using the agents, it is just updating the album title. And also the Refresh metadata is greyed out after the initial update. Does anyone else have this problem?
