Server Version#:1.29.0.6244-7000
Player Version#:4.87.2
Running my Synology DS918+ NAS with the PlexMediaServer-1.26.1.5798-99a4a6ac9-x86_64_DSM7 initially without any issues at all, September 13 2022 the server disappeared from all sorts of visibilities externally and internally. The whole media Library is still intact and in order (playable when directly accessed).
After a brief check I decided to clean out the server completely and I uninstalled it all with the “Erase all PMS” option.
I restarted the NAS and started a clean installation of the PlexMediaServer-1.28.2.6151-914ddd2b3-x86_64_DSM7, which went through the whole process completely only showing my friends shared media lib´s. I never got any “Configure new Server” option at all which surprised me. I made some more checks and checked the log-files for errors. Seems it´s complaining about missing plugin´s, but that should not prevent it from unable to run.
So tonight I decided to give it another stab. No luck tonight either.
Uninstalled wholly the 1.28 version and tried a clean install of PlexMediaServer-1.29.0.6244-819d3678c-x86_64_DSM7
Same thing again.
Need some help guys. What is wrong with the installation here? I´ve tried to remove the installation folder “PlexMediaServer”, created a new one later with same name. Checked the access rights for the “PlexMediaServer” internal service
R/W rights as well.
Then I installed the Windows version on my PC and that worked like a charm straight out of the box. But that´s not where I want the server to run!
Is there some reason you have a public IP address assigned to the NAS?
Net 135.17 is assigned to Genesys Telecom Labs in California.
If the NAS is on your local network, you need to change your addressing to be RFC-1918 compliant. Use private addresses: 10.x.x.x; 172.16.x.x - 172.31.x.x; 192.168.x.x.
NetRange: 135.17.0.0 - 135.17.255.255
CIDR: 135.17.0.0/16
NetName: GENESYS-135-17-0-0-SLASH-16
NetHandle: NET-135-17-0-0-1
Parent: NET135 (NET-135-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Genesys Telecommunications Laboratories,Inc. (GTL-21)
RegDate: 1996-04-30
Updated: 2021-12-14
Comment: Genesys Telecommunications Laboratories, Inc.
Ref: https://rdap.arin.net/registry/ip/135.17.0.0
OrgName: Genesys Telecommunications Laboratories,Inc.
OrgId: GTL-21
Address: 2001 Junipero Serra Blvd
City: Daly City
StateProv: CA
PostalCode: 94014
Country: US
RegDate: 1999-10-20
Updated: 2008-04-16
Comment: GTL-21 GTL-6 GENESY GENESY-1 GENESY-5 GENESY-7 GENESY-21
Comment: Old address. 1155 Market Street San Francisco CA 94103
Ref: https://rdap.arin.net/registry/entity/GTL-21
Great notice there.
I´ve been using this range for many years now, without any problems as a local network. As you state it´s outside RFC-1918 compliance range.
Has there been any recent changes in this area for Plex? I´ve been running it with this IP address range for many years and versions.
As for RFC-1918, it’s always been a requirement when Remote Access is required or when you use https://app.plex.tv
What breaks here is the plex.direct certificate for your LAN which is how your apps communicate with your server. Firmware updates to ISP modem/routers will also soon start to fail as those devices offer more services.
If everything were purely by no-auth-required IP addresses, you’d be ok.
While you’ve been OK for a long time, it’s unfortunately caught up and now does require making it compliant.
If everything on your home LAN has a DHCP-assigned address
Shutdown your equipment while you have control
Change the LAN’s base address in the modem-router
Restart it if required.
Restart your devices.
IF you have static IP addresses, change them one-by-one to their new addresses first and then switch the LAN (modem/router).
