Server Version#: Synology DS3018xs - DSM 6.2.3-25426 Update 2 - Plex version: 4.34.4
Player Version#: LG TV WebOS TV UN8100PTB
Hi All,
Just checking if something has changed in Plex, I’ll explain why?
For the last 3 years I have always used my LG tv to watch videos on my Synology by just selecting the INPUT button on the remote and selecting our PLEX MEDIA SERVER:NAS under STORAGE, so rather than using the PLEX app on the tv, I believe it just uses PLEX on the NAS, it’s always worked flawlessly, it only shows folder views similar to windows, it’s fantastic.
But recently it doesn’t work like that, either it says the file cannot be recognized or the it says the file has no audio.
But if I start the PLEX app on the tv, I can watch the videos no problem (Before you say just use the app, I find the menus to be slow and painful to get around).
Does anybody know if anything could have changed?
BTW, I have two different LG tv’s and it’s the same on both.
I suppose what you say is you’re using the DLNA part of your Plex Media Server – not the respective “native” Plex client?!
Some year(s) ago, Plex started disabling that by default. It’ll also be disabled if you enable a “Plex Home” with managed users (allowing for fast user switching with Pins) – this was mostly to avoid locking stuff for your kids in the Plex app but keeping it all accessible via DLNA as there’s no user management with that.
You should be able to enable the DLNA server via Plex Web: Settings > [Server Name] > DLNA > Enable the DLNA server
Does that issue persist when you restart the DLNA component (disable, wait a moment, re-enable), restart the Plex Media Server or the underlying machine?
Do you have the same issue when you try to access Plex through another DLNA client (e.g. VLC)?
The issue does persist after restarting the DLNA server, I have to restart the DLNA server ever 3-5 days (uncheck, apply, wait a bit, recheck, apply), because the memory usage skyrockets on my Synology, it took me awhile to figure out it was the DLNA server causing the memory issues, it must have a memory leak, it’s been doing it for at least 1 year.