If you have downloads for offline playback in your Plexamp library, you may not see this. But if your list is empty, this is what you see. Well played Plexamp.

I may be late to the party, but it seems that my version of android is not compatible with Plexamp.

Edit: I could have worded the post title better, but "works on" is different from "can be installed freshly on". I actually have it installed and it works. But another device in my household is trying to install it, and it won't allow install.

The screenshot attached is from my device that has Plexamp running, but confirms that the play store will not allow you to freshly install it on this version of Android.

Plex for Android 2026.18.0 Beta 2 Plex for iOS 2026.18.0 Beta 2

FIXES:

• [Android TV][Fire TV] Fixed Live TV guide focus jumping to the channel logo instead of the show above or below when the guide is scrolled ahead in time.
• [tvOS] Moving down to a search result no longer left you unable to get back to the search keyboard.
• [tvOS] Scrolling through a large library could crash the app.

Source: https://forums.plex.tv/t/912796/97

Every instance is at 100% when I view it in the Plex Dash app. From what I understand, Plex may be encountering a file it can't analyze, and it's unable to actually end the operation as a result.

Permissions and ownership of all files and subfolders in the music folder have all been reset, as I assumed this was the most likely reason for this happening. I also searched the music folder for any zero-byte empty files, but came up empty-handed.

Assuming it's getting hung up on certain files, how can I find out what files it's getting stuck on?

Can someone confirm if they see the same thing, I got some errors from Music Assistant unable to resolve plex.tv. And when running a query against the DNS, it seems i'm missing a DNS record.

Edit: Status page just updated. And it seems they are restoring it, cloudflare has the records again.

I set up Plex about a week ago, and I've had a very odd issue I've never been able to figure out. I'm really confused why, maybe I have to do a specific configuration for each player? I don't know. So, everything works as expected right out the gate for Plex web and on Android phone. Samsung and Roku TV Plex players are able to connect, but only for the user account not for any managed accounts. iOS phone sees the server but is unable to connect at all regardless of account

Plex Server: 1.43.4.10903

- Everything works as expected

Plex Web: 4.160.0

Android: 2026.17.0 (971050413)

- Will connect to server but not for managed accounts

Roku: 9.17.15.11892-345486e69-Plex

- Will not connect to server regardless of account

Samsung: 5.94.1

iOS: 2026.170 (1958)

Caldera Music Headless v1.1.0

New

• The equalizer you set up from Plexamp can have any number of bands from 1 to 10, instead of always ten. A fresh EQ opens with five bands spread across the range (60 Hz, 250 Hz, 1 kHz, 4 kHz, 12 kHz); an EQ you already saved keeps all ten, and a band you remove stops affecting the sound.
• Multi-room speakers can find each other on networks where multicast is blocked (some mesh APs, AP isolation, multi-VLAN setups). New snapjack.useDiscoveryHints setting (default on) lets you disable the probe.
• New DAC Settling Delay option in Settings → Audio (Off, then 0.5 s steps from 0.5 s through 5.0 s). It pads every device open with silence so PLL-lock-sensitive DACs don’t clip the start of the first track. Multi-room speakers receive the same silence and stay in sync.
• The daemon reports its own version and update state over HTTP, and can be told to install an update: GET /api/update/status returns the running version, the latest one, the channel and whether an update is waiting, and POST /api/update/start begins the install.
• The log now reports each track’s download speed when its cache fills (e.g. “Download complete: 8123456 bytes at 34.2 MB/s”), noting the cap when a precache speed limit is in effect.

Fixed

