Plex Completely Unusable

Server Version#: Any
Player Version#: Any

A few months ago, plex became unreachable for me. My LG smart TV app only would give me “Plex Servers Unreachable” error and I could not access anything, even settings.
On my computer, I cannot access plex on chrome. (firefox seems to work okay) Chrome gives the same error that my TV does.
I uninstalled my plex media server from my Synology NAS (DS920+ / DSM 7.1.1-42962, update 1), hoping that a fresh install would fix it. It did not. I am now unable to claim my server. (if I can get it to install on my NAS at all.) I cannot install with the claim token, and when I install it and try to perform a claim after, it doesn’t seem to access plex before the claim token times out (is my guess).

For a while, I thought it might be an account issue, so I deleted my account and started over. Now I’m back, and nothing is fixed. I think I’ve properly done some port-forwarding, but that didn’t seem to help either. I downloaded the Plex app for windows, but it just loads forever.
Plex went from being my favorite software, to my biggest headache. Please help! I have no idea what else to try.

Is Plex Media Server still installed on the Synology?

If so, what version? It is visible in the Synology Package Center.

Do you still have the /PlexMediaServer shared folder?

If so, using Synology File Station, navigate to /PlexMediaServer/AppData/Plex Media Server.

Right click on the Logs directory and choose Compress to Logs.zip.

Download the zip file and post it to this thread. You can drag it into the message window. It will insert at the cursor location.

I do not have it currently installed. I can recreate it though.
When I try to install (from Synology Package Center) with the claim token, it says “Coul dnot complete dialog with Plex.tv. Unable to claim.” almost instantly. When I install without, it installs just fine, but when I open the URL to try and claim, it just times out, giving an “unable to connect” error.

This behavior is the same if I manually install the most recent version from the Plex Media Server Download page.

I have re-installed from package center, then manual install with the new version. I have put both log files here:
Logs-PackageCenter.zip (113.9 KB)
Logs-PlexManualInstall.zip (200.8 KB)

After starting from scratch, and redoing my port forwarding, I somehow got plex to open from the nas, and I see the server (kinda), but it still refuses to claim it. I’m doing this on firefox browser, because all other access points (LG-smartTV, Chrome, & Plex Windows app) still just give errors. If I open plex.tv any other way, I do not see the server (I assume because I haven’t claimed it).

I assume it’s a networking or port-forward issue. Since theoretically, I should be seeing something, even the plex streaming services on my devices, right? even without the media server, on most devices I can’t see plex at all. I have no idea why firefox seems to mostly work for me. Luckily it does, or I would be completely locked out.

Here is the current Logs folder.
Logs.zip (313.5 KB)

@SNGmagician

I’ve edited your tagging. This is only a Synology server issue. No need to splatter-tag the forum.

The error is right here.

