I see you have 1.18.9.
Do you still happen to have 1.18.8 or 1.18.7 handy to switch to as a comparison?
1.18.9 got sprung on us by Engineering. I’ve not even had chance to test it but there is a flurry of movie metadata failures.
I see you have 1.18.9.
Do you still happen to have 1.18.8 or 1.18.7 handy to switch to as a comparison?
1.18.9 got sprung on us by Engineering. I’ve not even had chance to test it but there is a flurry of movie metadata failures.
Unfortunately no, I will say though that I was on a previous version when this issues started earlier today. I updated as part of my troubleshooting, so version doesn’t seem to matter. Definitely seems like some sort of network or API issue.
On Windows (IIRC) ( I’m the linux guy and don’t know/ own / use Windows), the installer keeps older versions stored somewhere?
Perhaps you can find an older version still stored in your machine?
I think (not certain) I’ve seen others speak of it.
In Windows it’s in the Appdata/local/Plex Media Server folder.
But I can save some time and say that rolling back to.18 and.17 has not had an effect with this issue for me, unfortunately.
Andrew,
Can you capture some logs for me please?
I’m also spinning up a couple comparative VMs to see if this is Plex internal or external.
I am with 1.18.8, Do you want me to try Version 1.18.9.2571 
Thanks for those screenshots! I will use them in my testing.
Please stay with the version you’re at. I’m trying to determine if this is a PMS issue or a TMDB issue. If we have too many variables changing, I’ll go nuts (well, crazier than I am now. lol)
Phil,
Thanks for those logs. I’m working with engineering now.
We see the TMDB errors (permission denied) when attempting to retrieve the metadata.
Engineering is looking at your logs so please leave them here for now.
As a followup question, to confirm, Is this a regular PMS scan or a command line scan request?
Regular PMS scan.
Same issue as others have reported.
Server - Win10
Plex Version - 1.18.9.2571
For me, Everything was fine on Tuesday, problem started today. I was on previous version of Plex until about 2 hours ago. I saw new update available and thought it would address the issue. No change. I attempted to use “match” for 2 movies before downloading the log file zip (Predestination and The Purge)
Attached is my zip.
thanksPlex Media Server Logs_2020-03-25_20-02-44.zip (3.6 MB)
Thanks for those logs.
We are zeroing in on what is happening. 
We can’t explain the why yet but are seeing a pattern.
@MannyplexHTPC
@phil0115
@ezeitoun
@veruszetec
I have a strange request. We think we see it.
May I ask you all to restart PMS then attempt to match again ?
Please let me know your progress? Grab logs if not successful ?
Restarted and no change unfortunately. Logs attached.
Retsrat didnt helped… Attached Logs
Plex Media Server Logs_2020-03-26_01-19-41.zip (1.9 MB)
Thanks. I will start going through these.
What I expect to find is a 200 return code for TMDB followed by a 401 (which is the problem).
no change. tested with same 2 movies.
Plex Media Server Logs_2020-03-25_22-25-11.zip (2.6 MB)
I’ve finished all the logs… Thank you all. The same errors are being returned.
These errors are the TMDB access keys being rejected.
Under PMS there is a Cache and a Plug-in Support/Data directory.
We went through this exercise once before with TheTVDB and their API.
Let’s give this a shot.
Stop PMS
Remove everything under Cache
Remove everything under Plug-in Support/Data
DO NOT remove Plug-in Support/Databases . This would kill the whole PMS.
Start PMS.
Refresh All Metadata through the GUI
Thank you. We are tracking internally too.
Engineering has the information (logs) and sees what’s happening in the cloud itself.
At this point, unfortunately, all we can do is wait.
I wish I had more hope to give.
Where are the older versions (rpm/deb) of plex available at?
Older versions aren’t available.
May I ask why you request them?