I skipped the first bad one and updated to the new one with no problems…knock on wood.
My Synology Plex Media Server is stopping randomly
I have the PMS version 1.23.6.4881-6000.
I’ve noticed the issue since the upgrade.
I’m running DSM 6.
I can access my Plex both outside and inside my network on many devices with the app and web…I cannot access the server on the host system at all! I keep getting the message “unable to access server” I’ve tried rolling back and still not able to access my server! this all started after the latest update when I went to restart my server, I then attempted to check settings, and was presented with the message…please help
Hey, guys, problem is back to stay?
Yea im getting the problem again too.
Windows Version 1.24.0.4930 works perfekt for me.
I’m dealing with a problem that seems somewhat related, although not exactly the same as some others in this thread. I originally posted it here: Plex server "crashes" even though Plex logo remains in the Mac menu bar but didn’t get any response. Hopefully some of the admins can take a look and if it’s related, maybe add my logs to the pile to help sort it out.
I initially thought my problem was due to a huge library. But I’ve actually removed a bunch of items recently to try and sort this out, and it doesn’t seem to be helping. Then I found this topic, and realized it might be the latest version of Plex that is the culprit.
The server was down again this morning when I woke up, so I grabbed some fresh logs. Here they are:
Is anyone else still experiencing this? My server is down almost every morning when I get up. Is there a solution? Roll back to a previous version? If so, which one?
I would highly suggest that anyone having issues create a new thread. I don’t think they’re checking this one anymore.
I did create a separate thread here: Plex server "crashes" even though Plex logo remains in the Mac menu bar
15 days ago … but unfortunately no one has responded.
Had this issue with 1.23.4.4712 and downgraded to an old 1.22 version I had sitting around and that fixed the problem (for now).
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.