Server getting slower and buggier

Server Version#: 4.43.4

I’m been having increasing problems with my Plex Server that I’m not sure where to go to fix. Basically, it’s become slow and buggy. Here are the key points:

  • If I reboot the computer it’s on, the server software will not launch properly. It will stall out, say “application not responding”. Every time I reboot the computer it takes 2-4 times of force quitting Plex and restarting it before it finally connects.
  • Users say that they notice the server is lagging. I often have problems connecting to it even in my home network (with devices that are hard wired, so not a wifi problem). It will drop a couple times a a week completely, then come back 10-15 minutes later.
  • Meta-data has a really hard time loading. When adding new content it will take hours before it finally files in meta-data and almost always I need to manually match it and force meta-data to load
  • The server itself is plenty powerful enough to run Plex and isn’t doing much else. It’s an iMac 2013 3.2 i7 Quad Core with 24 GB of RAM and a dedicated GPU. I recently ran tests on all the hardware and it’s working fine. Running macOS 10.15 Catalina. Content is on a attached RAID.
    *I have been running Plex continuously since 2009. Since about 2013 when I had a server failure and had to restore from a backup, my server has been basically cloned from one Mac to another every time I do a hardware upgrade.

So basically I just need tips on what it could be and what I need to try. Do I just need to uninstall and reinstall PMS? Do I need to bite that bullet and move to a Docker instance (and is it worth the effort)? Should I be doing a complete restore of the Mac and reinstalling PMS, then restore my server content from the backup?

I just want some tips as it’s been frustrating to my users and to myself. I’m having problems I didn’t have years ago on older hardware running PMS.

Hi, just read through your posting. Here are some suggestions for your Haswell powered iMac

  1. I would try dumping your Server’s cache and restart.
    Re seat your RAM
    Reset SMC
    Reset PRAM
    A lot of clients have a reset.
    Avoid implementation IPv6 on clients and Server
    Disable DLNA in Server if not used.
    Avoid collection of files that will Transcode ( Broadwell and later recommended)

  2. Look at a different DNS like 8.8.8.8 or 1.1.1.1 applied at clients, Server and if possible Router
    Clearing Plugin/Channel/Agent HTTP Cache
    Reset your router
    Reserve or make Static LAN IP addresses of all LAN playing devices including server
    You don’t mention your clients but adding in settings there manual Server IP Address and port .

  3. Failing all, a clean instillation of PMS. Following the correct way of Uninstalling Plex.
    Migrate to Plex’s new Scanner.

https://support.plex.tv/articles/202967376-clearing-plugin-channel-agent-http-caches/

https://support.plex.tv/articles/201941078-uninstall-plex-media-server/

1 Like

Thanks! Appreciate all those suggestions. Some I have already done (I’m a Mac tech so resetting the SMC and PRAM for example). Using a static DNS is something I do as well. I also use a PiHole which hasn’t really been an issue but I guess would be something to check. I’ll try those Plex specific things you suggested and maybe just do a clean installation of PMS. After running from one box to the next for 7 years, it’s probably about time.

Could you tell me a bit more about avoiding collection of files that will Transcode?

You would have to detail your clients. Example, I use a 2018 LG 65OLEDB8 mostly, along with 2 iPads, I do share.

Movies 98% HEVC, 5.1 AAC, TV mostly H.264 EAC3. I do have some 4K stuff but all 5.1 channel.

It’s a matter of testing your equipment and checking your advanced dashboard in the server for Trans coding. This way the load is off your server from the beginning. You can limit trans codes in server settings. There then the issue of remote shares hardware, if you don’t Transcode and they need to, it’s a better situation.

As for DNS I have found that ISP DNS are notoriously flaky and slow. Never had the need for PiHole as I protect my Network and such with a double NAT router arrangement to iOT’s, leaving my server totaly protected by weakness in the network security. To add I have found I can in my location up my MTU to 3000 which has improved my response times.

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