Newest version of Plex Media Server 1.30.1.6562 issue

Server Version#:1.30.1.6562
Player Version#:
There is an issue with the newest version not being able to play encodes that previously worked on version 1.30.0. I tried to play a series I have encoded with HEVC that has worked on the previous version of plex that no longer works on the newest version 1.30.1.6562.
When I have tried to play any of the encodes for that series on my computer through plex it stays on the buffering wheel, and when I try to play on my Xbox series X it fails and says there was an issue with the encode. I have had to revert back to 1.30.0 in order for the encodes to work again like they previously did. May want to look into what may be causing previous encodes to fail in the newer version. Hope this issue gets resolved otherwise I will be stuck on Version 1.30.0 from now on.

1 Like

Things are being looked at, I’ve had similar issues. Hang tight :wink:

Same issue on my Rokus and also in web players. Anytime my PMS server tries to hardware transcode HEVC → H264, it fails to play on any clients that don’t support HEVC. It works fine on my clients that direct play HEVC. I’m running PMS in Docker (Ubuntu) using Nvidia runtime for hardware decoding if it helps any.

I edited my docker-compose.yaml to use the version tagged as “1.30.0”, and got it working again. I’ll update it back to use “latest” container after the problem has been addressed.

I’m not saying it’s a good idea, and I’m not running docker, but I downgraded to 1.29.2 and everything started to work again fine. Don’t know if that helps, but I’m checking this forum every day to see if there are any fixes in the pipeline :wink:

You may want to look at this first (linked below). I just spotted it, so maybe it could help?

To be honest, as part of my downgrade of PMS, I also made sure to use Nvidia 515 drivers, but wasn’t 100% sure if that helped or not (I just saw a post from another site talking about it).

https://forums.plex.tv/t/latest-update-has-rendered-my-plex-server-un-usable/826455/14

1 Like

I had to revert back to 1.30.0 cause even when it was doing direct play it would not load the file at all when it was 1.30.1.6562. there is no issues with direct play or encoding with 1.30.0. for me running it in a docker on an unraid server.

FWIW for anyone else who is/was having this issue with Plex and have been running on version 1.30.0 or earlier as a result, my Linux distribution (Ubuntu 22.04.2 LTS) received some nVidia driver, utilities, and container runtime updates on my latest apt update/upgrade that I ran today. I tried the latest Plex docker container afterward, and transcoding is working again.

Here was the full list of packages that got installed, per /var/lib/apt/history.log

Upgrade: tcpdump:amd64 (4.99.1-3build2, 4.99.1-3ubuntu0.1), nvidia-compute-utils-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libmm-glib0:amd64 (1.18.6-1, 1.20.0-1~ubuntu22.04.1), libqmi-proxy:amd64 (1.30.4-1, 1.32.0-1ubuntu0.22.04.1), modemmanager:amd64 (1.18.6-1, 1.20.0-1~ubuntu22.04.1), libpango-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libmbim-glib4:amd64 (1.26.2-1build1, 1.28.0-1~ubuntu20.04.1), libnvidia-encode-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), nvidia-kernel-common-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libsasl2-modules:amd64 (2.1.27+dfsg2-3ubuntu1.1, 2.1.27+dfsg2-3ubuntu1.2), libsasl2-2:amd64 (2.1.27+dfsg2-3ubuntu1.1, 2.1.27+dfsg2-3ubuntu1.2), software-properties-common:amd64 (0.99.22.4, 0.99.22.6), libnvidia-compute-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), xserver-xorg-video-nvidia-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libsasl2-modules-db:amd64 (2.1.27+dfsg2-3ubuntu1.1, 2.1.27+dfsg2-3ubuntu1.2), nvidia-utils-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), python3-software-properties:amd64 (0.99.22.4, 0.99.22.6), libnvidia-gl-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.3, 4.4.1-2.3ubuntu2.4), nvidia-dkms-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libnvidia-common-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libpangocairo-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.3ubuntu2.3, 4.4.1-2.3ubuntu2.4), libmbim-proxy:amd64 (1.26.2-1build1, 1.28.0-1~ubuntu20.04.1), nvidia-driver-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libpangoft2-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libnvidia-cfg1-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), systemd-hwe-hwdb:amd64 (249.11.2, 249.11.3), libqmi-glib5:amd64 (1.30.4-1, 1.32.0-1ubuntu0.22.04.1), libnvidia-decode-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), libnvidia-fbc1-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), nvidia-kernel-source-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), ubuntu-advantage-tools:amd64 (27.13.5~22.04.1, 27.13.6~22.04.1), libnvidia-extra-515-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2), nvidia-driver-510-server:amd64 (515.86.01-0ubuntu0.22.04.1, 515.86.01-0ubuntu0.22.04.2)
End-Date: 2023-03-11  12:17:52
1 Like

I tried the latest 1.31.1.6782 PMS with a fully update 515 nvidia drivers on the 10th of March (a day before your post), and I still ended up with CUDA_ERROR_INVALID_VALUE? :worried: @daverichards78 Did Nvidia change something the following day?

Looking for rollback also. I’m on 1.31.2.6783 and would like to try rolling back to before the recent spate of transcode issues. Is the db compatible? When I rollback to 1.30.0.6486 I get schema changed errors and even after 3-4 vacuums it hasn’t come back successfully.

1 Like

So my wife told me today she had issues playing back a movie on Plex today. Looks like the issue has come back. I know for sure it started working again when I performed the updates on 3-11-2023. I verified from Firefox which doesn’t support HEVC playback and forced transcoding on one of my Rokus. Today, it’s not working. So I rolled my Plex container back to version 1.30.0 again, and it works again. Takes a few minutes before Plex comes back online after the rollback because of the database migration that has to happen.

1 Like

TBH I don’t know if you can roll it back. I know I tried one of the beta versions a few weeks ago and just couldn’t roll it back. I had to restore a backup of my PMS server. So any further testing I’ve been doing I’ve been taking a virtual snapshot before upgrading. I appreciate most people won’t be running virtualisation :wink: All I can say is to restore a backup and/or to make a backup before testing newer versions.

Version 1.29.xxx is the version I’ve been sticking with just now as it seems to work fine.

I hope someone discovers the solution for this transcoding problem. I’d like to be able to put my Plex container back on the latest release so I can use the newer features when they get released.

1 Like

Found this post last night and was reading through it. Seems like the Plex team is working to fix it relatively soon. There’s already some patched installers in the thread for testing.

Yes, somebody is already working on it but it is a very complex problem, it’s not only Plex but a combination.
And I have to be honest: the troubleshooting the guys are doing is way over my Linux knowledge! :grin:

I updated my Plex container to the latest release (1.31.2.6810) yesterday, and so far so good. Transcoding seems to be working again. Already watched a few items in my libraries.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.