Plex Server Not Found? Start With These Official Fixes Before Touching Your Database

Plex troubleshooting gets dangerous fast because a five-minute connection problem can send you into a forum thread telling you to delete a database, open ports, or weaken security.

So this is the reset: no invented test results, no “worked 80% of the time” numbers, and no pretending one person’s network setup is everybody’s network setup. These are the steps Plex itself currently recommends.

What should you check first when Plex says “Server Not Found”?

1. Check Plex’s status page. If Plex is reporting a service problem, do not start changing your router.
2. Confirm Plex Media Server is actually running. Plex lists this as a basic first check.
3. Update Plex Media Server and the player app. Plex recommends running a current server version.
4. Confirm the server and app are signed in. They need to be connected to the correct Plex account.
5. Temporarily rule out a VPN or proxy. Plex says both can interfere with connection information.

Plex keeps those basics together in its official guide, Why can’t the Plex app find or connect to my Plex Media Server?

How do you troubleshoot Plex Remote Access?

Open Plex Web App and go to Settings → Server → Remote Access. Plex says automatic configuration works best when the router supports UPnP or NAT-PMP. If automatic setup fails, the next checks are router support, firewall rules, double NAT, and—in advanced setups—a correctly configured manual port forward.

The important part is that a manual port forward is not just “pick a port and hope.” Plex says the external port must forward to internal port 32400 for the server’s local IP address, and the same external port must be entered in Plex with Manually specify public port enabled.

Use Plex’s Remote Access troubleshooting guide for the exact sequence. Router menus vary, so Plex also recommends using the router manufacturer’s instructions.

Should you disable secure connections in Plex?

No—not as a general fix. Plex says the default server setting is Preferred. That uses a secure connection when one is available and allows an insecure connection only when secure transport is not possible.

Plex also warns that setting secure connections to Disabled can prevent modern apps from connecting. If you are troubleshooting an older app, confirm whether that app supports secure connections and keep the server at Preferred unless Plex’s documentation for your exact setup says otherwise.

See Plex’s official secure server connections guide.

Should you delete the Plex database?

Not for an ordinary connection problem. Deleting the main database gives you a nearly fresh server install. Plex says you will lose your libraries and need to recreate them, even though your media files themselves are not deleted.

If you have evidence of database corruption, Plex’s supported process starts with stopping the server and making a backup copy. Plex Media Server includes a customized SQLite tool, and Plex specifically says the standard SQLite interpreter cannot perform its repair procedure.

Follow Plex’s database repair instructions for your platform. This is a corruption-recovery job, not step three in a generic “server not found” list.

What order should you try these fixes in?

1. Check Plex status.
2. Confirm the server is running, current, and signed in.
3. Confirm the player app is current and signed into the same account.
4. Temporarily rule out VPN, proxy, firewall, or DNS-rebinding interference.
5. Use Plex’s Remote Access page for outside-the-home failures.
6. Touch the database only when you have a corruption symptom and a backup.

That order is less dramatic than a viral forum fix. It is also much less likely to turn a temporary connection problem into a rebuild.