Just saw a couple posts on the forum, one notes that the player team got laid off. And another that it was more than 20 people.

https://forums.plex.tv/t/2026-20-0-beta-ios-and-tvos-4k-dovi-hdr10-won-t-play-infinite-spinning-circle/943966/92

https://forums.plex.tv/t/are-the-desktop-apps-dead/935518/118

Just thought I’d voice my concerns about Plex as someone who has seen this before from other companies that once offered lifetime passes…

With the most recent updates being as bad as they are, as well as layoffs happening within their company, Plex looks eerily similar to other companies that drove themselves under and eventually restructured under a different name in order to break user lifetime pass agreements in favor of an all subscription based platform and changing to a different business model.

Just saying… I think this is a controlled burn (As in they’re purposely tanking their existing platform) and everyone who paid for lifetime passes should be watching this closely.

I can’t imagine anyone investing in the lifetime passes right now, but I would advise anyone here from Google, or who is somehow just now finding out about Plex to not sink any money into it, subscription or lifetime pass.

The :public tag installs the newest Plex every time the container starts. So Plex is always current, but the image itself apparently never gets rebuilt. Mine was Ubuntu 20.04 from 2021. Watchtower never noticed because the tag never changes.

Trivy found a pile of fixable high/critical CVEs in it, including two on CISA's known-exploited list: unrar (CVE-2022-30333) and HTTP/2 Rapid Reset (CVE-2023-44487).

Plex bundles most of its own libraries, so I'm not saying these are exploitable through Plex. But after Plex2Shell, a 2021 userland on an internet-facing box ain't where you want to be.
 

Fix: switch to the :latest tag and give up the self-updating-on-start feature.
 

EDIT: this situation also appears to apply to :plexpass and :beta tags.
 

EDIT2: it turns out the LinuxServer image offers the ability to install the current Plex at startup AND its base OS is updated frequently. I've switched to that image, no migration necessary. lscr.io/linuxserver/plex:latest

Help. I’m 1500 miles from my server. I can stream my iOS PlexAmp no problem.
Thankfully I can at least access my music.
But when I try streaming movies from the iOS Plex app, I’m showing that my server is currently unavailable.
I’ve tried accessing it through WiFi and through cellular networks.
My server is running on a Win11 machine. Plex server is running the latest version. Prior to leaving for this trip I triple checked
that my server was accessible remotely. Ports are configured per Plex instructions.
I know I’m sol till I get back home. Any advice is welcome, comments on switching to Linux, though well intentioned is a no go.
Thanks in advance.

Tldr im an idiot, package manager was broken and I didnt realize, got pwned, plex running on windows, immediately shut it down and isolated, found exploit in logs. Created an isolated network segment, shut down all services on the box that would have expected network traffic, enabled internet access on box for 2 minutes, box reached out to over a dozen c2 servers in a dozen countries instantly.

Rebuilding from metal now, oh happy days.

But yes if you think youre safe cus windows dont be dumb, investigate

How does Jelly/Emby/Infuse compare to Plex if I am NOT using the remote network connection? Everything I read here says Plex has a huge advantage to the others because of the ease of remote connectivity .... but if I don't use that???

To start this off I want to make clear that I am a complete dunce when it’s comes to networking and cybersecurity. It’s all just over my head.

I use my Plex server pretty bare bones, at least I imagine I do. It runs directly off my PC, I only house Movies and TV, if I want to watch something on the living room television I just run upstairs, flick on the computer, and head to the couch. This is all I’ve ever used it for. I constantly run a VPN as well.

My concern comes in when I begin to read through comments and posts on here and always talking potential threats to their network and data, and it kinda seems like everyone is using their Plex for much more than I am, but it could very well be I just don’t understand, because I, in fact, don’t understand what anyone is talking about. So, should I be worried running my Plex the way I do currently? Completely local? Or should I be taking other steps?

