Plex Media Server stops manually

Plex Media Server NAS & Devices
1

Server Version#: PlexMediaServer-1.43.0.10346

I updated my Synology DS423+ (from DSM Version: 7.2.2-72806 Update 4 TO DSM version: 7.2.2-72806 Update 5) and now Plex suddenly stops by it self.

I start PMS and open the PMS and within a few seconds after login PMS stops again.

In Synology Package Center it reports that PMS stopped manually.
But I didn’t. Meaning Plex lives on its own.

I thought it was due to an old version of Plex Media Server (PMS).
Therefore I updated PMS.
First I updated from Plex Media Server 1.42.1.10060
TO v.1.42.2.10156-f737b826c. Sadly without the hoped effect.

Thereafter I updated to Beta PlexMediaServer-1.43.0.10346
And without positive effect.
Plex Media Server stops right after I start it and logs in.

I’m a bit out in the dark. Can any one please help?

Current installed versions
DSM version: 7.2.2-72806 Update 5
Beta: PlexMediaServer-1.43.0.10346

Before I experienced the problems
Installed version:
DSM Version: 7.2.2-72806 Update 4
Plex version: v.1.42.2.10156-f737b826c

2

Can you post a copy if your server logs

3

Hi

Thank U for your respone.

Hopefully I gathered the right logfiles. It wasn’t that easy using Plex as it stops. But here are the logfiles as a zip-file.

Kind regards

Plex Media Server Logs_2025-12-01_19-49-40.zip (2.8 MB)

4

