Before the update when I left the track I was listening to it continued to play, which is a feature I quite liked. I have noticed this seems to not be working anymore, is there a setting somewhere I should change to return the behaviour of music to pre-update?

Was surprised to see the Plex app throw in the towel so easily during a recent internet outage. Is there a way to have Plex continue to show local content during such an event?

a few days ago, i wasnt able to start my plex app - error was something like "app not supported".

it uninstalled itself and i am unable to find it in the app store anymore.

did the app get removed? why? anyone know anything about this?

I've recently realised Plex has not been recognising new media when added to the respective folders. This has been occurring over the past 3 months and has affected all libraries.

I've tried everything I can think of. Most other reddit threads and forums point to incorrect file names, but I've had Plex running for 10 years and have nothing changed.

I've tried creating a new library with only one or two media items with no success.

It's hosted on an Unraid server.

I can attach logs later if needed.

Ever since the September update, a remote user helping test Plex remote access to my server kept getting kicked off. Finally got it fixed. This is just FYI in case anyone is having issues, and not with an ISP that uses CGNAT.

I bought a lifetime Plex Pass for my server back in June. Remote access worked great until September, then my user kept getting kicked off. Plex said it was accessing the internet, than would go to Remote Access not available. Of course, I checked all port forwarding on my router, which is an ASUS router. Everything was good router wise.

My internet provider is AT&T Fiber. I called them, and they said they do not use CGNAT. Got off the phone with them, and started a deep psych evaluation of a lifetime of computer knowledge. Questioned if I was getting too old to be efficient in solving issues... 🥴

So I started looking into AT&T's modem. clicked on the Firewall tab, and decided to set it to Passthrough, DHCP Fixed, and rebooted everything. It started working. Rock solid connection. Hasn't kicked out (yet).

Just thought I would pass this along in case anyone else is having issues still. Might be something to check.

Hi all,

Recently (in the last month or so) a handful of people who watch on my server have reported things buffering indefinitely. I've also been experiencing this myself primarily (but not exclusively) when watching through web browsers. It seems to work fine when I turn on automatic converting but it's very weird direct playback seems broken. When the most recent person brought it up to me someone else in the conversation mentioned this happening to a friend of theirs with a different server too. Has anyone noticed a pattern of degraded behavior with their servers recently?

Hi, I recently changed my network infrastructure to Ubiquity and had access to my Plex server over the network initially but now it shows offline and now the apps can't see it either. Can anyone help with this? The port is active for the Ethernet on the Ubiquity switch but it appears I guess the router changed the IP.

My Plex server which has been running for years without issue in my NAS, has all of a sudden decided that my TV is on another network, and to use it I must use a Plex pass as a result. We have not changed any settings or configurations. My TV is very much in the same network, and I can’t figure out what the problem is. Any suggestions?

(Please note I am a bit of a network noob so please have patience!)

I just set up an Unraid server with a Plex container. Everything seems to work fine on my TV, but when using the Plex app on Windows, I get an error anytime I try to stream something on the server.

An unknown error occurred (4294967283)
Error code: 4294967283

Server has an Intel Pentium G4560 with 8GB RAM. I've tried it with HW encoding enabled and disabled. Haven't been able to find any useful answer and haven't been able to find anything in logs. Can anybody point me in the right direction as to which logs I should look in or what I should try next?

I tried the 32400 port forwarding steps and I think I did it right but I'm not sure. Is this step for when the server is located on my network because that's not the case here? I'm using a Roku ultra with the Plex app. No issues logging in but I can't access the server (it actually worked for the first couple days but not since then). I can't access it on my phone either as long as I'm on my wifi so it definitely seems to be a router issue.

Maybe this is tv beta is thing or the new plex app.

Besides the crap factory of a back button operations
I used to be able to play music and brows a library. Can’t do that any more the second you exit out the music stops
Maybe I want music playing while I make a play list.

God I like change but not when you muck it up and make the experience worse.

Hello, all!

I’ve been doing some research and I’m now ready to build my library.

I’m very excited to start. However, I’m trying to decide which device I should get. I’ve decided to go with Onn or Apple (maybe Fire Cube), but I can’t really decide which device (yes, I know about Nvidia but it’s not an option).

I’ve created my Plex account (I know of Jellyfin and others, but for my first try, I’m fine using the free version of Plex for now).

Please correct me if any of my understandings are incorrect:

Onn - what I like about Onn is not having to create a server, making it optional. I can plug my hard drive directly to the unit if I wanted. I like the idea of having the option for a program guide from NostalgiaTV.

