Plex Media Server won't open in DSM or browser with LAN IP

Plex Media Server NAS & Devices
1

Server Version#: 1.41.5.9522-
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

On DSM the Plex Media Server is running, but when attempting to open it, I get the error “DSM Synology Can’t Open the Page” (“192.168.0.101:32400/web”) with details about the server unexpectedly dropping the connection. The IP is correctly that of my NAS.

I get a similar error in MacOS Chrome for the same URL.

The server itself is running and can be accessed normally via “https://app.plex.tv/”

(as you can see, in an effort to fix this, I attempted to install a version newer than the “newest” one listed in Synology package center, which is 1.40.4.8840… But the issue persists)

2

@redrocklobster

When you change versions, there is always a few extra seconds to update the database. Sometimes they have more significant database changes which requires minutes (not often but it happens).

During that initial period, you should get a “503 Maintenance” reply when attempting to open PMS

With you sharing that it’s dropping the connection, that’s more serious and sounds like a DSM configuration problem. These are usually easy to correct once we identify it.

Would you please:

  1. Stop PMS
  2. Wait a minute
  3. Start PMS
  4. Wait two minutes for it to initialize fully and be stable
  5. Attempt to access it by the LAN IP:32400/web URL
  6. Stop PMS

Now, in FileStation,

  1. Navigate to PlexMediaServer/AppData/Plex Media Server
    – Or Plex/Library/Application Support/Plex Media Server (DSM 6)

  2. Right-click ‘Logs’ → ‘Compress to Logs.zip’

  3. When complete, Download the Logs zip file and then upload it here.

This will let me see what’s happening

3

Thanks for the quick reply!

Logs.zip (3.8 MB)

Edit/FYI:
I had to select all the files in the Logs folder to be able to compress from File Station. Not an option to compress the folder. right clicking on “Logs” did not have a compress option. The action menu has a compress option but all items in that menu are greyed out for the Logs folder. (permissions are allow RW for PlexMediaServer and all administrators). I copied it elsewhere and zipped it.

4

Curious, any ideas? thanks

5

@redrocklobster

Thanks for pinging me again. For some reason, the forum didn’t alert me.

It looks like your server is set for Secure Connections = required.

There is a device ( 192.168.0.208 ) which is trying to connect HTTP, not HTTPS

Apr 26, 2025 15:02:50.431 [140674813119288] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57944 rejected because secure connections are required
Apr 26, 2025 15:02:50.433 [140674813119288] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57946 rejected because secure connections are required
Apr 26, 2025 15:02:50.434 [140674813119288] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57947 rejected because secure connections are required
Apr 26, 2025 15:02:50.436 [140674813119288] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57948 rejected because secure connections are required
Apr 26, 2025 15:03:15.352 [140674755332920] DEBUG - [NSB/SSDP] Parsing SSDP schema for http://192.168.0.102:80/description.xml
Apr 26, 2025 15:03:15.357 [140674794142520] DEBUG - [HttpClient/HCl#3a] HTTP/1.1 (0.0s) 200 response from GET http://192.168.0.102:80/description.xml
Apr 26, 2025 15:03:15.357 [140674755332920] DEBUG - [NSB/SSDP] found 1 SSDP devices via http://192.168.0.102:80/description.xml
Apr 26, 2025 15:03:15.358 [140674755332920] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.0.102 (Hue Bridge (192.168.0.102))
Apr 26, 2025 15:03:31.749 [140674813119288] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57977 rejected because secure connections are required
Apr 26, 2025 15:03:32.808 [140674813119288] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57978 rejected because secure connections are required
Apr 26, 2025 15:03:32.809 [140674815228728] DEBUG - Request: plaintext connection from [::ffff:192.168.0.208]:57979 rejected because secure connections are required

Does this make sense to you?

6

perfect, thank you. yes it does make sense. i guess i must have changed the “secure connections” network settings from “preferred” to “required” when I initially set it up. I believe “preferred” was the default then. Is it advisable to leave it on “preferred”?

(btw, if so, opening the “Plex Media Server” app from DSM doesn’t provide an option to connect securely on the LAN so it just wouldn’t work, right?)

7

@ChuckPa , apologies if I’m hijacking the thread, but I’ve been experiencing what seems to be the same symptoms redrocklobster had, but I can’t see that it’s the same problem.

When I’m logged onto my Synology NAS and try to open Plex I get the same error message about dropped connection, and like him accessing Plex via “https://app.plex.tv/” worked.

Versions are Plex Server, 1.31.5.9626 and Synology DSM 7.2.2-72806 Update 3, my Synology’s IP is 192.168.1.3 and I’m trying to access from my MacBook on 192.168.1.206. .

I followed your instructions to redrocklobster in order to create log files, and tried searching for similar error messages related to “rejected because secure connections are required”, but couldn’t find any. Quite possible I’ve missed it, but I wondered if you could had any ideas? I’ve uploaded the zipped log file.

Thanks, and if I should start a new thread please just let me know!

Andrew
Logs.zip (14.4 KB)

8

Plex’s clients will all automatically change from HTTP → HTTPS as soon as they can.

If you look at Plex/web, even though you might connect with HTTP in the URL, the green dot in the left panel means HTTPS (encrypted).

I always use Preferred network setting.
PMS knows (for all Plex clients) to use HTTPS for everything remote.

In spite of the Syno link in package center, it is starting HTTP but immediately flipping to HTTPS.

1 Like
9

Thanks for replying, I should have mentioned that “preferred” is selected for secure connections. After digging further, I realised that the Firewall and I hadn’t added port 32400, doing so solved it.

1 Like
10

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