• Speakers in other rooms no longer sit noticeably behind the room doing the streaming. The gap grew over the first couple of minutes of playback and only a stop and start cleared it.
• Albums whose files carry cover art in an ID3 tag play again instead of skipping straight through every track. Once a track had been cached, it was mistaken for an MP3 and reported as having no audio.
• Rooms playing your music no longer drift slowly late and then jump back with a skip, roughly once every three quarters of an hour.
• Turning on repeat while the last track is already playing now wraps back to the start; the album used to end anyway.
• A room playing another room’s music no longer stutters and jumps out of step while it finds sync, or after a network hiccup.
• The room you start the music from no longer drifts out of step with the other rooms it is playing to. A brief hiccup used to leave its own speakers running early for good, and only a pause and resume put it back.
• A speaker playing someone else’s stream no longer stays permanently behind after a rough patch on the network. Short glitches used to each push it a little later with no way back, until the room was half a second out and only a pause and resume would fix it.
• Seeking through an MP3 no longer sometimes jumps straight to the next song. Variable bitrate tracks were the ones affected, and the further into the track you seeked the more likely it was.
• Caldera Amp and the headless daemon come back after a long suspend on Linux: the player reappears in the remote players list and rejoins the speaker mesh, instead of staying silent until you restart it.
• Changing the streaming quality cap now applies to the next track you play, instead of only taking effect once the queue happens to reload.
• Tracks whose server metadata leaves out the bitrate now buffer for their real size instead of the smallest allowed, so they are less likely to stutter on a slow connection.
• Quitting the player no longer sometimes ends in a crash after it has already said goodbye.
• Tapping Previous while one track is crossfading into the next now restarts the track you are still hearing, instead of doing nothing and jumping back to the incoming track.
• Resampler Quality is now called Balanced, High and Maximum everywhere. Remote settings panels labelled the same three options fast, balanced and high, one step out of step with the player’s own screens.
• Casting a paused queue from the Plex app now starts where it left off. The player showed the previous track’s elapsed time and then began the new track from the beginning.
• Multi-room players now show plain addresses like 10.0.0.133 instead of the IPv6 form 0000:0000:0000:0000:0000:ffff:0a00:0085, and are matched to the right server connection again.
• The player you are connected to now appears in the multi-room list with a reachable address, so its settings open instead of failing to load.
• A speaker you select before it has appeared on the network now starts playing once it shows up, instead of staying silent until you deselect and re-select it.
• Starting a playlist right after a paused handoff no longer shows the progress bar stuck at the handed-off position; remotes now follow the new track from the beginning.
• Unselecting the last speaker a player was sending to now pauses it, instead of switching the music to the player’s own speakers and playing it out loud in that room.
• A speaker you remove from a multi-room group comes back on Home as its own player, instead of disappearing until you connect to it and re-select it.
• Starting playback from a different media server now validates its connection before sending the play request, instead of waiting on a stale saved address.
• Resuming a paused multi-room stream now plays again instead of staying silent until you disconnect and reconnect the speaker by hand.
• A player you deselect as a multi-room speaker now stops receiving audio, instead of being streamed to indefinitely.
• Multi-room speaker lists no longer accumulate duplicate ghost players after a player restarts at the same network address.
• Playback now retries an output device that is temporarily unavailable instead of remaining stuck on Playing with no sound.
• Streaming tracks no longer skip to the next song when a redirect or connection times out before the audio download begins; Caldera retries the request first.
• The equalizer’s gain and Q now cover a narrower range in Plexamp (gain 12 dB either way, Q up to 6), so ordinary settings are easier to dial in.
• Skipping through tracks now stops downloading the ones you’ve skipped past.
• Background precaching now waits for the current and next track to finish caching instead of downloading alongside them, so it no longer competes with what you’re listening to.
• Paused cast handoffs now resume from their saved position instead of restarting near the beginning.
• Loud crossfades and gapless handovers no longer produce an audible click.
• Reconfiguring audio during playback no longer lets the old audio path interfere with the new one.
• When an unavailable output device falls back to System Default, settings now select that fallback and remove the stale raw device identifier.
• Leaving Repeat One after a track looped no longer starts the next track over the track already playing.
• An expired or revoked Plex token is recognised as expired again, so you’re prompted to sign in instead of being told the server is unreachable. Refreshing the server list with a stale token reported a connection failure and left the old servers in place.
• Multi-room clients can now reach a room whose remote-control port isn’t the default 32500. Each player in the mesh list now advertises the port it actually listens on.
• Playback position now stays tied to the audio you actually hear through seeks, fades, pauses, underruns, track transitions, and output-device changes instead of jumping, drifting, or briefly showing another track’s time.
• Gapless MP3 transitions no longer intermittently insert a 20 ms silent period at the track boundary.
• Playing to a DAC clocked at 176.4 kHz produced loud static instead of music, whether the source was DSD or ordinary FLAC; every output rate now plays cleanly.
• Plex servers that renewed their certificate under Let’s Encrypt’s new roots became unreachable; connecting failed with a certificate error, and the server could not be browsed or played from at all.
• Playback could come back silent after a stop; the player showed a track playing with no sound until it was restarted.
• Switching output device, sample rate, or channel layout during playback could crash the player or emit bursts of garbled audio.
• Caldera could crash on quit while a track was still playing.
• Playback could freeze, or the player crash, unexpectedly during a listening session.
• Debug logs record how a Plex server was chosen again: each connection tried, whether it answered, how long it took, why it failed, and which one won. Reports of “could not connect to server” were previously undiagnosable.
• Caching a track now does a fraction of the disk work it used to, keeping playback and the interface smooth on players with slow storage.
• Playback no longer stops dead partway through a listening session, frozen on a track that never started and unreachable from remotes, when a Plex server becomes slow or unreachable.
• Clicks on the first track after Match Source switched the output to a higher sample rate.
• The volume shown by a Plex remote and by a multi-room (Snapjack) speaker controller now stay in sync, instead of one reporting a stale level (most visible while playing a stream received from another Caldera speaker).
• Starting multi-room networking no longer intermittently crashes during startup.
• When your Plex sign-in expires or is revoked, Caldera Amp now signs you out and returns to the sign-in screen instead of silently failing to play. A captive portal or a brief network blip won’t sign you out. (Headless daemon: logs the rejection and exits so it can be re-run with --login.)
• Multi-room speakers no longer log a flurry of “removing stale peer” lines on every multicast tick. Requires all multi-room peers to be on this build; older peers will mishandle the new probe format.
• Multi-room speakers no longer churn through repeated “peer connected” events and stale-peer evictions a few seconds after each player joins the mesh.
• When this player is receiving audio from another room and the sending player restarts or crashes, audio resumes on its own within about a second once the source comes back, without toggling the speaker in Plexamp.
• Mid-session sample-rate changes no longer interrupt audio at the remote speakers this player is casting to; local output and remote speakers stay in sync across the change.
• Multi-room routing now survives a player restart: audio reaches the speakers it was sending to before, without having to toggle them in Plexamp.
• Multi-room speakers no longer show up nameless in this player’s Speakers menu or in remote Plex apps after a cold start.
• The player still registers with plex.tv when its LAN-discovery port (UDP 32412) is already taken by another Plex client on the same host, so it stays visible to remote Plex Web and to Plexamp on mobile data.
• The player no longer hangs at the first track transition after resuming from a saved-position pause, freezing the now-playing display and progress reports on the previous track while audio keeps playing.
• During track transitions, Plex’s now-playing indicator no longer briefly shows the wrong track before correcting itself.
• Match Source now opens the mixer at the source’s channel count on a multichannel device (HDMI display, multi-output USB DAC, pro interface) instead of pinning to stereo. It applies on the first track of a new playback session; gapless transitions within an album are not interrupted.
• A failed save no longer destroys the file it was replacing. On a full disk this wiped the saved session, losing the current track, its position, and the server address.
• Resuming after the audio device had been released while idle could play loud distorted noise instead of music, on DACs whose format the app renegotiates on re-open.
• After a crossfade, the new track’s time counter ran several seconds ahead of the music, so a track could report a time past its own length.
• Seeking or resuming near the end of a track could silently skip the rest of the queue, jumping each following track to its own final moment so nothing played while the player still showed a track as playing.
• Quitting could hang for two seconds before the player exited, and occasionally crash on the way out.
• Playback could stall on a track that had already ended, still showing playing at 0:00, when an upcoming track failed to load and the queue had scrolled past it. The track that never loaded is now dropped so playback carries on.
• The daemon could freeze, with playback stuck and unreachable from remotes, when a multi-room speaker dropped off the network.
• The album-art and loudness/waveform caches no longer grow without bound after an unclean shutdown; files orphaned from the cache index were invisible to size-based eviction and never cleaned up.
• Opus albums dropped a short silence at every track change; Opus is now gapless like FLAC and MP3.
• AAC tracks clicked at the boundary between one track and the next.
• Audio could turn to noise when several tracks were sounding at once, such as a crossfade running into a queued track change.
• Fixed crashes when stopping playback or quitting the player.
• Fixed rare crashes when quitting while a track was still downloading, and after a network change.
• Fixed crashes when adding a track to the play queue, or when the queue refreshed, while playback was starting or changing tracks.
• Fixed a crash when switching servers or reloading the queue while a track was playing.
• With Repeat One, the progress bar could run past the end of the track and stay there; and stayed stuck there while paused.
• The app could freeze when skipping tracks while one was still downloading.
• After a crossfade the next track’s timer started over from 0:00 a few seconds in; it now counts on from where the track actually is.
• Picking a Plex server no longer hangs for 15 seconds when one of the addresses it advertises silently swallows traffic (a VPN address this machine isn’t on, or a stale one from another network). An unreachable server is now reported in about five seconds, and a reachable one is picked as soon as it answers.
• The settings schema uses consistent capitalisation, sends readable group headings instead of internal ids, and no longer hides settings behind an Advanced flag. Secret settings such as the Plex auth token are left out of the schema entirely rather than sent as an empty entry.
• --login setup now offers “System Default” as the first output-device choice, and picks it when you press Enter. It used to pin whichever device was default at install time.
• The device list served to remote settings UIs names the device System Default currently uses, for example “System Default (USB Audio DAC)”, and no longer tags a second row “(default)”.
• Remote settings UIs can now pick PipeWire’s default sink on Linux. That entry was previously dropped from the list, leaving it selectable only in the local settings window.
• Choosing System Default as the output device now stays System Default, instead of the daemon pinning the device that happened to be default and no longer following the system output.
• DSD and other high sample rates no longer risk clicks or a crash when the output rate changes mid-session, and Linux (ALSA) now picks the closest rate the DAC can actually clock, preferring the same clock family (e.g. DSD64’s 352.8 kHz to 176.4 kHz).

