I have a problem with Plex Media Player. When playing any media I get the following error: ‘Abspielen von “abc” nicht erfolgreich’ which is probably “Playback of “abc” failed” in english. This error happens with all videos and all music and on all windows pc in my lan.
Some basic information (see more at bottom):
Plex Media Server: plexinc/pms-docker:latest (1.13.0.5023-31d3c0c65) @ Debian Stretch
Plex Media Player for Windows: I tried latest (2.11.0.867-f27f8d2a), previous, and some very old versions @ Windows 7 x64
using the windows phone app (thank you so much for supporting this great OS!!!)
with plex Media Player after setting “secure connections” for the server from “prefered” to “disabled”.
Because of this results I guess the error is related to the secure connection or my network configuration. I’m not sure if with b) the error “bad cert domain” should occur or if it should just work.
I habe a attached a excerpt from the player’s logfile. The interesting part is probably “ffmpeg: tls: Unable to decrypt message (error 0x80090330)”. After that the playback attempt is aborted.
Of course it would be a workaround to either disable secure connections or use a browser, but I don’t want that for security and comfort reasons. Please help and point me in the direction.
Some more background:
I have a small home network with a router (fritzbox @ 192.168.1.1), Openmediavault (on linux) with some Docker services (plex @ 192.168.1.5, pihole @ 192.168.1.2, vpn and backup services) and a few Win7 computers. DHCP is running on the router and announcing 192.168.1.1 as gateway and pihole @ 192.168.1.2 as DNS. Pihole is forwarding external dns-requests to the router.
DNS lookups are fine on the computer running plex media player as well as within the plex docker container. Nslookup to 192-168-1-5.**********.plex.direct returns whatever IP I fill in. Nslookup to plex.tv is fine, too.
I also tried enabling external access to plex (including port-forwarding in the router) and disabling GDM. I have added 192.168.1.0/24 to the “no authentification needed” list. I tried disabling direct stream and direct playback in the plex media player, all without success.
edit: now, that I’m promoted to level 2 I could improve some mistakes…
I have done some more research: https://plex.tv/api/resources?includeHttps=1&X-Plex-Token=******* contains my plex server with the correct public address and a single entry: <Connection protocol="https" address="192.168.1.5" port="32400" uri="https://192-168-1-5.********.plex.direct:32400" local="1"/>
Opening that uri address with firefox works (without a security exception for the certificate) and nslookup is fine, too. (I already had added plex.direct to DNS-rebind exeption in my router). But the plex media player is still not playing anything. The log file shows: [Connections] Active connection to plex--hive is https://192-168-1-5.*******.plex.direct:32400 ... PlayerComponent.cpp @ 589 - cplayer: Playing: https://192.168.1.5:32400/library/parts/8020/1513703684/file.mkv?...
When I open the latter address with firefox I need a security exception. I think the media player runs into the same issue…?
In Windows 7, support for TLS 1.1 and TSL 1.2 was added with a patch. However, these newer versions are disabled by default. This is changed by adding the following registry keys. After that, the secure connection works without any problems!
I am surprised, however, that the problem is not more well-known? I had it on all Windows 7 PCs and I’m sure I didn’t make any odd settings in this respect. Maybe on one PC, but not systematically on all… o:)
Yes, I have installed both as well as all security updates. Maybe some rare combination of software, settings or update history can lead to disabled tls 1.1.
If TLS 1.1 should be enabled on a up-to-date Win7 under normal conditions, this would explain why only few people have this issue.
Yes but PMS requires Windows 7 SP1 and not Windows 7 as minimum supported version. The linked page refers to Windows 7 and not with SP1. For windows server 2008 they do mention Service Pack
Sorry for resurrecting an old thread, but I wanted to offer another way for people still looking for a fix. If you aren’t comfortable with windows registry, microsoft has as program you can download to do it for you.
