Server Version#: DSM 6.2.2-24922 Update 2
Player Version#: 1.16.4.1469-6d5612c2f
Hi there,
Last night my Plex began to list itself as unable to connect securely by both myself and 2 friends. This morning I attempted to follow this guide to solve it, which had me look for the “preferred” option of secure connections.
I think that the UI has been updated since that guide was made because the layout is entirely different now. Unable to do that, I attempted to follow a different guide to refresh the permissions. I got as far as attempting step #5, but because I’m on a remote connection I don’t think I was able to connect to the specific address. I attempted to simply log in via app.plex.tv and now its telling me that my server “is unreachable. Make sure it’s running, double check your network, and try again.”
In the process of doing this I’ve restarted the Synology NAS, stopped the process within the package center and restarted it, and signed out and in again.
Does anyone know what’s going on and how I can fix this?
Given this occurred last night, Recreating by restarting PMS (DEBUG logging on, VERBOSE off)
then recreate what you see will tell me more about what’s happening.
Most likely, the logs will show as it starts.
If noticed, Trumpy instructed to access locally via the LAN IP address instead of app.plex.tv
This is the best way to get control of it again.
my friend can technically access all my media, but gets a little yellow warning (exlamation mark in a yellow circle) next to each of the libraries for the server.
I can technically access the server from app.plex.tv, though the results are bizzarely inconsistent. I’ve tried to refresh the web player a bunch and the behavior seems to follow a pattern: the server says that it’s unavailable (can’t connect securely), but sometimes, not always, it suddenly corrects itself and shows me all my media without issue
I dont know if this makes this more or less complicated, but accessing from my iPhone app seems to result in zero issues. I can stream things and there’s no problem. Does this help?
This is why it works when on your LAN but not when remote.
You also state it’s not remotely accessible which further tells me it is switching to local mode.
Please do clarify, in event I have misunderstood above, what you mean by technically access the server ? Is it accessible in the manner I stated above?
Have you attempted to open the server directly on your lan by using it’s IP address ?
What I mean is that to the best of my knowledge, I believe she’s been able to watch things. So technically, using her account (I’ve enabled her access as a friend), she can reach things on my server but it’s alerting her that the connection isn’t secure.
Your explanation is helping me understand this, I think. It sounds like I don’t have any issue accessing the server from my LAN, but when I attempt over a remote network the server can’t establish a secure connection. I haven’t attempted to open the server over my LAN via it’s IP (I’m currently at work, I can’t reach it right now), but would that entail the process that Trumpy was talking about?
Also, as far as I can make sense of this, while it is technically “remotely accessible” (sorry if I’m retracting things I said earlier), it’s giving me all sorts of warnings that it’s not available/secure. And yet I’m able to stream things? I’m getting a notice that it’s “indirect”…
Indirect is when the playback outside your home must be sent through plex.tv.
Normal operation is to connect direct to your server and have full quality.
It seems we’ve answered the bulk of that and now which remains is to determine why you don’t have Remote Acccess (Direct) capability.
Do you need assistance with testing and diagnosing this?
What was the last known state of it ? Remote should be working or not working?
I would love some help diagnosing this, thank you.
By remote woking/not working, I assume you mean Remote Access (Direct) should be working properly, yes? I have occasionally had issue with this way in the past (last time I remember is probably almost a year ago), but up until the last 24 hours it was working fine. I access the server through app.plex.tv maybe even daily, so in the past the indirect alert hadn’t been happening.
Is this what you mean? or does “last known state of it” refer to something else?
It’s a modem/router combo, and as far as I know it hasn’t received any updates.
I manually updated DSM this morning thinking it would fix something. It updated node.js v8, synology drive server, and synology application service.
At first it may seem like the obvious issue was with the Drive Server, but I’m not so sure about that. Unless you know that by default Plex works with it? I don’t actually use that application (I don’t think), though it does seem to have some info in the console that could be related to indexing some plex stuff.
Something odd that happened recently however is that it looks like in the log it’s turned off and on 10 times in the past day. It says its operating correctly right now…
I think it’s more likely an issue between the node.js v8 and the Synology Application Service, as there’s a series of recursive-looking alerts:
Please install the following package(s) before installing this package: SynologyApplicationService 2019-08-01 11:29
Please install the following package(s) before installing this package: Node.js_v8 2019-08-01 11:29
and those two would just repeat, I think 24 times.
Hm. That actually may be it? I set up port forwarding for Minecraft last week and to do so required that I reset my router/modem, so perhaps in doing so that wiped settings related to Plex.
I don’t remember doing any port forwarding for the Synology before but I may have actually. Is that something I would allow specifically within the Synology’s DSM OS, or would I do it through the router/modem itself? The rule I set up for the Minecraft server was through the router/modem but the way you’re wording “Synology firewall” sounds like it’d be a setting through the DSM OS itself.