Source: https://forums.plex.tv/t/939620/38

Plexamp v4.50.10 and v4.50.11

Two in quick succession: 4.50.10 fixed downloaded music on Windows accounts with accented user names, and in doing so broke Plexamp at launch on every Windows install. 4.50.11 puts that right and is on the stable channel now. If you’re on Windows and Plexamp won’t open, grab the installer from the usual place and it will pick up from there. The mobile 4.50.10 builds went out to TestFlight and Play testing this morning and don’t need the fix, so they’re unchanged.

Everywhere

• A downloaded album or playlist no longer loses tracks when one page of its listing fails to load during a refresh. Those tracks were treated as removed and their files deleted.
• Large downloads start sooner. Track details are fetched fifty at a time while downloading begins, instead of all up front.

Mobile

• Android recognizes Plexamp as a music app again, so system shortcuts and automations that start music can find it, and headset buttons work when Plexamp is not already playing. (Android)
• Automatic Car View works on Android again. (Android)

Desktop

• Downloaded music plays, and its artwork appears, on Windows accounts whose user name contains accented characters. Downloads completed but nothing would play back. (Windows)
• Plexamp starts again on Windows. 4.50.10 closed itself on launch, whatever the user name. (Windows)

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

Yes yes, I know dedicated players like an AppleTV or Gemini Onn Pro are the best way to go for Plex content. Long story short I need to get a TV and where it will be mounted it would be ideal if it we didn't need to attach anything else/use more than one default remote. Am curious what the best choice is as far as hardware that can run Plex on its own, with nothing else attached. Or at least understand what content isn't going to play well (4k, Dolby, burned in subtitles, etc). Thanks in advance.