Feb 08, 2023 11:48:10.947 [0x7f3cc68eab38] WARN - [HttpClient/HCl#13] HTTP error requesting GET https://plex.tv/users/4495c5a6c24c43af/avatar?c=1675195730 (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 no servers registered at Plex.tv.

  1. Stop PMS.
  2. Open Filestation
  3. Navigate: PlexMediaServer/AppData/Plex Media Server/Cache
  4. Delete cert-v2.p12
  5. Restart PMS
  6. Give it an extra 15-30 seconds to get a new certificate
  7. Now open by LAN IP only . http://192.168.1.134:32400/web
    – with you on the same LAN subnet.

Feb 08, 2023 11:49:24.479 [0x7f3cc7003b38] DEBUG - [Req#70] MyPlex: Did token exchange for claim (returnCode: -60)
Feb 08, 2023 11:49:24.480 [0x7f3cc7003b38] DEBUG - [Req#70] MyPlex: Got a token poked, let’s act on it.

This implies you’re using QuickConnect or your own FQDN. Neither can be used for claiming

@ChuckPa
Thank you for your help,
However, I do not think this is just a Synology server issue. I’m not able to access any form of plex. Not just my media server. Which is why I used multiple tags.

I did as you suggested, but I did not have a cert-v2.p12 file at that location, or any other location in the PlexMediaServer directory.
I am also aware that I should not use quickconnect for claiming. I have ceased doing so, and even through the LAN IP, I am unable to claim the server. I can see that my media server exists within plex, but the “claim server” button does nothing. I am also still unable to install with a claim token while on LAN IP.
All of this still does not explain why my TV, chrome, and plex app for widows are unresponsive and only says “plex is not reachable”. If I even get an error. The only places I see any signs of life from plex is from Firefox, and my mobile app, but both are still not behaving properly. I do not think that behavior would not be caused by a plex media server issue.

@SNGmagician

Given what I see in your logs, I’m very much thinking a networking issue.
Not able to get a good cert from Plex.tv and authenticating – Network.

Do you have the Syno firewall enabled ?

If you do, and have your normal firewall (at the modem router) ?

Asking because,

  1. Under normal circumstances , the modem/router firewall is more than enough
  2. Running the Syno firewall complicates access for all devices on your LAN.

If it’s enabled , for testing purposes, Turn the Syno firewall OFF.

Let’s get basic stuff working.

Also, in the Syno : Control Panel - Network - ETH0 (which is your active adapter)
– Make sure the DNS and IP point to the modem/router IP
– Make sure it’s the “Default Gateway”
– Make sure you don’t have “Jumbo Frames” enabled.

@ChuckPa

I did have the Syno firewall on. I have now disabled it, with no noticeable effect.

As far as I can tell, all of the Synology network settings you mentioned are correct.
the DNS server is not set to manual, so it should be automatic, and unchanged.
The default gateway is an IP that points to my router. (through LAN direct line)
And I couldn’t find anything named “Jumbo Frames”, and I don’t remember changing anything similar to that. (I’ve only had the NAS about one year).

@SNGmagician

Let’s get a little radical with it.

  1. Stop Plex

  2. From Filestation, navigate into ‘PlexMediaServer/AppData/Plex Media Server’

  3. Delete the “Cache” folder.

  4. This might take a moment so let it clean it all up.

  5. When completed, Start PMS

  6. Give it 3 minutes to get started without accessing it (wait for the CPU usage in the Syno activity/health widget to drop to near zero CPU usage. (in case it’s running DB maintenance again)

  7. When it’s idle,

  8. Stop PMS

  9. Back in Filestation

  10. You’ll see the “Logs” folder

  11. Right-Click → Compress to Logs.zip

  12. Download the ZIP file

  13. Attach here.

What I’ll be looking for is a fresh pull of credentials and setup of the networking.

Quick question: Is your forum username the same email address you register the server with ?

@ChuckPa

Here are the new logs as requested.
yes, it should be the same email on both.

Logs-CacheDelete.zip (472.1 KB)

Did you install a certificate for the Syno to be something OTHER than the default synology certificate ?

The machine is getting a MITM certificate mismatch when it attempts to talk to Plex.tv

CURL error 60 =

Error “curl: (60) SSL certificate problem: unable to get local issuer certificate” can be seen when the SSL certificate on the server is not verified or properly configured

Your Logs show:

Feb 08, 2023 15:00:28.716 [0x7f72a2dd4b38] WARN - [HttpClient/HCl#5] 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’)

Replies back from Plex.tv are being “edited” to a different domain / cert.

Do you have a Proxy or VPN involved ?

@ChuckPa

No, not to my knowledge. My Certificate list is only Synology items. During my troubleshooting, I tried to get the plex certificate key to work, but I never got through the process.

I do not have a VPN or Proxy active.

@SNGmagician

ould you please go into the PlexMediaServer shared folder ?

Delete AppData-chuck ?

I forgot to before I logged out.
You don’t need that wasting space.

To all that find this:

This was a tough one.

  1. Somehow the Syno lost its IPV4 identity.
  2. The hostname was routed back to ::1 (loopback) in /etc/hosts
  3. editing /etc/hosts
    – Manually adding Lan.IP.of.Syno SynoName
  4. Restarting
  5. Plex came up clean without any issues.
1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.