Synology 7.2.2 just installed on a new 1522+, just getting a blank screen

Plex Media Server NAS & Devices
1

Server Version#: 1.41.4.9463-630c9f557-x86_64_DSM72
Player Version#: all

I’m not new to plex, but I am new to DSM 7.2.2. I installed the latest version and 7.2.2 appears to be a slightly different animal, and I’ve granted permissions to several directories for Movies, TV, etc. but when it comes up in a web page, all I get is a black screen with the PlexTV logo in the middle.

I don’t know if this is a permissions issue or something more fundamentally wrong. Ultimately what I’m trying to do is connect it to my existing Plex account to replace an older server, and this is not going the way I expected it to go.

I can upload log files if that will help. I will have to take out personal details, but that won’t take long. Just tell me which logs to upload.

2

Did you give user PlexMediaServer permission to read all files and folders in the share(s) containing your media?

Please check here and pay attention to the “Apply to this folder, sub-folders, and files” box

3

Thank you for your reply. This is a first-time installation of Plex on the DS1522+. When I just set it up, I did tell it to update the OS to the latest (7.2.2). I went through the faq you mentioned, doubled checked permissions, including ensuring permissions were cascaded down through sub-folders and such, I even uninstalled (removing everything) and re-installed, but when I try it in my browser I get the same results; a black screen with the PLEXTV logo in the middle.

I’ve looked through the logs, and I don’t see anything obviously wrong (I was looking for “ERROR” or something similar, but I didn’t see anything like that). The only thing that I can think of it although this NAS has four ethernet ports, I’m only using one at present, but those ports do show up log files with the typical 169.x.x.x address that you get when it doesn’t.

Any other ideas?

I’m probably missing something very obvious, but I can’t think what.

UPDATE: Looking through the log, I see this:
LINE 1: Feb 22, 2025 05:02:58.672 [139813707635512] DEBUG - [JobRunner] Job running: /volume1/@appstore/PlexMediaServer/CrashUploader “–directory=/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Crash Reports/1.41.4.9463-630c9f557” --version=1.41.4.9463-630c9f557 --platform=Linux “–platformVersion=DSM 7.2.2.72806-3” --serverUuid= --userId=NOUSERID --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Synology --model=x86_64 --device=DS1522+

LINE 2: Feb 22, 2025 05:02:58.673 [139813707635512] DEBUG - [JobRunner] Jobs: Starting child process with pid 20514

LINE 3 Feb 22, 2025 05:02:58.682 [139813723900728] DEBUG - Jobs: ‘/volume1/@appstore/PlexMediaServer/CrashUploader’ exit code for process 20514 is 1 (failure)

Later I see this:

Feb 22, 2025 05:02:59.109 [139813728635536] INFO - SQLITE3:0x80000001, 17, statement aborts at 56: [select * from metadata_items limit 1] database schema has changed

This repeats 20x and it seems to keep trying to execute the SQL statement in groups of 20

I compared it with previous versions of the logs from DSM 6.x and they’re completely different.

4

the schema change notices are not a big deal, thats fairly common, can you post a copy of your server logs?

5

Sure. The logs I’m including are:
Plex Media Server.log
Plex Tuner Service.log
com.plexapp.system.log
Plex Media Server.log (1004.6 KB)
Plex Tuner Service.log (2.0 KB)
com.plexapp.system.log (200.5 KB)

I apologize for not being able to do it the proper way, but as I said, Plex just presents a black screen with the PLEXTV logo in the middle.

6

I am not seeing anything meaningful in those logs, can you provide a zip of your log directory?

7

I did a stop and start to see if it would give more information.

8

Are you censoring or removing anything from your log folder? I am only getting a very limited amount of information.

EDIT: Delete that last zip file ASAP, you posted more information that you should have. All I was asking for was the log directory.

9

No, not even a little. When I installed, I originally “claimed” this server (I created the key). For these logs, I unclaimed it, uninstalled it and installed again, checking permissions, giving it RW access to Movies, TV Shows & The Plex directory itself (I don’t know if that’s a problem). And then stopped and started it again.

Logs(1).zip (1.8 MB)

It might be worth mentioning I have two other plex servers running, I don’t know if that would affect anything though. Also, can I go into a config file and bump up the logging level? Don’t know if that’s possible for an end user.

Just looking at how it comes up again, it comes up with a large PLEX TV logo, that disappears, then it goes to a small plex TV logo and then its just “dead” at that point

10

Why? Please just use plex normally what you did was wipe out a lot of information that can be useful. Please re-claim the server and use it normally, then provide a copy of your log files. Unclaimed servers behave differently than claimed servers. Then can you please visit http://[Local Plex Media Server IP Address]:32400/web in an incognito tab and let us know if it behaves differently?

11

So reclaiming the server actually made it work. When I put in the local address in an incognito it mostly seemed to work, except for a stray DS1522 that kept saying it couldn’t connect. But at the same time there was another DS1522 that would connect and all my other servers were available as well.

I think the problem all along was the address that was given in the Synology Server is really kind of a dead end in the DS1522 server, and I actually needed to log into my Plex account and all was visible. That’s just a guess, BTW.

I can’t thank you enough for your help. If you were local, I’d buy you lunch,
(Let me know if you’d still like to see the logs)

12

What happened there is when you uninstall/re-install claim/unclaimed you created two different servers (both being ran on the same DS1522) in your preferences.xml there is a value that identifies the server. When you were doing that you generated a second server ID, which means the previous server became a ghost.

13

Is there any harm in editing the preferences XML file?

14

That is wholly dependent on if you know what you are modifying. In general it is rarely necessary to manually edit that file. Most settings can be accessed via the web. In cases of reclaiming ChuckPa has a very useful tool for both making the needed xml changes, and actually claiming the server.

15

To add to @dbirch’s comments, there is no need to edit preferences.xml to unclaim/re-claim.

Instead, uninstall/re-install Plex Media Server using Synology Package Center. See FAQ 31: Reset / Reclaim PMS on DSM 7 (Not Authorized - Locked Out).

If the “ghost server” is still hanging around, remove it from your list of Authorized Devices. You may also need to unpin associated libraries in your clients.

16

After I logged into my plex.tv account the ghost server went away. In addition, I saw the two instances of servers in my account and I deleted the old one.

17

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