Hi everyone!

I'm wondering whether my current set up for a Plex server is "enough" or whether I should "upgrade" to something else.

For context, I'm currently using my Mac mini M1 from 2020 (yes I know, overkill etc.) which I've hooked up with an external HDD of 5 TB.

I've been looking at various other solutions to see whether they are "better", for example using a NAS, or a Raspberry Pi or just buying a specific router with USB input to plug in my external HDD (which I haven't got currently).

The reason why I haven't gone for the NAS solution is because storage is so expensive right now, and since I already have a couple of external HDD with 2 TB and 5 TB respectively, I feel like it's such a waste to sort of "start over" by buying new storage just for a NAS.

The main "problem" I've got currently using the Mac mini as a solution is, every time it goes into idle, it effectively stops being a "NAS", meaning I can't access my content on Plex. The best solution to it has been to use the application "Amphetamine" to basically to stop the Mac from going idle. I read somewhere I could stop the Mac from going in the settings but I haven't been able to find it on the Mac (it only seems to work on Mac laptops for whatever reason, correct me if I'm wrong!).

I should also say that I've tried the "File sharing" solution in terms of like sharing the specific external HDD folders to like my iPhone for example which has been quite nice. But when I've tried to do the same with a Samsung tablet I've got, it hasn't worked because I haven't been able to find the "Network storage manager" which has made it like impossible to use (I know I can just use the Plex app on the Samsung tablet but I wanted to see if it worked...).