Along with this, I’ve been wanting to give server access to my family, which would just involve one other household. If I’m just using the Remote Streaming Pass, do I need to take extra steps beyond that? Is that secure on its own? I’ve been under the assumption that most people active here have their own methods of streaming remotely and that’s why so much precaution is taken and talked about, but then again, I simply don’t know and it’s hard to find an answer.

I’d really appreciate some clarity and direction with this.

Plexamp v4.50.20-beta.33

Desktop is out on the beta channel, and mobile is on its way to TestFlight and Play testing. The main ones: artist pages on a computer or tablet got a lot of attention, and Android Auto’s queue stops jumping back to the top.

Added

• Desktop: drag the sidebar’s edge to make it wider or narrower; it remembers the width.
• Desktop/Tablet: choose what an artist page’s header shows from its ⋯ menu: background art, the artist’s picture, or both.
• Similar artists, Sonic Recommendations and music service hubs follow the page’s Grid, List or Carousel setting.
• Sonic matches show their percentage and whose library they’re from in Grid and List too.
• The signal path light sits after the codec and is a glowing dot; tap either to open the signal path.

Fixed

• Desktop/Tablet: artists without background art get a header that fits their picture.
• Desktop/Tablet: the artist header leaves the first row of albums in view in a short window.
• Similar artists in a carousel keep loading as you scroll.
• Albums on an artist page no longer draw twice as it opens.
• Windows/Linux: album, artist and playlist titles no longer have their descenders clipped.
• Android Auto: the play queue no longer jumps back to the top while music plays.
• Android: music no longer stops in the background when a song changes sample rate.

Source: https://forums.plex.tv/t/221280/126

Metadata inaccuracies.

I updated the app on my nvidia shield last week and it looks really nice and all, but the photos aren’t there. The old app could view the photos folders that I have set up. The server still shows them, but not on the TV app. Can I get them back?

Can we fix it? Properly calculate the video bounding box and resize matrix? Hide the player controls when in pip mode? Android, Pixel 8 Pro

Hi All,

My plex server worked a treat with all of my movies until the update.
AAC 5.1 Movies default now to stereo on my system and it is driving me crazy, im unsure of how to fix it?

I have the following

• Nvidia TV Shield Pro
• Dolby audio processing o
• Sonos Playbar , sub and surround
• Passthrough set to Optical with Dolby digital and Dolby on
• Sony TV with Earc

Any ideas on how I can get this working again?

Many thanks

Unraid 7.3.2, 32GB RAM, Plex in a Docker container

Lately, I've been getting daily out of memory(OOM) errors in my logs and they say the Plex Transcoder is the culprit.

So far, I've tried this:

- Stopped DLNA
- Limited memory to 4GB with --memory=4g (now trying 8GB)
- Turned off Generate intro video markers (now trying with "Generate credits video markers", "Analyze audio tracks for loudness", and "Generate intro video markers" set to never)
- Using RAM for cache via --mount type=tmpfs,destination=/tmp,tmpfs-size=4000000000 --no-healthcheck (I've used this for years. It was 16GB previously, but now it's 4GB)

There was an update to Plex today so I updated it. As shown above, I set a few other things to off so we'll see what happens.

Any other ideas?

Has anyone else been having technical default with the new Roku App and Chrome Updates? I am an AV Engineer and programmer and ive been using Plex for almost 6 years now. Post the most recent update I am having connectivity issues with the Remote Access portion of the server though I do use a dedicated and routed network port as well as unrestricted 2 directional firewall access. I am also getting a blank Home Screen on just the Roku app but not on the web app despite having all the appopriate channels favorited and pinned. Anyone else having these kinds of issues?

Not specific to settings but settings is a useful example. If I go to settings, and drill down into a specific settings menu like “Experience”, how do I go back to the top level settings menu? Left on the remote goes to the server name. Back button exits settings entirely and takes me to the menu with switch profile at top. I am a bit puzzled as to how to navigate this new UI.

