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

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???

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

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.

I logged into Plex today and saw that I could purchase the Plex Pass; I thought it was a mistake, and there was also an update. But after the update, the message was still there. According to my billing history, I paid €169 for the Lifetime Pass on August 31, 2020, and have been using it continuously ever since. Now, though, it seems to be gone, since my billing history also says “Ended Oct. 20.”

What happend, what can i do?

Container is up to date but oh yea....lots of port scans

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

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.

I setup a second Plex server a while ago, and I'm planning on decomming the original one once I get the new one fully up and updated. The reason is because the original is running on my 10-year old NAS, so performance isn't great. Both are still using the NAS's storage as their content source though, so keeping both going indefinitely isn't needed.

However, the one thing that's still bugging me is the content sync. I have Settings Sync enabled, so watch status is sync'd, but the new server is showing all of this old content as being newly added. Which makes sense, because it is. But I was hoping Settings Sync would sync up that info as well, although obviously it's not. Does anyone know of another way to get that info sync'd? It's annoying looking at my home screen trying to find stuff I just added, only to see content from years ago filling up the "Recently Added" list instead.

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.

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.

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?

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?

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

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.

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?

Metadata inaccuracies.

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.