Looks like this may be a PhotoTranscoder issue Dec 01, 2025 19:48:39.390 [140164836891448] WARN - [Req#6d/PhotoTranscoder] Crash: Crash reporting disabled

Not something Ive done a lot with. @ChuckPa any chance you can see more in these logs?

5

Sounds like it has some thing to do with “photo”.

The “crash” or server-stop happened during a scan after I stored a new movie on it.

The server some kind of halted and/or slowed down.

I thought it was due to at upgrade of DSM version og Plex. In my bewilderness I tried to update the Plex-version. I suppose I should have withhold from doing that.

I hope sincerly the is som kind of possible solution to my wrongdoing.

6

This is fixable, I am just asking for a second opinion from Chuck, as he knows Synos better than almost anyone.

7

Sorry to bother you again. This is the first time I’ve have to reach out to Plex experts. I’m still stucked with a stopping Plex Server. But I dont know if I can or how to reach out to Chuck or appeal to other experts to contribute or direct me to a usable solution.

8

@godtselskab

Your logs show some network connection issues.

I recommend that you reboot the modem/router and everything connected to it, including any wireless devices. important!

That should clear any DNS cache corruption that may be causing the issues seen in your logs.

It also seems that the network connection issues are in part, related to your server crashing/becoming unresponsive.

You should enable Crash Reports in Plex Settings > Server > General > Send crash reports to Plex.

I recommend that you run @ChuckPa’s DBRepair script and optimise/repair your database.

The script can be found here: DBRepair - ChuckPa along with instructions for using the script.

You may also want to run Refresh Metadata on all of your Libraries once the network issues have been dealt with.

9

This networking error needs to be resolved.

Dec 01, 2025 19:49:39.377 [140651058563896] WARN - [HttpClient/HCl#2b] HTTP error requesting GET https://downloads.plex.tv/relay/relay_v1.pub (7, Couldn’t connect to server) (Failed to connect to downloads.plex.tv port 443 after 5005 ms: Couldn’t connect to server)

Dec 01, 2025 19:49:39.377 [140651180579640] ERROR - [EventSourceClient/pubsub/172.104.133.220:443] Relay: Failed to retrieve relay host key from plex.tv

First steps.

  1. Make certain NAS Date & Time are sync’d to the NTP (world clock). If it’s too far out of sync, secure connection (port 443) will fail.
  2. Make certain the Default Gateway IP (Control Panel - Network - eth0 ) points to your modem router and is set as the Default Gateway

If either is changed, restart the NAS and let it come up clean again

PS: I can be pinged by @chuckpa (need the @ in front of my name :slight_smile: )

PPS: My ears were burning :stuck_out_tongue: lol

10

So they should be … lol :stuck_out_tongue:

Good point regarding the Date/Time, I overlooked that … lol

11

Hi ChuckPa

Christmas came in between and postponed my work on my problems on Plex

  1. But now I looking into it. Make certain NAS Date & Time are sync’d to the NTP (world clock). If it’s too far out of sync, secure connection (port 443) will fail.

On the NAS time is set to synchronise on time.google.com

  1. Make certain the Default Gateway IP (Control Panel - Network - eth0 ) points to your modem router and is set as the Default Gateway

I have to clarify what you mean.

Is the Default Gateway IP to be set in the Settings on Plex (wrench) > Settings > Network?

If it is, is it in the Local Area Network I should write the IP Adress of my router?

Or if not, where am I supposed to write it?

Kind regards

Allan

12

Plex does NOT have a Control Panel, so you should set the default gateway in the DSM Control Panel > Network > Network Interface > LAN x Interface settings.

image
image1198×433 9.79 KB

The image above shows the gateway is set to 192.168.0.1 which is correct for my router.

In most cases the gateway will be automatically set, but you should make sure it is actually pointing to your router and not some other address.

You only need to correct it if it was set incorrectly.

13

Hi there

IP-settings on the NAS as shown here:

2026-01-04 14 46 45 NAS IPsettings
2026-01-04 14 46 45 NAS IPsettings400×174 15.8 KB

Sorry, but still same fault / error when I choose Movies (Film) “Something went wrong” (“Noget gik galt”)

2026-01-04 14 19 43 Plex-error
2026-01-04 14 19 43 Plex-error800×453 45.5 KB

14

Have you repaired the database as I recommended earlier?

Try re-pinning your libraries to the Home page by going to More > and clicking on a library and select Pin etc…

15

Hi Trumpy81

If you mean ChuckPa database-repair. No, I am kind of afraid of messing with a server in terminal. The last time I tried I ruin my NAS totally. So I’m a newbee and did not repair using ChuckPa . I rekon it’s the best way to solve my problems but I’m into the dark even though ChuckPa has detailed instructions. I don’t dare don’t know how to go down that road. Sorry for my incompetence in this field.

In Plex I have tried to optimize the database (I chose the wrench (1) > Administration (2) > Troubleshooting (3) > Optimize Database (4) and also Clean Up Content (5). (My translations to the attached picture on my danish installation with numbers).

2026-01-04 17 13 Plex-error 02
2026-01-04 17 13 Plex-error 02632×833 99.6 KB

16

Unfortunately, your steps wont cut it, you really need to run ChuckPa’s script in order to correct your issues.

I know it is daunting, but you must try it at least.

Make sure you back up your NAS configuration in DSM Control Panel > Update & Restore > Configuration Backup before you start, although it should not be needed at all, none of the commands given by ChuckPa are dangerous at all.

You can also backup the PlexMediaServer folder and all of it’s contents.

I recommend using Hyper Backup which you will find in the Package Center for that.

Make sure you enable SSH in DSM Control Panel > Terminal & SNMP.

Here is what you need to do after downloading the DBRepair.sh file from ChuckPa’s page and placing it in the PlexMediaServer folder on your NAS.

Hit enter after you type in each command.

  1. Open a terminal window on your PC
  2. Type in ssh NasAdminUserName@NAS-IP-Address
  3. Type in your NAS Admin User Password (it will not show on screen)
  4. Type in cd /volume1/PlexMediaServer
  5. Type in sudo bash (the prompt in the terminal window will change)
  6. Type in chmod +x DBRepair.sh
  7. Type in ./DBRepair.sh (Don’t forget the . period at the beginning of the command)

Then you should be presented with a numbered menu. You want to:

Stop Plex (option 1)
Run the Automatic routine (option 2)
Start Plex (option 7)