Plex running on Synology, but suddenly can't access

[lbutlr]

Server Version#: 1.16.0.1226-7eb2c8f6f - Synology DS1815+ x86_64 - build: linux-x86_64 synology
Linux version: DSM 6.2.2.24922-0, language: en-US
Processor Intel® Atom™ CPU C2538 @ 2.40GH (DS1815+)
Player Version#:

At some point in the last few weeks the Plex server running on my Synology has become unreachable. When I was told about this I went and made sure the permission changes for 1.15 had been made and restarted the server. Still unreachable. Sort of.

I can connect to :32400/web/ and I get the login screen. I get the user selection. It loads up the other Plex server attached to my account, but the one on the Synology shows unreachable. The one I am currently connected to.

On the Synology, the ‘Plex’ user has r/w access to the shared folder Media and the shared folder Plex.

If rebooted the Synology and the Plex app via the Package Center AND via the command line.

looking in the PMS log file, I see that it selects the right interface, gets the right IP,

One it is 'up" I see lines like this in the log file:

Jun 26, 2019 09:56:54.409 [0x7f7cc7159700] DEBUG - Request: [127.0.0.1:35035 (Loopback)] PUT /myplex/refreshReachability (4 live) Token () Jun 26, 2019 09:56:54.410 [0x7f7cf6614700] DEBUG - Completed: [127.0.0.1:35035] 200 PUT /myplex/refreshReachability (4 live) 0ms 195 bytes (pipelined: 1) Jun 26, 2019 09:56:54.413 [0x7f7cc7159700] DEBUG - Request: [127.0.0.1:35036 (Loopback)] GET /myplex/account (4 live) Token () Jun 26, 2019 09:56:54.413 [0x7f7cf6614700] DEBUG - Completed: [127.0.0.1:35036] 200 GET /myplex/account (4 live) 0ms 1133 bytes (pipelined: 1)

processes running are:

plex 29195 0.2 1.2 1981792 49176 ? Sl 09:50 0:02 /var/packages/Plex Media Server/target/Plex Media Server plex 29344 1.1 1.1 1808332 45824 ? SNl 09:50 0:08 Plex Plug-in [com.plexapp.system] /volume1/@appstore/Plex Media Server/Resources/Plug-ins-7eb2c8f6f/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.16.0.1226-7eb2c8f6f /volume1/@appstore/Plex Media Server/Resources/Plug-ins-7eb2c8f6f/System.bundle plex 29864 0.0 0.3 1337024 13108 ? Sl 09:50 0:00 /volume1/@appstore/Plex Media Server/Plex DLNA Server plex 29868 0.0 0.2 463684 8760 ? Sl 09:50 0:00 /volume1/@appstore/Plex Media Server/Plex Tuner Service /volume1/@appstore/Plex Media Server/Resources/Tuner/Private /volume1/@appstore/Plex Media Server/Resources/Tuner/Shared 1.16.0.1226-7eb2c8f6f 32600 /waitmutex plex 29904 0.6 1.0 910544 41432 ? Sl 09:50 0:04 Plex Plug-in [com.plexapp.agents.imdb] /volume1/@appstore/Plex Media Server/Resources/Plug-ins-7eb2c8f6f/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.16.0.1226-7eb2c8f6f /volume1/@appstore/Plex Media Server/Resources/Plug-ins-7eb2c8f6f/PlexMovie.bundle

I’m stumped.

[lbutlr]

Thanks, the sript claims it cannot authenticate with Plex using the email and password out of 1Password that I use to authenticate with Plex (copy and pasted, not typoed).

I assume that it is not excepting my plus-address email name properly, but I haven’t looked at the script code yet.

`plex.tv Username: lbutlr+plex@fake.example.com

plex.tv Password:
plex.tv Password Repeated:
IP Address of PMS server: 127.0.0.1
Comparing entered passwords
Comparing entered passwords ok
Validating IP address
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
******** ERROR ********
We failed to authenticate towards plex.tv
Please check username and password, as well as network access

$ sudo ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=2.57 ms`

[lbutlr]

Ah, yes, the script build the URL by simply plugging in the user name and password without escaping any special characters, so that crept will fail for anyone with, for example, [ & + in the username or password fields. I am not familiar enough with sh to know hot to properly encode the server and passvar fields before tasing them too curl.

I finally managed to rebuild the final request to claim the server but ripping apart the script and forcing ti to process manually percent-encoded username and password. Thank you for the script, I’ll leave a not on GitHub about the encoding issue.

[lbutlr]

No problem, there is already an issue open there and that person posted a fix, so that’ll learn me to check the bugs/issues first time around!

Well, no it probably won’t, but in theory!