Server Version#: 1.22.0.4163
Plex server is installed via community package and has recently crashed several times with no obvious cause. I’m including the logs in the hopes something stands out.
Thank you for the reply. I followed each direction. Hopefully that works.
I wanted to get back and say I have experienced no new crashes, but still see
Error issuing curl_easy_perform(handle): 60
I run pfSense as my router and I have taken the steps with the DNS resolver to add plex.direct (actually I had it in there already)
I can connect securely from devices outside the LAN.
Thoughts?
I’m attaching new logs if they are needed.
Plex Media Server Logs_2021-04-05_19-53-09.zip (6.8 MB)
Not in any way that I’m aware of. I wouldn’t know how to change/modify it.
I’ll run the optimize and clean.
Curl error 60 occurs when you have a certificate problem / http vs https
If Secure Connections are required and attempt to open http, curl error 60 results (server sent no data). The socket opened but SSL/TLS didn’t setup so no data was sent and socket closed.
What if anything can /should I do about it?
Don’t know what to tell you.
Apr 05, 2021 19:32:37.768 [0x7fc92d52d700] INFO - Plex Media Server v1.22.2.4264-b275c4330 - Synology DS918+ x86_64 - build: linux-x86_64 synology - GMT -07:00
Apr 05, 2021 19:32:37.768 [0x7fc92d52d700] INFO - Linux version: DSM 6.2.3.25426-3, language: en-US
Apr 05, 2021 19:32:37.768 [0x7fc92d52d700] INFO - Processor Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz
The DS918+ is a J3455 CPU.
I don’t know what this is with it claiming to have an E3-1225
I’m running DSM via xpenology boot loader.
@Bulfinch That’s the reason why Plex is crashing
It could be the case, but since fixing the net mask I had incorrectly set, there hasn’t been a crash. Additionally, I’d expect this forum, reddit, and others to be filled with… IF xpenology boot THEN plex no work, but that’s not the case either.
But I guess it could be the issue related to a crash.
Such things as wrong drivers being used can cause a crash and I’m sure you must be aware that there is plenty of posts on the Xpenology forums that do highlight this.
So I went over the Xpenology forum and poked around and discovered that I was indeed behind on a driver update to the bootloader. Got the new one loaded up and voila, most of the errors cleared up.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