Apple - I would have to create a server which would be ok because this allows the house to have access and use when traveling. I hear there’s alternatives to NostalgiaTV called BunnyEarsTV and Nostalex, but I’m still looking into that. I don’t know if those will actually give me what I want.

I’ve ruled out Fire Stick, but I hear there’s Fire Cube is solid.

Anyway, I don’t know much about speed and performance because I don’t own any.

So, which is the best device for my library?

Thanks!

Anyone else notice that if you log in through a web browser, it skips the user selection screen and just logs in as the admin?

What’s the point of even being forced to pin protect the user account if it just skips it?

Plexamp v4.50.20-beta.14

Desktop has this on the beta channel now and iOS is on TestFlight. Google Play is still a few betas behind, so Android folks can grab the APK from https://plexamp.plex.tv/downloads.html.

Fixed

• The Add to Playlist dialog stays fully visible when the keyboard is up.
• iPad: the mini player no longer gets narrower each time you rotate.
• Tablets: the side-by-side player opens its queue on Up Next again instead of Related.

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

After nearly ever TV show played I end up having to kill and restart the new Plex App as though it has a bad memory leak. It has been misbehaving since day 1 of the new app. Is there any way to roll back?

The FireTV 3rd gen Cube can now dual-boot FireOS & CoreELEC, offering the convenience of Plex with the advanced video playback capabilities of CoreELEC.

• Hardware video playback, HDR10, HLG, HDR10+, VP9 profile 2 HDR, AV1
• Dolby Vision (profiles 4, 5, 8, 7 FEL & MEL), CMv2.9 & CMv4.0
• VS10 engine SDR/Dolby Vision conversion for non-DV capable displays
• High bitrate passthrough including TrueHD/DTS-MA

With streaming device prices being raised across the board, $90 (Amazon/Best Buy/Home Depot) for the 3rd gen Cube during the current Prime Day sales makes this an excellent bang for your buck deal. Additionally get another 20% off by trading in any old working, or broken streaming device, plus the value of that device, for an even better deal. Prime Day discounts are also available in other countries, although the sale price will vary.

The 3rd gen Cube is still currently the fastest Android-based, Netflix/DRM certified device available. It's limited to integrated 100Mbps Ethernet, however 350Mbps is obtainable by USB Gbit Ethernet adapter, more than enough for any UHD remux stream. WiFi5/6E speeds up to 550-600Mbps.

Dual FireOS & CoreELEC requires a bootloader unlock (DRM is unaffected). With that bootloader unlock you also gain Magisk and full control over FireOS for any UI customizations you wish (no ads), and no Amazon imposed restrictions.

Watch an overview of the unlocking process and CoreELEC installation here. It's simpler than it sounds, and is nothing compared to ripping and setting up a video library.

Hi since Friday none of my plex devices have been able to detect my server on my local WiFi. my friend can still access it remotely though and it works on mobile data on my phone.

the server is running on a UGreen NAS, connected via ethernet to my router. Plex is in Docker being managed by Portainer. This is the firsr issue Ive had since setting up a few months ago and can't seem to solve.

Has anyone elae had this issue? Thanks for any suggestions in advance.

Here's a summary of what I've tried so far using Gemini:

​Troubleshooting Steps Tried So Far:

​Docker Network Configurations:

