Server Version#: 1.15.4.994-107756f7e Synology package
Player Version#: any
After the latest “improvement” for permissions, I’ve had a hell of a time with my server. Today I said screw it and just tried to start fresh. I followed the support article - I removed the package, the plex shared folder, removed plex user from /etc. Removed the /home directory for the plex user
I reinstalled, and no matter what I do I can’t get the server setup wizard to start. I saw other posts saying I could go to this url- http://<nas ip:32400/manage/index.html#!/setup and that simply says “you don’t have any media servers yet” download and install.
Still getting the same problem when running a fresh docker install on the same server. That means it’s a problem on the plex.tv account side, which I can’t do anything about.
I concur with you on this abrupt update.
My better half cannot access her photos either, it really is a downer when forced to
“manually set file permissions using SSH” , that is if you can even process through the instructions with no real outside support.
Here we sit with a quagmire of Synology FAQ guides to wade through, might as well use Synology DS apps to access your media.
I feel your mental anguish…
Tried running the script. Not able to login. I tried email address and username as login. Running while ssh’ed into my nas. Verified that curl was able to reach https://plex.tv/api/claim/ from the command line. I added echos to the script to verify that I entered my password correctly. IP address set to 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
Latest on github. It’s precisely what is linked to in the the FAQ.
Doesn’t matter if it’s docker or not, there’s a bug in the script. URL’s can’t contain certain characters, and if those characters are in your username or password, the claim script claims you can’t login.
With my fix to the script, I was able to claim the server. Seems like it’s working. Indexing seems to be having issues though. will report back after it gets as far as it can.
The original bork - files stopped getting indexed. So I changed permissions and did everything in the sticky post. Worked for a day then I got a could not connect error. I repaired the database.
It worked for a bit, then got another general error saying I couldn’t connect. So I said screw it, and wanted to start clean WITH THE SYNOLOGY PACKAGE. That didn’t do to the fact you guys have this arbitrary bash script floating in the ether that thankfully you pointed to. However, it’s insane that an uninstall and reinstall makes the server unusable. No other software does this.
So, I went to docker. That’s it. Now the package permissions issues can’t cause an error and screw with my Synology users.
So once again, this was all originally because of errors after the upgrade OF THE SYNOLOGY PACKAGE. (This was a 2 year old stable synology package server before this.)
That’s what I was referring to. I went through all the steps. It’s like you’re reading everything but the most important sentence in everything I post.
