Running Plex on a Synology DS218+. Plex was acting up and so I uninstalled it and erased the related files. Reinstalled it with version 1.29.2.6364-7000, and appropriate permissions, and now I get “Not authorized You do not have access to this server.” (I also got the same results with the more-current 1.40… build).
I’ve tried modifying the Preferences.xml file, but it doesn’t even include the relevant info (e.g., user email or token) that seems to cause similar problems (see below for text). I even tried using an older preferences file but that merely allowed me to “connect” with my Plex account but not my actual server and files.
This problem is driving me bananas. At this point, I just want to do a clean reinstall and start a new server with my existing files. Really hoping someone has some good advice.
MODERATOR EDIT: Preferences info removed
@ChuckPa, thanks for the response. That’s one of the other things that I tried, a few times. Tried it again and I got:
“Failed to install the package. ERROR: Could not complete dialog with Plex.tv. Unable to claim. Either installation time was too long or difficulties with Plex.tv exist. Please try again or seek assistance in our support forum.”
Ah ha! The Syno can’t talk to Plex.tv/the internet but your computer can.
Go to Control Panel - Network
Confirm the network settings point to your modem/router IP address correctly.
If you make changes, restart the Syno
@bhaggart
If you have more than one Ethernet connection to the NAS, then open DSM Control Panel > Network > Network Interface > Create > Create Bond and bond the connections.
This will effectively, give you a single connection/IP Address to the NAS and that will allow Plex to communicate correctly with the internet and other devices on your LAN.
This is getting a bit out of my technical comfort zone, but I’m looking at my router’s list of clients and I see my Synology server there, and I don’t think it’s changed over the past few days. Maybe I’m looking at the wrong thing? Or I’m not sure how to tell if it’s pointing correctly to the modem/IP address (they differ only on the last number…). It’s wired directly to my router, FWIW.
@bhaggart
Don’t overthink it
-
Control Panel - Network - (now look at the network adapters)
-
They should be “automatic” like this -
- Or manually set like this -
I suspect you are using the manual (static) method?
Does it point to the correct IP address (your modem/router) ?
I’m definitely using the automatic method, and it’s connected, as far as I can tell…
Using FileStation,
Navigate to PlexMediaServer/AppData/Plex Media Server
Right-click “Logs” → “Compress to Logs.zip”
Download that zip then attach it here.
We’ll see what’s happening
Here’s hoping there’s something in here, and not just me running through the server’s guts like a bull in a china shop! Thanks…
Logs.zip (153.5 KB)
@bhaggart
You’ve got a few things going on here.
- You have QuickConnect enabled. That QuickConnect connection link you’re trying to use is wreaking havoc. It’s tryng to inject itself between you and plex.tv
Apr 19, 2024 13:55:19.087 [0x7f2ca8213b38] WARN - [HttpClient/HCl#4] HTTP error requesting GET https://plex.tv/api/photos/profile (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name ‘plex.tv’)
-
You have IPv6 enabled but your LAN is IPv4 only (?)
– If true, we can turn off IPv6 and make life easier
-
Do you have your own Domain you’ve assigned here anywhere ?
Summary: It’s refusing to connect because of the Domain (SSL) mismatches.
I’ve turned off IPv6 and disabled QuickConnect. I’m assuming there’s another step I have to do, but I tried connecting to Plex anyway w/o success. Re my own Domain, I don’t think so, unless you mean the ones related to QuickConnect (under Certificate? Like I said, I’m a bit out of my depth here.).
turn off quick connect too
open the syno in your browser by its LAN IP
Some progress, I think. Thanks for the help. I’ve turned off quickconnect and opened synology w/ its lan ip. Wasn’t able to install plex using the claim token approach, but a normal install is sort of allowing plex to talk with my server. I can access my content, but now I’ve got a warning that the server is not claimed and not secure. And when I try to claim it by pressing the claim server button, nothing happens. It also keeps asking for an update that I need to install manually, even after I’ve already done that.Also under remote access, it says It’s not available outside my network, and asks me to sign in to access my server from anywhere (I’m already signed in).
@bhaggart
With you now getting some activity and claim requests, Please download and attach a fresh set of logs.
There’s something going on with your networking.
Hopefully a fresh set of logs will tell us more
Here they are…
Logs.zip (2.3 MB)
@bhaggart
The logs you gave me still show a certificate problem.
Question: Is your Synology time / clock correct and properly sync’d to internet time ? (pool.ntp.org)
Apr 19, 2024 14:02:57.548 [0x7f3cc506ab38] INFO - Plex Media Server v1.29.2.6364-6d72b0cf6 - Synology DS218+ x86_64 - build: linux-x86_64 synology-dsm7 - GMT -05:00
Apr 19, 2024 14:02:57.548 [0x7f3cc506ab38] INFO - Linux version: DSM 7.1.1.42962-6, language: en-US
Apr 19, 2024 14:02:57.548 [0x7f3cc506ab38] INFO - Processor: 2-core Intel(R) Celeron(R) CPU J3355 @ 2.00GHz
Apr 19, 2024 14:02:57.548 [0x7f3cc506ab38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Look at the time. 2pm??
I checked the time and it was off by one hour (wrong time zone). Not sure how to solve a certificate problem. The only certificates I have under Security-Certificate is the default Synology certificate and the QuickConnect one, which doesn’t look like I can delete…
Once you put it in the correct time zone, and sync’d the time to NTP, did you restart and did it then work?
(time skewed badly will show as SSL certificate errors too)
Regarding Quick Connect – you just turn it off / disconnect.
Leave their certificate in there and unused.
What’s happening is instead of keeping your traffic 100% on your LAN,
you’re routing it all the way out to Synology and back instead of staying completely local.
It didn’t, unfortunately. It still won’t let me claim the server. It’s still where I can trigger the setup screen and add my content, but the problems re claiming the server, asking for me to sign in when I’m already signed in, and asking to update manually when it’s already been updated are still there. As is the inability to use a token to claim the server when installing.
