Server Version#: 1.29.2.6364-7000
Player Version#: 1.56.2.3345-2a4c0924
Weird problem and unsure of how to remedy: After updating to the latest Beta Server was provided a warning that the server was in relay mode. I inspected the information on the connections page and did not notice anything that would force it to be in relay mode per se, other than the bandwidth limitation was not set. I updated that information and the server appears to have spontaneously disappeared from my account. I can not see any options for settings or claim the server as described in the FAQs.
When inspecting the authorized devices list I see the server listed. When inspecting the package on the package center I see it as running. I can even go to the web interface. Unfortunately, I still don’t have any of the associated server settings available to me–So pulling logs via the normal method is impossible.
I have tried stopping the package and turning it back on. I have logged out of both the web interface and the app and logged back in, but the setting do not show. I even hunted for a crash report by chance in the appropriate location with no success.
From a system on the same network as the NAS, use an incognito/private browser window pointed directly at the IP address of the NAS: http://syno_ip_address:32400/web.
For example, if the IP address of the NAS is 10.11.12.13, you would point a browser window at http://10.11.12.13:32400/web.
Can you login and see the server settings?
You may see a message similar to “this is not hosted at plex.tv…” That is OK. It just means you’re pulling the login page from your local server, not app.plex.tv.
If the above does not work…
Uninstall Plex Media Server.
Choose the Uninstall Only option.
This removes Plex Media Server application.
It does not remove the Plex Data Folder or your media.
Reinstall the same PMS version you just uninstalled.
Choose the Plex Claim Token option.
Click on Get Plex Claim Token to generate a token.
Copy it to the clipboard, then paste it into the Claim Token Field.
Finish the installation.
If successful, you will see a “Server successfully claimed by <userid>” message.
Login to the server using the IP address: http://syno_ip_address:32400/web
The server should be claimed and you should be able to reach the server settings.
Once claimed and accessed directly, you can access it via app.plex.tv, any app, etc.
This is the only thing I can see in the log files. Everything else looks normal.
Nov 06, 2022 13:14:09.247 [0x7f9327883b38] DEBUG - [HCl#2e] HTTP requesting GET https://192-168-1-147.00c33eab261144e98dcc36421a413dae.plex.direct:32400
Nov 06, 2022 13:14:12.253 [0x7f932b35cb38] WARN - [HttpClient/HCl#2e] HTTP error requesting GET https://192-168-1-147.00c33eab261144e98dcc36421a413dae.plex.direct:32400 (7, Couldn't connect to server) (Failed to connect to 192-168-1-147.00c33eab261144e98dcc36421a413dae.plex.direct port 32400: Host is unreachable)
It looks like you are running into DNS Rebinding protection, which is blocking the plex.direct domain.
Are you running a PiHole, pfSense firewall, etc? Your ISP router could be blocking things as well.
I’m not 100% the DNS rebinding makes a lot of sense for the sudden behavior change–but may be it does. Wouldn’t the local interface negate the need for a reference to the DNS? I can not adjust the DNS at the router level, unfortunately–and the adjustment to use the public DNS doesn’t appear to have an impact on the NAS level.
Is there a way to set the server back to relay mode as that seemed to function properly prior to this? This would pose a limitation on bit-rate–but I’d rather have it functional than not.
Success: I had to go into the Preferences.xml and change the setting for:
PublishServerOnPlexOnlineKey=“0” to PublishServerOnPlexOnlineKey=“1”
I now have access to the server settings on the web app and on the windows app. I did not knowingly set this option to false, but setting it to true appears to remedy my issue. Is this going to cause any security concerns?
From a comment that has since been removed: There are no security concerns with adjusting or setting this Boolean to true.
I think there might be a bug here that may need inspection:
To duplicate the issue–
from the Windows Client go to Remote Access.
In my case, the manually specify public port is required to be “fully accessible outside your network”.
Clicking the checkmark will change the boolean of PublishServerOnPlexOnlineKey from “1” to “0”, at which point it will require manipulation of the .xml file to get the server information back.
Have not adjusted any settings between instances. I am now showing the Plex for Windows client as indirect. Previous instances of the server would show direct (either via “nearby” or “remote”). I have made another thread concerning this particular issue however.
