Sounds good. I’ll keep my settings at default moving forward.
Just installed this version (v.1.41.8.9834) and did a movie library scan. Had 3 movies come in with correct metadata. So far so good. Will update if this changes.
@drzoidberg33 We really do appreciate the work you’re doing and trying to keep up with all our noise. Keep up the good work.
1 Like
When this will be fixed for the mere mortals?
Could you elaborate a bit?
Also:
Not sure, what do you want me to elaborate on, beyond everything that was said earlier in this thread? Fully functional setup, working for years. After updating to the latest release 1.41.7.9799, basic functionality (i.e. Plex agents) stopped working. Nothing new can be matched. Rolling back to 1.41.5.9522 solves the issue completely; everything works as supposed. It looks like 1.41.8.9834 solves the issue, but it is available only for PlexPass users. So the question is, when can regular users update without the risk of losing basic functionality?
Still not working for me. Agent cannot find any movies. I have forced refresh of all metadata like I did with the others but when a new movie gets added it cannot find it with the agent
May 30, 2025 14:31:28.637 [139036534340408] DEBUG - It took 80.000000 ms to retrieve 1 items.
May 30, 2025 14:31:28.652 [139036544154424] ERROR - MetadataAgentPostProcessor: failed to find agent for identifier tv.plex.agents.movie
May 30, 2025 14:31:28.895 [139036550875960] ERROR - MetadataAgentPostProcessor: failed to find agent for identifier tv.plex.agents.movie
May 30, 2025 14:31:28.902 [139036550875960] DEBUG - It took 10.000000 ms to retrieve 107 items.
1.41.8.9834 was working perfectly agent wise but I just rebooted my server to apply a windows update and now the agents stopped working. No other changes on my end. Here are some logs.
Plex Media Server Logs_2025-05-31_06-12-58-1.41.8.9834.zip (3.6 MB)
After a few 3x or so reboots it seems my agents are back to normal. I’ll attach the previous “non working logs” and the “working ones”. Debugging is enabled for both sets of logs.
Plex Media Server Logs_2025-05-31_06-49-10-1.41.8.9834-Working.zip (2.0 MB)
Plex Media Server Logs_2025-05-31_06-12-58-1.41.8.9834.zip (3.6 MB)
Just wanted to say, after upgrading to v.1.41.8.9834 on Win11, I’ve had no issues for almost 2 weeks.
My experience has been better since upgrading but my agents still say no match when I reboot my server. I have an automated task to reboot the server at 1AM every day to get around Windows Updates killing or interfering with the plex processes. A second reboot of the server gets the agents to become responsive again and match content. I’m also running Plex on Windows 11 24H2.
I am using Linux and rebooting does nothing for me. None of these updates have fixed my setup and honestly with the way Plex has been treating the admins with their so called updates I will probably move away from Plex. You guys seem to not care about the media server side of the business as of late
Haven’t been able to use Plex Agent either since OP’s initial post. Finally after installing the latest update v.1.41.8.9834 Plex Agent is working again. Running Unraid 7.0.1 using linuxserver.io’s docker image.
Is your fix live with the latest build? I ask because i’ve updated twice and the issue remains.
@drzoidberg33 here are the logs
Plex Media Server Logs_2025-06-11_08-06-54.zip (1.1 MB)
Please enable debug logging, then restart and replicate the issue again. There isn’t much to go on when this is not enabled. Thanks!
Thanks bud for your attention. Here is the updated log and made sure everything including unraid was restarted before attempting to scrape via “match”.
I also confirmed unraid DNS is with google, also ran “optimized database” from inside plex troubleshooting.
Any insight as to what is causing the failure on me PMS?
Edit:
I changed DNS again, this time to cloudfare, it works.
Is google not supported?
Upgraded to 1.41.8.9834 on my Synology NAS resolves this for me as well. Thanks for the tip!
Even after updating to the latest version, I still have those issues.
Has anyone else got these issues ongoing?
I am having this issue now. was not an issue until like a week ago