My Plex container was compromised in the recent Plex2Shell attack. I’ve managed to stop the malicious processes and set up a fresh, updated Plex container, but I cannot get the original infected container deleted.
I’m running Docker 24 on a Synology DS423+ with Btrfs. The old container has been stuck in removing for days, with PID 0. I’ve tried restarting Docker and even rebooting the entire NAS, but neither fixed it.
From the diagnostics, Docker seems to be getting stuck traversing a massive /run/plex-temp directory in the old container’s writable layer. It looks similar to this Docker issue: https://github.com/moby/moby/issues/42973
Has anyone dealt with this before? Is there a way to safely force the container and its writable layer to be deleted without affecting my other containers or media?
I’ve spent days on this and would really appreciate any suggestions beyond restarting Docker or the NAS, since I’ve already tried both.

Hello! I switched from using Plex on my Roku TV to a 4k ONN box and, honestly, it's been a really mixed bag. I love the improved support for .ass subtitles, but I'm constantly being plagued with buffering issues I never had with the Roku. That said, I just switched back to the Roku and it's having the same issues, so I assume it's platform agnostic. The streaming box (and TV) is connected to the same WiFi network as my Plex server, so it should all be streaming locally. However, intermittently, whenever I click to play a file I get stuck buffering; sometimes just for a few seconds, sometimes the little white circle just spins endlessly.

Dropping the quality to 720 'fixes' the issue, but confusingly even if it were a remote stream, the original quality 1080 stream should be totally manageable. My apartment keeps us on a barbaric ~12mbps upload plan, but these shows even in 1080 are less than that.

Example 1: the right is the stream box, and shows being a remote play despite being a local 192.168 address. Example 2 comparing the ONN 4k and the Roku TV... which is converting down to SD....? Even though 1080 should be fine even if it were remote. Which it isn't.

Disabling remote access didn't seem to change anything, and remote streaming (in 720) still worked. Under network settings, I have 192.168.1.0/255.255.255.0 for LAN Networks and http://192.168.0.210:32400 for Custom server access URLs. As far as I know, that's supposed to solve the issue? I also have a Pi-hole with unbound running, which may be a factor.

Any suggestions on how to fix this and not have to deal with random remote buffering on my local network?

I don’t want to disable discover completly because I use the search and watchlist function in seerr to add new content. But I don’t want content from discover on my home page.

i think it’s the same on the new TV App, but I stopped updates for now so I’m still on the old version on my appletv.

Anybody else seeing this? All I have now is recently added, no continue watching. Boo.

plezy shows the same two recently added sections.

EDIT: had to rescan all my media for some odd reason.

I just updated Plex via docker container on my Ynraid server. Now when I try to play video on web app it says there’s a playback error: There was an unexpected error during playback. Please visit our forums if you continue to experience problems.

It works fine on mobile and I still have to check Apple TV but is there a fix for this?

Update: well that’s weird I refreshed my plex tab on the browser and now it seems to work.

I’m trying to diagnose recurring whole-host hard freezes on a Plex server. The recently a few times it has stopped responding have coincided with different Plex activities: first an HDHomeRun DVR recording, and most recently adding media to a QNAP share and rescanning the Plex library.

The machine has needed a physical power cycle to recover. During the latest freeze, Plex and SSH were both unreachable. After the power cycle, Plex started normally.

Hardware and software

• Intel NUC Kit NUC7i7DNHE, board/hardware version J85489-202
• Intel Core i7-8650U, integrated Intel UHD Graphics 620 (8086:5917, revision 07)
• Kernel driver in use: i915
• Ubuntu 26.04.1 LTS
• Linux kernel 7.0.0-38-generic
• BIOS: DNKBLi7v.86A.0037.2018.0131.0828, dated 2018-01-31
• 32 GB RAM
• Two Samsung SSD 860 drives, each about 1 TB
• Plex Media Server currently 1.43.5.11029-6bf8af3f0

Plex storage