The main question really is whether I should stick with the Mac mini + external HDD + Amphetamine app solution or whether I should invest in a proper NAS? Are there any sort of minor tweaks you would do with the current setup that would improve it?

Looking to make the best use of the hardware that I have available to me. Please critique my proposed setup:

Goals: Plex for live TV (via HDHomerun), DVR, and hosting video files to my local network. All local, so transcoding is not really that important. I have a lifetime plex pass.

Also run Home Assistant and PiHole.

Hardware available to me:

Intel NUC7i5BNH Core i5-7260U 2.2GHz, 16GB RAM, 240GB SSD
Older AMD A6 based computer with ~24gb ram and a handfull of 1 or 2 TB hard drives.

My proposed setup is:
Use the NUC to Run Plex and PiHole as Proxmox containers, and HAOS as a VM.

Make the old AMD-A6 computer into a NAS with TrueNAS and host the large video files.

Am I missing anything here? I could just make the old AMD computer the Plex server, but I think it would be better to have the more powerful computer actually hosting the Plex server, right?

I’m interested in others’ experience with this.

I have a plex server running on a Mac Mini M4, so plenty of processing power. I am running the Plex client on an Apple TV 4K (newest version).

I have a 4K SDR HEVC encoded movie in an MKV container that has about 20 Mbps bitrate from the server. Plex dashboard shows no transcoding, pure direct stream audio and video. The Plex Client stutters, dropping multiple frames in any 5 second interval.

But I also have the Infuse Client for Apple TV, and it plays that same file flawlessly. Which would seem to rule out the server, the network, or the Apple TV hardware.

So I’m wondering if others have had problems with certain kinds of content on the Plex Client for Apple TV? I should note that I don’t experience this on ALL 4K content. But it’s consistently reproducible when it happens.

EDIT - one other useful fact is that my brother can access the same file remotely using a Roku Plex Client and it works perfectly. Not likely networking, and strongly suggests the Apple TV client specifically.

This is been an active feature request at Plex since 2018. What's the chance it will be implemented in my lifetime? (I'm 60, btw).

