Issue Running Plex on Synology DSM 7.2.2-72803

Hello,

I am currently experiencing issues with getting Plex to run on my Synology DSM after upgrading to version 7.2.2-72803 (Intel/AMD 64bit). My Plex server version is Plex Media Server 1.41.0.8930.

I have tried several potential fixes, such as disabling QuickConnect, reinstalling the latest version of Plex, and using the claim functionality, but unfortunately, none of these have resolved the issue. My Plex server has been running flawlessly for many years, and I am a Plex Pass subscriber.

I suspect that the problem might be related to the plex.tv service and SSL, but I cannot confirm this. I have read somewhere in this forum that it might be possible to reset or refresh a certificate through the Plex support forum.

Has anyone else experienced a similar issue or have any advice on this matter? I would greatly appreciate any assistance or insights.

Thank you!

1 Like

Did you installed the version dedicated to DSM 7.2.2 and newer from the official Plex download page?
DSM 7.2.2 isn’t compatible with the builds for older versions.

Yes, at first I tried installing the standard package, but I realized I should use the latest version, which seems to be PlexMediaServer-1.41.0.8930-056c2ed26-x86_64_DSM72 for Synology. However, this version doesn’t work for me.

Edit: Synology model?

What version of Plex Media Server was installed before you updated to DSM 7.2.2?

What happens when you try to install Plex Media Server?

With Plex stopped, using File Station, navigate to the Plex Data Folder. Right click on the Logs directory and compress to Logs.zip. Download and attach to thread…

The Synology is a DS916+

Unfortunately I do not recall the exact number of Plex before the upgrade to DSM 7.2.2… However I always kept it upgraded when I was notified by Plex. So I guess the latest for the latest DSM version before 7.2.2

I have zipped the log files and attached here (link to files)

I have tried several times to remove completely and reinstall but it does not help. There is a small difference if I used local lan ip address then somehow I can make my NAS appear, however I cannot reclaim the server.

