Hardware transcodes (from Linux based server) crashing on Windows client

Plex Media Server
1

Server Version#: 1.19.3.2852 (have also tried on 1.19.4.*)
Player Version#: 1.11.0.1215-1d8c460c

Proxmox host with Ryzen 1700, 16GB of DDR4. PMS running in an Ubuntu 18.04 LXC with 4 cores/4GB RAM. Quadro P400 passed through to the LXC and confirmed working with other transcodes.

When playing videos on Plex, whether in Plex for Windows or in browser from both a reverse proxy and via app.plex.tv on a Windows computer, I receive Playback Errors when trying to engage the transcoder by setting Quality to convert (for example to 4mbps).

An unknown error occurred (4294967283)

Error code: 4294967283

Hardware transcoding does appear to be working on other devices (Android, Samsung TV) and I’ve confirmed my GPU passthrough appears to be working, as ffmpeg can use NVENC and NVDEC for transcode tasks.

I’ve attached logs from an example instance where I specifically triggered the failure. In the past, I did not experience this error and have been able to play HW transcoded videos on Windows clients without issue. I did have to reinstall NVIDIA drivers on my server right before this issue appeared, but I’ve now tested on both 440.62 and 440.84 and the issue occurs identically. Windows did recently update to the 2004 feature update, and I wonder if that may be causing issues?

Unable to find client profile for device; platform=windows, platformVersion=10.0.19041, device=, model=standalone plex

PFW-transcodefail.log (47.7 KB) PMS-transcodefail.log (389.0 KB)

2

Is there additional information I should be providing? Anybody have input?

3

Search the forums for “ProxMox” and review the threads.
Proxmox is not supported but there is a very helpful user community.

4

For clarification, I don’t believe this error is related to Proxmox, since GPU passthrough is confirmed working with other applications inside of the container and hardware acceleration through PMS is also working via other players. I have confirmed hardware transcodes working on the Android client and a Samsung TV with this exact configuration, as shown by (hw) showing in the Plex dashboard and Tautulli.

The only circumstance that hardware transcoding isn’t working in is when playing on a Windows 10 client that had worked up until the past couple of weeks.

5

This is a client issue only?

I will remove the server-linux tag. Please ping me if this is in error.

6

I suppose I’m not entirely sure if the issue is stemming from the server side or the client side, which is why I tagged both. On the server side, I am getting a log error message:

ERROR - Unable to find client profile for device; platform=windows, platformVersion=10.0.19041, device=, model=standalone

But I am also getting this series of errors on the client:

2020-06-02T09:49:42.587 [ ERROR ] [MPVEngine] loading failed. 
2020-06-02T09:49:42.587 [ DEBUG ] [QHotkeyinput] Playback state is now 'Stopped' 
2020-06-02T09:49:42.587 [ WARN  ] [mpv] ffmpeg: https: HTTP error 400 Bad Request 
2020-06-02T09:49:42.587 [ ERROR ] [mpv] stream: Failed to open https://192-168-1-7.4c66a45db10f47bf8bed80003d7bb476.plex.direct:32400/video/:/transcode/universal/start?hasMDE=1&path=%2Flibrary%2Fmetadata%2F165632&mediaIndex=0&partIndex=0&protocol=http&fastSeek=1&directPlay=0&directStream=0&subtitleSize=100&audioBoost=100&location=lan&maxVideoBitrate=4000&directStreamAudio=0&session=xo5371hcf7mok6jj9nxcxbsz&offset=2&subtitles=auto&copyts=1&Accept-Language=en&X-Plex-Session-Identifier=kf9w9ji1fyzgsugrquzftkud&X-Plex-Chunked=1&X-Plex-Incomplete-Segments=1&X-Plex-Product=Plex%20for%20Windows&X-Plex-Version=1.11.0.1215-1d8c460c&X-Plex-Client-Identifier=e6cyjugdag5wr94b0ohatbsn&X-Plex-Platform=windows&X-Plex-Platform-Version=10.0.19041&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=standalone&X-Plex-Device-Name=HOME-HEAD&X-Plex-Device-Screen-Resolution=1427x949%2C2560x1440&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&X-Plex-Language=en&X-Plex-Client-Profile-Name=Plex%20Desktop. 
2020-06-02T09:49:42.587 [ DEBUG ] [mpv] cplayer: Opening failed or was aborted: https://192-168-1-7.4c66a45db10f47bf8bed80003d7bb476.plex.direct:32400/video/:/transcode/universal/start?hasMDE=1&path=%2Flibrary%2Fmetadata%2F165632&mediaIndex=0&partIndex=0&protocol=http&fastSeek=1&directPlay=0&directStream=0&subtitleSize=100&audioBoost=100&location=lan&maxVideoBitrate=4000&directStreamAudio=0&session=xo5371hcf7mok6jj9nxcxbsz&offset=2&subtitles=auto&copyts=1&Accept-Language=en&X-Plex-Session-Identifier=kf9w9ji1fyzgsugrquzftkud&X-Plex-Chunked=1&X-Plex-Incomplete-Segments=1&X-Plex-Product=Plex%20for%20Windows&X-Plex-Version=1.11.0.1215-1d8c460c&X-Plex-Client-Identifier=e6cyjugdag5wr94b0ohatbsn&X-Plex-Platform=windows&X-Plex-Platform-Version=10.0.19041&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=standalone&X-Plex-Device-Name=HOME-HEAD&X-Plex-Device-Screen-Resolution=1427x949%2C2560x1440&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&X-Plex-Language=en&X-Plex-Client-Profile-Name=Plex%20Desktop 
2020-06-02T09:49:42.588 [ DEBUG ] [mpv] cplayer: finished playback, loading failed (reason 4) 
2020-06-02T09:49:42.588 [ INFO  ] [mpv] cplayer:  
2020-06-02T09:49:42.588 [ DEBUG ] [MPVEngine] Property 'volume' set to '90' 
2020-06-02T09:49:42.588 [ DEBUG ] [mpv] cplayer: Set property: volume=90.000000 -> 1 
2020-06-02T09:49:42.588 [ WARN  ] [Web] [Player] A critical error occurred: 4294967283 An unknown error occurred (4294967283) 
2020-06-02T09:49:42.588 [ INFO  ] [Web] [Metrics] Updating session last interaction time

So I’m unclear on where the issue is ultimately stemming from.

7

Those are client errors.

  1. HTTP 400 is what it states. A request was made to PMS which wasn’t properly formatted and it was rejected.

  2. Volume seems to be set for 9000% (90 = 9000%) ? (1.00 = 100%)

8

Ok, progress.

So to that end, are there steps I can take to fix that on the client end? I’ve tried completely purging Plex for Windows and reinstalling, enabling fallback to insecure connections on local network, restarting my client, nothing seems to work.

The only change that comes to mind on the client side is that the Windows 2004 feature update installed, so could that be a/the cause?

9

I know nothing of Windows. I don’t even have a Windows VM. I am strictly Linux.

10

I currently have the same bug happening to me as well really annoying and it is also only happening on windows 10/7 clients. android works fine.
Server:
Ubuntu 20.04
CPU: 2x 2680v2
GPU: Nvidia Quadro P2200
RAM: 128 GIG ECC memory
I could DM the logs if neccesary

11

5 posts were split to a new topic: Client failure in VM server environment

12

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