Plex App Not Connecting to Server — Fix Connection Issues

You open the Plex app and your server is nowhere to be found. Or it appears in the sidebar but shows as "Unavailable." Or it was working five minutes ago and now everything is gone. Connection failures between Plex clients and servers are frustrating precisely because the symptom — "cannot connect" — has dozens of possible causes. This guide walks through them systematically, from the obvious to the obscure.

Step 1: Is the Server Actually Running?

Start with the simplest check. On the machine running Plex Media Server, verify the process is active. On Windows, open Task Manager and look for "Plex Media Server" in the process list. On macOS, check Activity Monitor. On Linux, run systemctl status plexmediaserver or ps aux | grep plex. On NAS devices (Synology, QNAP, Unraid), check the package or container status in the management UI.

If the server is not running, start it. If it was supposed to be running but stopped, check the logs for crash information (see our guide on Plex server crashes).

Next, confirm you can access the server locally. On the server machine itself (or another device on the same network), open a web browser and navigate to http://[server-ip]:32400/web. If this loads the Plex web interface, the server is running and accessible on the local network. If it does not load, the issue is with the server itself, not the client.

Step 2: Same Network Test

If you are trying to connect from outside your home network, first confirm the client can connect when on the same local network as the server. Connect the client device to your home WiFi, then try again. If it works locally but not remotely, the problem is remote access (port forwarding, firewall, or NAT issues). If it does not work even locally, the problem is network discovery or authentication.

For local network issues, check whether client and server are on the same subnet. If your router has separate networks for 2.4 GHz and 5 GHz WiFi, or if you have VLANs configured, the client and server may be on isolated network segments that cannot communicate. Plex uses GDM (G'Day Mate) protocol for local server discovery, which relies on UDP multicast. If multicast is blocked between subnets, the client will not discover the server automatically.

Step 3: Sign Out and Sign Back In

Plex uses plex.tv authentication to link clients to servers. When this authentication breaks — due to expired tokens, password changes, or account issues — the client cannot verify its connection to the server, even if the network path is fine.

On the client app, sign out of your Plex account, close the app completely, reopen it, and sign back in with your plex.tv credentials. This refreshes the authentication token and forces the client to re-discover your servers through plex.tv's connection broker.

On the server side, check that the server is signed into the correct plex.tv account. Go to Settings > General in the server web interface and verify the account shown. If the server was "claimed" under a different account than the one you are signing into on the client, the client will not see it.

Step 4: Clear App Cache

Plex client apps cache connection data, server lists, and authentication tokens. Corrupted cache data can prevent connections even when everything else is configured correctly.

iOS: The Plex app does not expose a cache-clearing option. Delete the app from your device and reinstall it from the App Store. This clears all cached data.

Android / Fire TV: Go to device Settings > Apps > Plex > Clear Cache. If that does not help, also try Clear Data (this will reset the app to its initial state, so you will need to sign in again).

Smart TVs (Samsung, LG, Roku): Uninstall the Plex app and reinstall it. Most smart TVs do not offer a separate cache-clearing option.

Desktop (Windows / macOS): For the Plex desktop app, try uninstalling and reinstalling. For the web player at app.plex.tv, clear your browser's cache and cookies for plex.tv and app.plex.tv domains.

Step 5: DNS Issues

Plex clients connect to plex.tv to authenticate and discover servers. If DNS resolution for plex.tv is failing on your network, the client cannot complete authentication and will appear unable to find your server, even on the local network.

Test DNS resolution by opening a web browser on the client device and navigating to https://plex.tv. If the page does not load, DNS is likely the issue. Try changing your device's DNS settings to use a public DNS server like Google (8.8.8.8, 8.8.4.4) or Cloudflare (1.1.1.1, 1.0.0.1).

Some ad-blocking DNS solutions (Pi-hole, AdGuard Home) or corporate network filters may block Plex-related domains. If you use a network-level ad blocker, check whether any plex.tv subdomains are being blocked and whitelist them.

Step 6: Firewall and Security Software

Firewalls on both the server and client side can block Plex connections. On the server, ensure port 32400 (TCP) is open for incoming connections. On the client device, ensure outgoing connections to port 32400 are not blocked.

Third-party security software (Norton, McAfee, Kaspersky, Bitdefender) frequently blocks Plex connections. These programs may identify the Plex traffic as suspicious and silently block it without any visible error. Temporarily disable your security software to test whether it is the cause. If it is, add an exception for Plex Media Server and port 32400.

On macOS, the built-in firewall may block incoming connections to Plex. Check System Settings > Network > Firewall > Options and ensure Plex Media Server is set to "Allow incoming connections."

Step 7: Plex Relay

When a direct connection cannot be established between a client and server (due to NAT, firewall, or port forwarding issues), Plex falls back to its Relay service. Relay connections are routed through Plex's infrastructure and are limited to 2 Mbps for Plex Pass subscribers and 1 Mbps for free users.

If your connection is going through Relay, you will see "Relay" or "Indirect" in the server information or the Plex dashboard. While Relay provides a working connection, the bandwidth limitation makes it unsuitable for anything beyond low-quality video. To avoid Relay, fix the underlying connection issue (usually port forwarding) so clients can connect directly.

Note that Relay requires an active internet connection on both the server and client sides. If either side loses internet, Relay connections drop. Local playback is not affected by internet outages as long as the client can reach the server on the local network.

Step 8: Manual Server Connection

If automatic server discovery is failing, you can add your server manually in most Plex client apps. This bypasses the plex.tv discovery mechanism and connects directly to your server's IP address.

In the Plex client settings, look for an option to add a server manually (the location varies by platform). Enter your server's local IP address and port (e.g., 192.168.1.100:32400 for local connections) or your public IP address and port for remote connections. Some clients require the full URL: http://192.168.1.100:32400.

If manual connection works but automatic discovery does not, the issue is likely with GDM multicast on your local network or with the plex.tv connection broker for remote access. Manual connections are a viable permanent workaround for networks where multicast is restricted.

Platform-Specific Notes

iOS: Ensure the Plex app has permission for local network access (Settings > Privacy > Local Network > Plex). iOS may prompt for this permission on first launch, and denying it prevents local server discovery.

Android TV / Google TV: Some Android TV devices have aggressive battery optimization that kills background connections. Ensure Plex is excluded from battery optimization in device settings.

Roku: Roku devices occasionally lose their Plex link. Unlink and relink the device in the Plex web interface under Settings > Authorized Devices.

Smart TVs: Older smart TV Plex apps may not support newer authentication methods. Check whether a firmware update is available for your TV, and ensure the Plex app is updated to the latest version available for your platform.

Related Articles