In the logfile I noticed
WARN - [HttpClient/HCl#6ea] HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (6, Couldn’t resolve host name) (Could not resolve host: plex.tv)

Furthermore that it seems it be listening on two ports
HttpServer: Listening on port 32400.
HttpServer: Listening on port 32401.
I have always only have 32400 open which usually works - so probably not an issue

Error 6, Could not resolve hostname = DNS lookup failure.

In Control Panel - Network - EDIT the network interface

Make the DNS point to the LAN IP of your modem router -or- google (8.8.8.8)

Also make certain your default gateway is pointing to your modem/router.

Here is mine.

2 Likes

@ChuckPa beat me to it, but I already typed everything, so I’m going to post it anyway. :rofl:


Plex Media Server cannot communicate with the hosts at plex.tv.

Verify the network settings for the NAS.

  • IP address & mask
  • Default Gateway
  • DNS servers - try using public servers such as 1.1.1.1 (Cloudflare), 8.8.8.8 (Google), 9.9.9.9 (Quad9).

Verify the NAS time is correct. Sync with a public NTP server. Control Panel → Regional Options

If you are running the Synology Firewall, you need to allow multiple ports. See What network ports do I need to allow through my firewall?

Note that the above document applies only to the Synology Firewall. For remote access the only port to forward in the router is TCP/32400.

4 Likes

thanks much appreciated and simple solution. :slight_smile: I use DNS package local on the DSM which use to work great. This is because I have local domain names which I direct. However apparently this does not work for me now. Maybe because I need to reconfigure DNS package.

Anyware great! finally - this really saved me time asking in the forum :wink:

I have had exactly the same issue, updated to dsm 7.2.2-72806
updated PMS to the latest version for dsm 7.2+
(PlexMediaServer-1.41.0.8992-8463ad060-x86_64_DSM72.spk)

However when I run Plex it starts, and then very soon after stops.

I have tried changing DNS to use 1.1.1.1

I’ve downloaded the logs

here : plexserverLogs.zip

The ā€œAutoā€ function should clear the damage (the logs look like minor damage)

Read and understand the ā€œREADME.mdā€.
It shows how to do this on synology.

It’s not pretty but it works (I’ve done my best to take the pain out of it)

thank you so much… i’ll have a little play with that… fingers crossed.

in a nutshell.

  1. ssh (Putty) into the Syno
  2. sudo bash (need super privileges)
  3. cd /volume*/PlexMediaServer
  4. wget https://github.com/ChuckPa/PlexDBRepair/blob/master/DBRepair.sh
  5. chmod +x ./DBRepair.sh
  6. ./DBRepair.sh

PMS is stopped.

auto - to auto clean up and repair what it can, usually most/all of it
start - to start plex
– now go try it in the GUI
exit - if everything works ok
-OR-
replace - replace the broken DBs with the most recent valid one.
– It will give you choices if there are. You can also decide how you want to proceed.

I gave it ago… it ran, but couldn’t get past a fail.

So in the end I stopped PMS and tried the last of the two files saved with date extensions
com.plexapp.plugins.library.blobs.db-2024-01-21
com.plexapp.plugins.library.db-2024-01-21

and manually recreated the changes through the plex interface…

I’ve learnt a lot here, so thank you all who have helped make this easier and taken the time to look at those in trouble.

essentially keep a regular backup of the Databases folder seems to be the outcome here, but thankfully Plex seems to partially help with older versions.

here were the logs if anyone interested.
2024-09-16 22.25.19 - Auto - START
2024-09-16 22.25.52 - Check - Check com.plexapp.plugins.library.db - FAIL (11)
2024-09-16 22.26.02 - Check - Check com.plexapp.plugins.library.blobs.db - PASS
2024-09-16 22.26.02 - Check - FAIL
2024-09-16 22.27.43 - Repair - Export databases - PASS
2024-09-16 22.29.07 - Repair - Import - PASS
2024-09-16 22.29.23 - Repair - Verify main database - PASS (Size: 344MB/276MB).
2024-09-16 22.29.24 - Repair - Verify blobs database - PASS (Size: 66MB/70MB).
2024-09-16 22.29.24 - Making repaired databases active
2024-09-16 22.29.24 - Repair - Move files - PASS
2024-09-16 22.29.24 - Repair - PASS
2024-09-16 22.29.24 - Repair - PASS
2024-09-16 22.29.25 - Reindex - MakeBackup com.plexapp.plugins.library.db - PASS
2024-09-16 22.29.25 - Reindex - MakeBackup com.plexapp.plugins.library.blobs.db - PASS
2024-09-16 22.29.25 - Reindex - MakeBackup - PASS
2024-09-16 22.30.06 - Reindex - Reindex: com.plexapp.plugins.library.db - PASS
2024-09-16 22.30.08 - Reindex - Reindex: com.plexapp.plugins.library.blobs.db - PASS
2024-09-16 22.30.08 - Reindex - PASS
2024-09-16 22.30.08 - Reindex - PASS
2024-09-16 22.30.08 - Auto - COMPLETED
2024-09-16 22.35.51 - Exit - Retain temp files.
2024-09-16 22.35.51 - Session end. Mon Sep 16 10:35:51 PM BST 2024

Thanks again for your help. I’m all good now.

VERY glad you’re up and running again.

For your and others benefit,

If you look at this logfile section, Here’s what it’s telling you:

  1. Started an ā€œAUTOā€ pass
  2. The main DB check failed with error code ā€˜11’
  3. The blobs DB was ok
  4. It then declared ā€œChecks - FAILā€
  5. Instead of optimizing, it now knew to repair
  6. Exported the databases (ignoring the damage)
  7. Re-imported the databases
  8. Verified the newly created candidate replacements.
  9. It shows the DB went from 344 MB → 276 MB in size ( a lot of junk / damage )
  10. It shows the blobs DB increased a bit. This is normal when making the DB consistent again
  11. With both having verified, Made them the active DBs
  12. Both repair steps (Main and Blobs) now have PASS
  13. Reindex the data tables inside the DB — this will be huge speedup
  14. Upon exit, you retained the the old DB’s in .dbtmp (you forgot ā€œexitā€?)

oh, hahah, maybe did thank you for the detail. maybe i’ll go back to it and give it another go. thank you again.

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