Cannot access it anymore

server-freebsd

#1

Hi,
I"m running the server version 1.7.5.4035 on FreeNAS. The server has security disabled. When I try to access the web interface via dns name, like plex:32400/web/index.html, I'm presented with no server and the Plex Pass advertising, even when I'm logged in.
And the "Looking for servers..." is displayed on the upper-left side.

When I access the interface via IP, everything is fine, I can see the interface, settings and all.
One strange thing is that I get a message "An unclaimed media server has been found on your network. Claim it now".
The dns mapping is correct.

Any ideas how to fix this?

Daniel


#2

The pref to disable security has been removed and its functionality obliterated. It was abused too often leaving many users with their server fully exposed on the internet without their knowledge.

If you were relying on this method to access your server, you will need to change to using the IP whitelisting.


#3

Mmm, nope.
I set the in Network/List of IP addresses and networks that are allowed without auth to the IP/net mask for my network. No use.
Anyway, I was talking about accessing via name instead of ip. If this "security" you are talking about would be enforced, I wouldn't be able to access the server at all.
And why is it making GET requests to http://127.0.0.1:32400/?X-Plex-Product=Plex? The Plex server is not installed on the same computer as the browser.
And the request to http://plex:32400/?X-Plex-Product=Plex is getting a 401 (Unauthorized).


#4

Did you recently update to 1.7.5? Saw another discussion on forum where user had two different installs of Plex on same NAS.


#5

No one can even begin to answer your specific questions when the context is lacking. First, you need to post logs: https://support.plex.tv/hc/en-us/articles/201643703-Reporting-issues-with-Plex-Media-Server

Second, you need to provide specific information on your network setup. For example, you mention a DNS name and IP but you fail to mention what any of the IPs are nor how you are mapping an obviously non-public name to IP.


#6

Right, sorry. I thought it's pretty obvious.
The server is installed on the FreeNAS - just one instance/version.
I'm trying to use the bwoser to connect to that server, to manage it.
By using the private IP on my internal network, I can access the server via browser.
When using the http://plex.home dns name associated with that private IP, I get the aforementioned error.
When I ping the plex.home, I get a reply from the IP, so the nework is working fine.

What irks me is that, before version 1.7.5.4035, it used to work.

And how can I download the logs when I can't connect to the server?


#7

@bdaniel7 said:
Right, sorry. I thought it's pretty obvious.
The server is installed on the FreeNAS - just one instance/version.
I'm trying to use the bwoser to connect to that server, to manage it.
By using the private IP on my internal network, I can access the server via browser.
When using the http://plex.home dns name associated with that private IP, I get the aforementioned error.
When I ping the plex.home, I get a reply from the IP, so the nework is working fine.

What irks me is that, before version 1.7.5.4035, it used to work.

And how can I download the logs when I can't connect to the server?

I can see attempts to access via domain name plex and getting rejected as unauthorized

Security was tightened about 12 months and host names are no longer allowed without authentication.
Some discussion you can find in this forum topic http://forums.plex.tv/discussion/229843/local-server-requests-sign-in-when-accessed-via-hostname-but-not-via-ip-address/p1

For the server logs you should be able to get to the directory
See https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
https://support.plex.tv/hc/en-us/articles/202915258