You open the Plex app, and instead of your library you see “Plex Media Server is not available.” It was working fine yesterday. Nothing changed — or so you thought.

This error is one of the most common Plex issues, and it has a surprisingly long list of possible causes. This guide walks through every one, from the obvious to the obscure, so you can get your server back online fast.

What “Server Not Available” Actually Means

This error means your Plex client (app, web player, smart TV) can’t reach your Plex Media Server process. The server might be down, unreachable on the network, or running but not responding to requests.

It does not necessarily mean your server hardware is off. The Plex Media Server software could have crashed, the service could have stopped, or a network issue is blocking the connection.

Step 1: Is the Server Process Running?

Windows

Open Task Manager (Ctrl+Shift+Esc) and look for Plex Media Server.exe in the Processes tab. If it’s not there, the server isn’t running.

Linux / Docker

Run systemctl status plexmediaserver (bare metal) or docker ps | grep plex (Docker). If the service is stopped or the container exited, restart it and check the logs.

NAS (Synology / QNAP / Unraid)

Open your NAS admin panel and check if the Plex package is running. On Synology, go to Package Center → Plex Media Server → check status. On Unraid, check the Docker tab.

Step 2: Can You Reach the Server Locally?

From a browser on the same machine as the server, try: http://localhost:32400/web

If this works, the server is running — the problem is network-related (your client can’t reach the server).

If this doesn’t work either, the server is genuinely down or not listening on port 32400.

Check the Port

Step 3: Network and Firewall Issues

Local Firewall Blocking

Windows Firewall, UFW (Linux), or your NAS firewall might be blocking port 32400. On Windows:

  1. Open Windows Defender Firewall → Advanced Settings
  2. Check Inbound Rules for “Plex Media Server”
  3. If missing, create a rule allowing TCP 32400

Antivirus Interference

Third-party antivirus software (Norton, McAfee, Bitdefender) sometimes blocks Plex connections. Temporarily disable your AV and test. If that fixes it, add an exclusion for Plex.

VPN Conflicts

If you’re running a VPN on the server machine, it can route Plex traffic through the VPN tunnel instead of the local network. Solutions:

Step 4: Plex Account and Claim Issues

Server Not Claimed

If you reinstalled Plex or reset your server, it might be unclaimed. Go to http://localhost:32400/web and sign in with your Plex account to reclaim it.

Plex.tv Authentication Down

Plex uses plex.tv for authentication. If their servers are down, you can’t sign in — even to access your local server. Check status.plex.tv and the Plex Forums for outage reports.

For local-only access during outages, you can add your network to the “List of IP addresses and networks that are allowed without auth” in Settings → Network.

Step 5: Corrupted Preferences or Database

Sometimes Plex’s preferences file or database gets corrupted, especially after a crash or power loss.

Reset Preferences

  1. Stop the Plex server
  2. Navigate to your Plex data directory and find Preferences.xml
  3. Rename it to Preferences.xml.bak
  4. Restart Plex — it will create a fresh preferences file
  5. You’ll need to reclaim the server and re-add your libraries

Database Repair

If the SQLite database is corrupted, Plex provides a built-in repair tool. Go to Settings → Troubleshooting → “Repair Library Database.” For severe corruption, you may need to restore from a backup or rebuild.

Step 6: Updates Gone Wrong

A failed Plex update can leave the server in a broken state. If the error started after an update:

When Nothing Works

If you’ve gone through every step and the server still won’t come back:

Need Help With This?

Our Plex specialists can set this up for you — remotely, same day, flat rate.

See Pricing & Book