Plex: Anything Needed for Non-Remote Use?
-
I'm using Plex solely for local viewing across my lan. I've seen various posts about what we need to do with pfSense for remote viewing from external networks. But, I'm wondering if I need to do anything at all to pfSense for Plex to work locally.
The reason I'm asking is I've just done a clean install on new hardware, don't recall ever doing anything special for Plex, and am now getting certificate errors with my NAS and television with the Plex app. There are plenty of recent reports where others have had these issues and they're either a problem at the Plex or the Let's Encrypt (their certificate issuer) end. I don't see anything bad happening in my logs, but I thought I'd double-check here.
-
@areckethennu really only thing you need to do is in unbound.
server: private-domain: "plex.direct"
This is put in the option box in unbound.
But cert errors more a device issue then anything else, some TVs etc. do not trust the new CA the plex being signed with.
Check out here
https://support.plex.tv/articles/204080173-which-smart-tv-models-are-supported/Note: Due to root certificate limitations with the device OS itself, only webOS 5.0+ devices support secure connections with a personal Plex Media Server. To allow connections to a personal server, devices running earlier webOS versions must be set to Allow Insecure Connections in the TV app settings and the Plex Media Server must be set to Preferred for the Secure Connections preference.
The whole certs thing has a been a sore spot for many users.. When their device hasn't been updated, etc..
The rebind stuff, what my above server: plex direct thing is talked about here
https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/ -
@johnpoz Thanks, again! It was the Custom Option thing at the bottom of Services > DNS Resolver > General Settings. I'd forgotten all about that.