• Plex metadata: /mnt/plex-fast/plex-meta, on /dev/sdb1 (ext4)
• Plex transcode directory: /mnt/plex-fast/transcode
• Media on a QNAP :mounted read/write as NFS 4.1 over TCP
• NFS mount uses hard, timeo=600, retrans=2

Recent incidents

1. Plex was recording from an HDHomeRun when the server stopped responding. Plex logged the recording starting at 19:50:00 and the HDHomeRun stream starting about eight seconds later. The NUC was power-cycled. The tuner was an HDHR5-4DT on firmware 20260326. Plex also logged Unknown source type 'Amateur' during tuner discovery, but I don’t know whether that is relevant.
2. October 21: I added to QNAP media folder and manually rescanned the folder/library. The NUC again became unreachable and required a power cycle.

What the logs show for the latest freeze

• Plex Media Server logs show a Scanning media folders activity at 08:56:46 BST, at 74.9% complete. The log was enumerating media on /home/plex/YYYZZ from the QNAP share.
• The current scan log did not show the newly added media files before it stopped.
• The previous boot’s last system journal entries were at about 08:51 BST. The last kernel messages included: workqueue: output_poll_execute hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >10000us 2051 times, consider switching to WQ_UNBOUND
• Earlier in the same boot, the same warnings appeared with smaller counts. There was also a perf: interrupt took too long warning.
• The journal stopped without a clean shutdown entry. I found no logged OOM kill, NFS “server not responding” message, disk I/O error, or hung-task report before the log stopped.
• The previous boot’s final sar sample, at 08:50, showed about 88.8% CPU idle and 0.15% I/O wait; run queue was 1. That sample is several minutes before the final Plex scan log.
• The prior-boot Plex log’s final timestamp was 08:56:46. The NUC was power-cycled later, at about 11:09 BST. I don’t know exactly when the host became unresponsive because the logs stop earlier.
• After reboot, Plex was active and returned HTTP 200 locally. Both the metadata SSD and NFS share mounted normally.
• SMART overall-health checks passed for both Samsung SSDs. No failed systemd units were reported after reboot.
• At the last check, /sys/class/drm reported all display connectors disconnected.
• The kernel command line contains no i915 workaround parameters.

Version/update history

Plex was on 1.43.5.11029. Plex was temporarily rolled back to 1.43.4.10903, then later installed again as 1.43.5.11029-6bf8af3f0 from the signed Public APT repository. There was some earlier ambiguity because the same build had also been described as Beta. I don’t know whether the Plex build is related to the host freezes.

The normal Ubuntu repository candidate for linux-generic-hwe-26.04 was still 7.0.0-38.38, the same kernel version currently running. I have not yet tried i915.enable_dc=0, changed kernel parameters.

Recovery configuration

Plex is configured to restart after a Plex service failure, but this does not help when the entire host stops responding. The latest recovery was therefore a physical power cycle.

Questions

1. Has anyone seen these i915_hpd_poll_init_work / output_poll_execute warnings on UHD Graphics 620 or Kaby Lake-R systems with Ubuntu 26.04 and kernel 7.0.0-38?
2. Could the i915 hotplug/display polling warnings plausibly be related to a headless NUC hard-freezing, even with all display connectors reporting disconnected?
3. Would testing i915.enable_dc=0 be a reasonable next step on this UHD 620 system? Are there specific risks or better diagnostic steps?
4. Could a Plex library scan over this NFS 4.1 hard mount be exposing an NFS/kernel issue, even though there are no NFS timeout messages in the saved logs?

I have not established a root cause yet. The fact that both incidents happened during Plex activity is a correlation.

I have cleaned up this wall of text with AI, I hope its still understandable...

Is there a way to export the artwork that is currently used for all items in Plex and have it plopped as a file next to each item on the HDD?

As I've gone along, I've customized it, but usually just by selecting from the available options in Plex, so when trying out Jellyfin, etc. none of that transfers.

If I could have something automatically save that as external art, I'd love it.