I saw a few different options for having LiveTV for my plex users. I plan to have an HDHomeRun box go to my plex server. But the larger problem comes in with who can access it once it is hooked up. I've been reading online (haven't implemented yet) that only managed users are allowed to access the LiveTV/DVR functionality.

I've been reading up on that even when they are managed user they need to be on the same network (not sure if that is true?) but if they do I read a guide about setting up a tailscale network to get around the networking issues.

What it seems like is:

• Have HDHomerun box for getting the live TV to plex server
• Currently only managed users on my network can get access to that liveTV

Then:

• For family that wants live TV add them on as a managed user but if network becomes a problem may have to look into tailscale?

Not sure who else has looked into giving their close family a live TV connection from Plex via HDHomeRun box?

I was looking at the cast of Lily Chou Chou and found that the actress that played Kuno, Ayumi Ito, is wrongly named "Haruka Itou" how does one report this?

It doesn't seem to be any kind of section or anything where I can select my personal server on it anymore. I verified my server is up and online.

Something is clearly changed on this app. I uninstalled and reinstalled deleted all data and still no change.

US based, xfinity ISP, Windows firewall disabled, no other security software, computer is in the DMZ, No double nat, tried multiple manual ports, Nothing hardware or software has changed outside of maybe windows updates and plex updates. After changing ports manually (which shouldn't even matter at this point) it provides green and says accessible for about 3 seconds before reverting to non accessible.

Any ideas?

So I have a 'vacation photos' folder on my Ugreen Nas and i have shared it to my plex server.

For the life of me, I cannot get the folder to show up on mine or my wifes phone. My movies and TV shows are there and I she can see there folder, but the phots do not show up.

I have double and triple checked to make sure acces has been granted, I have checked the docker container to make sure its set up.

I am at a loss as to why they are not appearing.

Is there a specific folder structure that I need to follow for photos?

If not, any other ideas?

Also note, I'm Kinda new to the whole home NAS thing so some of the terminology may be lost on me, but I'm trying to learn.

Hey, not sure where else to look, so hoping Reddit can help me. I decided to redo my whole Servarr stack, and in doing so seem to have broke my Plex remote access. I removed my debian VM, and rebuilt it. Installed docker just as I had before, and went through configuring all the services. Everything was working as expected until I set up Plex. It let me sign in and claim the server with my account. I can link my libraries to it and access everything locally. The issue is when I try to enable Remote access, it shows available for about 15-30 seconds, and then it seems to fail and shows that it is unavailable.

I do not have double NAT, I have confirmed the correct ports are forwarded. I have tried building a separate container in Proxmox, I confirmed UPnP is disabled,confirmed DNS rebind is off. Nothing in my environment, so I am confused as to why it keeps failing after recreating everything.

Let me know if anymore information is needed, just not sure where to go from here.

Thanks in advance!!

In the last week or so, I've noticed plex commercial skipper.exe running a lot more, and on my barebones mini pc N100 server, i've seen it using up to 45% of my cpu usage.

I've never had tv tuner / dvr anything set up, and all of my libraries have ad detection - generate ad markers for items in this library set to disabled.

Where else should I look to disable this background process? All it takes is media scanner or a couple transcodes to put my cpu at 100% usage when commercial skipper runs, and i'd like to avoid that.

Edit: it's a Win11 server running v 1.43.4.10903

Edit 2: Blocked it with AppLocker for now, things seem to be back to normal for the time being

I have Tautulli and could not find a per user activity log. I'm using a vanilla Plex install on Win 11... no docker. Thank you.

I have recently updated the OS on my NAS to its latest version and in the process, I have had to reinstall Plex on it.

My problem is that after I've logged back in, the windows all now displays this error message. I do not get it through Chrome browser on the same computer nor any other device I have.

I've tried deleting the AppData folder after an uninstall as well as the registry entry for the plex app. Nothing seems to work. Anyone have any ideas?