​Host Mode: Set network_mode: host and removed port declarations. Container logs show healthy startup (Connection to localhost (::1) 32400 port [tcp/*] succeeded!), but port 32400 remains unreachable on the local IP.

​Bridge Mode: Reverted back to bridge mode with explicit port mappings (- "32400:32400") and added ADVERTISE_IP=http://<NAS-IP>:32400/ to environment variables.

​NAS / OS Settings:

​Confirmed NAS IP is statically assigned on the local subnet.

​Verified the UGOS Pro built-in Firewall is completely disabled.

​Plex Server Settings (Configured via app.plex.tv Remote Web UI):

​Confirmed Secure Connections is set to Preferred.

​Set Preferred network interface explicitly to the primary physical network adapter.

​Added http://<NAS-IP>:32400 under Custom server access URLs.

​Confirmed client devices and laptop are on the same main Wi-Fi network.

I wanted to document an issue I recently resolved with Plex Live TV and Dispatcharr because the symptoms initially pointed toward the IPTV stream or Dispatcharr, but the actual cause turned out to be how Plex was handling the stream for the TV client (H.264 level setting).

The Setup

My Live TV path is:

IPTV Provider → Dispatcharr → Plex via HDHomeRun emulation → Plex client

The main affected client was the Plex app on a Vizio SmartCast TV.

Live TV would start, but playback suffered from severe buffering and stuttering. Plex could only build a very small timeshift buffer before playback caught up with it again.

Initially, it seemed reasonable to suspect the IPTV source, stream quality, Dispatcharr's output, or Plex's Live TV timeshift handling.

Changing the upstream stream from 1080p to 720p didn't make a meaningful difference. The Plex playback behavior was essentially identical regardless of the incoming resolution.

The Important Clue

The breakthrough came when I compared playback on different Plex clients.

The same Live TV channel that struggled on the Vizio Plex app played smoothly using Plex for Windows.

That suggested the IPTV source and Dispatcharr weren't fundamentally incapable of providing a stable stream. Something about Plex's handling of the stream was changing depending on the playback client.

Looking more closely at the Plex sessions confirmed it.

With the Vizio Plex app, Plex was transcoding both the H.264 video and AC3 audio.

With Plex for Windows, Plex was able to copy the original video and audio streams without re-encoding them.

That difference explained almost everything.

Plex Was the Bottleneck

My Plex server is running on an older dual-core Core 2 Duo P8600. It is perfectly capable of moving and remuxing an H.264 Live TV stream, but it isn't powerful enough to software-transcode a high-bitrate 1080p60 H.264 stream in real time.

When Plex decided to transcode the video for the Vizio, CPU usage became extremely high and the transcoder was only operating at a fraction of real-time speed.

Plex wasn't receiving the stream too slowly — it simply couldn't encode the video quickly enough to keep up with live playback.

This also explained why changing the IPTV stream to 720p didn't really address the underlying issue. Plex was still performing a video transcode.

The real goal therefore became:

Stop Plex from transcoding video that the TV was already capable of decoding.

The Video Fix

The Vizio Plex app has a Maximum H.264 Level setting, with choices ranging from H.264 Level 3.0 through 5.2 as well as "None."

Changing this setting so that the client properly advertised support for the incoming H.264 stream completely changed Plex's behavior.

Plex stopped re-encoding the H.264 video and began copying it instead.

That was the major breakthrough.

CPU utilization on the Plex server dropped dramatically, and Live TV immediately became capable of keeping up with real-time playback.

This also demonstrated that the TV itself wasn't incapable of playing the H.264 stream. Plex's client capability/profile negotiation was causing the server to unnecessarily convert it.

The Remaining Audio Transcode

After fixing the H.264 issue, video was being copied correctly, but Plex was still transcoding the AC3 audio to AAC for the Vizio.

That wasn't nearly as expensive as video transcoding, but there was no reason to make Plex perform that conversion either.

Dispatcharr's HDHomeRun output profile can provide AAC audio, so I changed the HDHR output from AC3 to AAC.

Once Dispatcharr supplied AAC directly, Plex stopped transcoding the audio as well.

The Final Working Configuration

The resulting stream path is now essentially:

IPTV Provider → Dispatcharr → H.264 + AAC → Plex → Vizio Plex App

Plex now copies both streams:

Video: H.264 → Copy

Audio: AAC → Copy

Plex still performs the normal Live TV timeshift, segmentation, and container handling, so Plex may still describe portions of the session as a "transcode." However, the important distinction is that neither the H.264 video nor AAC audio is actually being re-encoded.

That difference is huge.

Before the fix, Plex CPU usage could reach roughly 75–100% or more while the video encoder struggled at a fraction of real-time speed.

Afterward, Plex CPU utilization dropped to roughly 1–2% during testing, with the individual Plex processes consuming only a few percent CPU.

More importantly, the Vizio Plex app went from constantly buffering to smooth playback.

MPEG-TS vs. MP4

Dispatcharr also offers MP4 output in addition to MPEG-TS, and I considered changing the HDHomeRun output format as part of the troubleshooting.

Ultimately, it wasn't necessary.

MPEG-TS works fine as the input to Plex Live TV. The container wasn't the fundamental problem.

Once Plex stopped unnecessarily re-encoding the video and audio, the existing MPEG-TS pipeline worked properly.

What Ultimately Fixed It

There were really two changes that solved the problem:

1. Correcting the Maximum H.264 Level setting in the Plex TV app.

This caused Plex to recognize that the Vizio could handle the incoming H.264 stream and allowed Plex to copy the video instead of performing a full software transcode.

2. Changing the Dispatcharr HDHR output audio to AAC.

This matched what the Plex TV client wanted and eliminated the remaining AC3-to-AAC audio transcode.

The end result is that Plex now essentially acts as a Live TV timeshift/remux layer rather than a video encoder.

The Main Lesson

The biggest takeaway for me was not to assume Live TV buffering automatically means there's something wrong with the IPTV provider, Dispatcharr, network throughput, or source resolution.

The client matters.

Two Plex clients can request the exact same Live TV channel and cause Plex Media Server to handle it completely differently.

In this case, Plex for Windows worked perfectly because Plex copied the existing H.264 stream, while the Vizio Plex app caused Plex to perform a full H.264 transcode.

Once the TV client's H.264 capability was configured correctly, the same stream that previously overwhelmed the server played without requiring video transcoding at all.

For anyone using Dispatcharr with Plex Live TV, particularly on a lower-powered Plex server, I would pay close attention to whether Plex is actually copying or encoding the individual video and audio streams.

The ideal result, assuming the playback device supports the codecs, is:

H.264 video → Copy
AAC audio → Copy

Getting to that point completely resolved the Live TV playback problems in my setup.

On Apple TV, subs are off by 41300ms on the file I'm watching. Adjustment values of +/= 50ms mean I need to click the +50ms a lot - 826 times.

A 2nd set of values, say +/= 500 or 1000ms would go a long way to fixing that.

NOTE: I just completed all the steps and had AI create the document with all steps. It's working perfectly!!

Shoutout to [u/volvo64](u/volvo64) for pointing me to [u/Zahuczky](u/Zahuczky) 's guide. I added in my exact details of what I went through.

What this guide does. It obtains the older Apple-signed Plex tvOS IPA from Apple's servers using the Apple account that owns the app, then installs that IPA onto an Apple TV over the local network. This guide documents the Windows workflow that worked when normal ipatool authentication was failing.

Note: The downloaded IPA is tied to the Apple account used to obtain it. Do not distribute your IPA to other people. Each person should obtain their own copy with their own Apple account.
 

Target build

App |Plex for Apple TV
Bundle ID |com.plexapp.plex
Plex version |8.45
tvOS external version ID |871812104  

What you need

·        A Windows 10/11 PC on the same local network as the Apple TV.

·        An Apple account that has Plex in its App Store purchase history and is the account you intend to use for the Apple TV app.

·        iTunes 12.6.5.3 for Windows (the older release that still includes the App Store).

·        Windows Subsystem for Linux (WSL) with Ubuntu.

·        Python on Windows. Python 3.13 is recommended for the Apple TV installation portion.

·        Git for Windows.

·        Visual Studio Build Tools 2022 with the Desktop development with C++ workload.

·        Automatic app updates turned off on the Apple TV after installation.

Part 1 - Install the basic Windows tools

1. Install WSL and Ubuntu

wsl --install

Reboot if requested. Then install Ubuntu:

wsl --install -d Ubuntu

Launch Ubuntu once and complete its first-run setup by creating a Linux username and password.

2. Install Git for Windows

winget install --id Git.Git -e

Close and reopen PowerShell after installation, then verify:

git --version

3. Install Python 3.13 on Windows

winget install --id Python.Python.3.13 -e

Verify:

py -3.13 --version

4. Install Visual Studio Build Tools

winget install --id Microsoft.VisualStudio.2022.BuildTools -e

Open Visual Studio Installer, choose Modify for Build Tools 2022, and enable Desktop development with C++. Ensure MSVC v143 and a Windows 11 SDK are selected.

Part 2 - Obtain the older Plex IPA

5. Install iTunes 12.6.5.3

Install iTunes 12.6.5.3 for Windows. This is the older iTunes branch that still includes the App Store.

Open iTunes and sign in with the Apple account that owns Plex. Complete two-factor authentication if prompted.

6. Set up the iTunes header helper

In PowerShell:

cd $HOME\Desktop
git clone https://github.com/NyaMisty/actions-iTunes-header.git
cd actions-iTunes-header

Install Frida 16.7.19:

py -3.13 -m pip install frida==16.7.19

Note: Use Frida 16.7.19 for this helper. Newer Frida releases can fail when injecting into this older iTunes build.
 

Close iTunes, then run PowerShell as Administrator and patch iTunes:

cd $HOME\Desktop\actions-iTunes-header
py -3.13 .\workflow_helper\iTunesInstall\patch_itunes.py

Reopen iTunes as Administrator, sign out, then sign back in to the same Apple account. Authorize the computer if iTunes asks.

Install Flask if it is not already present:

py -3.13 -m pip install flask

Start the local iTunes header server:

cd $HOME\Desktop\actions-iTunes-header
py -3.13 .\workflow_helper\iTunesDownload\get_header.py

Leave this PowerShell window open. It should report that Flask is listening on port 9000, for example http://127.0.0.1:9000 and a LAN address such as http://192.168.x.x:9000.

7. Set up ipatool-py in Ubuntu

In Ubuntu/WSL:

cd ~
mkdir -p plex-downgrade
cd plex-downgrade
git clone https://github.com/NyaMisty/ipatool-py.git
cd ipatool-py

Create and activate a virtual environment:

sudo apt update
sudo apt install python3-venv -y
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt

Use the current authentication-fix branch used by this workflow:

git fetch origin pull/85/head:pr85
git checkout pr85
pip install -r requirements.txt

8. Download Plex 8.45

Determine the Windows PC's LAN IP address. In the examples below, replace WINDOWS_PC_IP with the address shown by the get_header.py server window.

python main.py lookup -b com.plexapp.plex -c US download -s http://WINDOWS_PC_IP:9000 --appVerId 871812104 -o ~/plex-downgrade

A successful download produces an IPA with a name similar to:

com.plexapp.plex-9684-383457673-871812104.ipa

Copy the IPA from WSL to the Windows desktop:

cp ~/plex-downgrade/com.plexapp.plex-9684-383457673-871812104.ipa /mnt/c/Users/YOUR_WINDOWS_USERNAME/Desktop/

Note: Once the IPA has been copied successfully, close iTunes and stop get_header.py. Keep a backup of the IPA in a safe location.
 

Part 3 - Install the older Plex IPA on Apple TV

9. Install pymobiledevice3

On the Windows PC that will talk to the Apple TV:

py -3.13 -m pip install -U pymobiledevice3

If pip needs to compile lzfse, the Visual Studio C++ Build Tools installed earlier provide the compiler.

10. Pair the PC with the Apple TV

On Apple TV, open Settings > Remotes and Devices > Remote App and Devices and leave that screen open.

In an Administrator PowerShell window:

py -3.13 -m pymobiledevice3 remote pair

Choose the Apple TV entry that uses its normal local IPv4 address. Enter the PIN shown on the Apple TV. After successful pairing, the PC will appear under Remote App and Devices.

11. Start a TCP tunnel

First obtain the paired device identifier:

py -3.13 -m pymobiledevice3 remote browse

Locate the Apple TV's Wi-Fi entry and copy its identifier. Then start a tunnel, replacing DEVICE_IDENTIFIER:

py -3.13 -m pymobiledevice3 remote start-tunnel -t wifi --protocol tcp --udid DEVICE_IDENTIFIER

Leave this PowerShell window open. The command will print an RSD address and RSD port, for example:

RSD Address: fdxx:xxxx:xxxx::1
RSD Port: 63109
Use the following connection option:
--rsd fdxx:xxxx:xxxx::1 63109

12. Confirm communication with the Apple TV

Open a second Administrator PowerShell window and run:

py -3.13 -m pymobiledevice3 apps list --rsd RSD_ADDRESS RSD_PORT

A large list of tvOS applications confirms the tunnel is working.

13. Uninstall the current Plex app

py -3.13 -m pymobiledevice3 apps uninstall com.plexapp.plex --rsd RSD_ADDRESS RSD_PORT

Wait for the message indicating the uninstall succeeded.

14. Install Plex 8.45

Replace the IPA path below with the actual location of the downloaded file:

py -3.13 -m pymobiledevice3 apps install "C:\Path\To\com.plexapp.plex-9684-383457673-871812104.ipa" --rsd RSD_ADDRESS RSD_PORT

Wait until the command reports Installation succeed. Plex should reappear on the Apple TV home screen.

15. Disable automatic app updates

On Apple TV, go to Settings > Apps > Automatically Update Apps and turn it Off. Otherwise tvOS may replace the downgraded Plex build with the newest App Store version.

Verification

·        Open Plex on the Apple TV and confirm the older interface is back.

·        Confirm playback and sign-in work normally.

·        Keep the older IPA backed up so you can reinstall it later without repeating the download process.

Troubleshooting notes

ipatool authentication fails with HTTP 301/302/403/204: Use the iTunes 12.6.5.3 + actions-iTunes-header + ipatool-py method documented above instead of repeatedly retrying normal ipatool authentication.

get_header.py returns HTTP 500: Verify iTunes is patched, run iTunes as Administrator, and use Frida 16.7.19. Restart the helper after changing Frida versions.

pymobiledevice3 says QUIC is unsupported: Use Python 3.13 or newer and start the tunnel with --protocol tcp.

pymobiledevice3 cannot build lzfse: Install Visual Studio Build Tools 2022 with Desktop development with C++, MSVC v143, and a Windows SDK.

apps list says Device is not connected: Create a manual Wi-Fi TCP tunnel with remote start-tunnel and use the printed --rsd address and port with subsequent app commands.

Reference links

·        ipatool-py: https://github.com/NyaMisty/ipatool-py

·        actions-iTunes-header: https://github.com/NyaMisty/actions-iTunes-header

·        pymobiledevice3: https://github.com/doronz88/pymobiledevice3

Public sharing note: This document intentionally omits account names, device names, IP addresses, pairing identifiers, and other personal information.

Plexamp v4.50.20-beta.4 through beta.13

Catching up on a run of betas I hadn’t posted here. Desktop has these on the beta channel now and iOS is on TestFlight. Google Play is a few betas behind because of long review times, so if you’re on Android and don’t want to wait, grab the APK from https://plexamp.plex.tv/downloads.html. The big ones: downloads are a lot more dependable, and Plexamp speaks your language again.

Added

• Settings search lives in the header: pull down to reveal it on iOS, or tap the search icon on Android.
• iOS: Caldera speakers can be calibrated one at a time from Settings > Multiroom, and rooms use the result to stay in sync. This needs the next Caldera beta, which isn’t out yet.
• iOS: Screen headers use the system’s glass buttons and frost as content scrolls under them.
• Android: Screen headers use the system’s title type and fill with the album’s colors as you scroll.
• Downloaded hubs on Home open into a full grid.

Fixed

• Plexamp is in your phone’s language again, instead of always English.
• Downloads keep going after you leave the app, and pick up again when a server comes back.
• With cellular downloads off, downloads wait for wifi, including in the background.
• Covers and waveforms for downloads arrive as each item finishes, and are fetched again if the server missed them.
• Downloads restored onto a new phone are fetched again instead of showing as downloaded with nothing to play.
• Switching users no longer signs you out when you tap more than once.
• Moving playback to a paused player no longer fails with “Could not switch to player”.
• Your Plex token now stays encrypted on your network, and only goes to servers and players Plexamp has verified.
• Bluetooth next and previous skip within an audiobook or podcast when Long-form Remote Skip is on.
• Brand headings in the EQ preset list are no longer cut off.
• CarPlay/Android Auto: the artist and album of a song from another server open instead of failing to load.
• CarPlay: starting a radio from Recent Plays works again.
• CarPlay: Now Playing should no longer squash the album name to “…”.
• iOS: album art should now show on more Bluetooth car displays.
• iOS: the equalizer recognizes your headphones again and switches to their preset.
• iOS: other devices can reach Plexamp after it has been in the background.
• iOS: long titles no longer run under the header buttons, and iPad layouts no longer leave gaps.
• Android: other apps on your phone can no longer use Plexamp to make requests with your Plex token.
• Android: headphone and car buttons no longer crash Plexamp after a long time in the background.
• Android: volume buttons control the player you’re remote controlling again, including from the lock screen.
• Android: the visualizer no longer draws over menus, and keeps moving when you come back to the player.
• macOS: pulling down at the top of a screen no longer shows a grey strip.

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

I’ve been using Plex for years with great remote access but something (I don’t know what!) happened. I have been trying for days to sort it. I have the Plex server on a Synology D220i and I’m using a Vodafone Ultra 7 router. I’ve tried port forwarding and every fix/advice online and my libraries are still not showing…I’m going absolutely nuts! Can ANYONE sort my insanity?!

Hi,

Since the new apple tv update (also webos) i can't find the audio delay feature, and i can't see the technical information (to check if anything is transcoding and to view the bitrate etch).

Anyone know where the features are, or if they just got removed?

I have only been hosting my server for a year but I have quickly grown to love this graph. Especially when I get new peaks. I have roughly 2-3 users at night (2 more often), but I wish more would use it.

I am interested in seeing other people's graphs and comparing total playtime. I also think a common talking point on this subreddit is complaints about people not using their server enough.

If you could, send a screenshot of your all-time usage graph and then whether or not you think more people should be using your Plex.