Server Version#:1.42.1.10060 - truenas/freebsd
Player Version#:4.147.1 webapp
Good day all, I’m new to the forum and couldn’t find anyone else with the issue I’m currently experiencing exactly,
Have been able to view my content on my Plex server via an internal host name DNS override on my router up until now without any issue.
However today after performing an update on my server I am unable to view my content via the domain name, as it always thinks I’m remote accessing the server and forces me to pay for the remote view subscription to watch the content, but my app on my phone and tv are still connecting without issue, and if I enter the IP address manually in a browser it works fine.
I am on a single network IP range, proof of this as above is IP only access works, and the only thing that changed is the update between working and not working.
However that makes my life harder for my family that don’t understand the ip address and “scares them” because they think its “hacker” stuff. Its basically a preference thing,
I understand that and as stated in my post, that does work - but the dns hostname used to work pre update and I prefer that.
Based on the name and descriptions in that post I take it as its a new “forced feature” that I’ve updated into and its now how plex works going forward and not a bug?
I’m using Let’s Encrypt to create my p12 cert on my router and upload it to all my services that needs it automatically
Have been using it like that for more than a year, long after version 32 as mentioned in the post.
I also tried it without a certified fqdn and host name that doesn’t have a cert and it would open via http instead of https, and behave exactly the same
I can access my web app with the host name and browse all my content but can not watch anything, as soon as I play content it pops up stating I have to pay for remote play
And if I open the settings it shows the server as “remote” not “nearby”. If I open the IP web app it shows “nearby”
And it’s important I note the issue exists on all devices web browsers that I’ve tested not just my pc
I have not opened the port for the plex and have not configured any remote settings on the server as the server is only used locally
I hope the above helps towards helping solve my problem.
How can I test you are correct, and can this be “fixed”, if so, could you direct me to some guide to do so.
My apologies my knowledge is somwhat limited and I don’t even know what to look up to begin resolving this.
If I ping my plex server via the fqdn I get it’s local ip as a result. Even on my browser if I inspect the page elements and look at network traffic it shows my plex local ip if I’m on my fqdn for plex
So the *.ch name is what has my p12 cert with https
The *.net name is the one I made to use private testing with http
I have tried toggling remote settings on and off in an attempt to see if some setting was misbehaving but I’ve left the remote settings disabled, I never used the remote feature and never plan to
Could you elaborate what ‘published’ means in this context?
Both dns fqdn is “defined” in my router to point to my server local ip address, if that is what you mean, if not please explain what you meant.
My apps on phone and TV detect and connect and play from my server no issues.
Only my web interface is giving me problems on the fqdn, where I can connect to server and browse my libraries but as soon as I press play the pop up for remote play stops me. This does not happen direct on ip.
When you create your server, it is private to you (your home) by default.
If you wish to share it with family or friends,
– Enable Remote Access
– Invite the person/people to access your server
– After they accept the invitation, they see your server in their apps.
What happens at Plex.tv
When you start your server, PMS sends the local IP & hostname information to Plex.tv
When you enable Remote Access,
– Opens the UPNP port (if set to do so)
– Sends your WAN IP and PMS UPNP port number to Plex.tv (This is “Publishing”. It’s the information your shared family/friends’ apps need to connect to your server.)
– Plex.tv adds your WAN UP and port number to your server info.
It then marks the server as “Published” ( shareable with others )
When you turn off Remote Access, Plex.tv will remove the WAN IP & port number information from the server. It becomes Private again.
When you use a FQDN with the web app, it will, By Default, expect the server to be Published and have its certificate registered with Plex.tv
Not being published is probably where you’re getting hung at.
With the apps, are you using LAN IP or automatic server discovery?
Unfortunately I don’t see where the problem is or how to resolve it from what you have explained. I might just not be smart enough
It sounds to me like you are either saying I need to turn on remote access to get the plex to behave correctly or that web app now views fqdn as a remote connection regardless if it is local.
And with the other apps, it’s been a while, but I think I used auto discovery and they worked just fine.
My apologies for not knowing what to do with information supplied
I’ve plex hosted in Kubernetes and if accessing it via FQDN (though traefik) it is behaving as described. Can browse media but not play it without pass.
Accessing it through a Nodeport via IP works fine. It seems a very strange decision to treat users coming via FQDN as remote users by default.
Setting https or http resolves to the same issue, if that’s what you are asking. Sorry I’m trying to keep up but I don’t understand everything that well.
My apologies, I looked at the log, and I get the same header host issue treating as non local, however the fqdn it’s not “recognizing” is in the fields that you fill in and that is in the cert.
And I have the same configuration with Opnsense router where I have the A table overide internally on my dns for the fqdn. Have multiple other things I host on a proxmox server and plex is the only thing giving me this “issue”
If there is anything else in the logs or settings I can provide to aide please let me know
