Another one, I know.
I spent hours reading all the possible posts related to this topic and trying different things.
I’m running the latest version of Plex for Linux on docker, on a Linux server (Ubuntu 24.4 LTS)
Note that the server did run happily WITHOUT problems until I did change the password as suggested by Plex.
I did obtain a new claim, update the docker compose file with the new claim, erased container and images and rebuilt everythng from scratch.
I did remove all the registered servers from my Plex account, started the container, no problem, logged in locally (http://localIpServer:32400/) logged in to my Plex account from there and … nothing.
My server is not there, my content is not there.
Any idea other the ones I already found on the forum ?
Very very very disappointing and frustrating.
I have same issue, i can see my folders going local on my computer running windows but when i go to android tv i cant access the folders they will not load.. i dont understand whats wrong.
I am getting this same error. Running on a dockerized linux container. After resetting my password as instructed, I can no longer see my libraries, either in a browser, iOS client, or Roku. I was able to log back in (this was expected after the password change) but it just can’t see my libraries. I re-read over the security email to see if this is expected behavior but there’s nothing in there about that.
I figured it out with no help from Plex tech. On a windows computer do the following:
Uninstall plex server. Reboot computer. Edit your registry but first export it so you can restore it if you mess up. Then do a search for “Plex” there will be many that are immaterial and unrelated. You are looking for anything that says “plex server.” Delete all of them. It took me over 2 hours to finally accomplish this. Then reboot and reinstall plex server. Give it a different from the previous installation a friendly name. Give it a little time and it will find all of your local content. Next go to the settings (wrench) and find the name of the previous server and delete it. You should see your new server with all of your content. If you want you can rename it to the old name. Next check out remote access (in my case the plex photo app on my iphone and log in with your new password. I hope this helps. No claim code was needed
having the same issue “No servers found“ android plexamp/android plexdash & web.
This is very frustrating !!
stop / start plex on NAS QNAP several times & rebooted my NAS several time all with no joy. This happened when I decided to react to the message of changing password (also at the same time created 2FA authentication).
Yeah is what I did.
I obtained a new claim code, I stopped the container, modified the docker compose file adding the new claim and restarted the server. Nothing.
There is some specific sequence to do ?
And when I run the server locally, I can’t even see my content, meaning nothing, not even the categories.
Before the claim I did see the categories, blocked but they were there !
Now nothing and the files are there, did check.
Very very very frustrating.
Thanks for the answer.
The main reason why I choose docker was EXACTLY to avoid to mess with my server in case something changed.
I rebuilt the container from scratch in order to use the latest image and deleting the old container did delete all the settings of the old server.
I need to find a way to make the new server visible, I’ll try again with a new claim code.
I found some time and started to take a look of the plex server log on the docker container.
Usual list of connection errors (since the server was not claimed) but then I noticed a strange error in a log :
So I edited the preference.xml file and there it was :
allowedNetworks=“192.168.2.*”
I changed it with : allowedNetworks=“192.168.2.0/24”
restarted the plex (on docker just docker restart ) and the server finally started for real !
I saw all my material back but was marked not accessible because not claimed.
So, this time did appear the claim button, hit it and voila’, my server was back to life !!!
Now, who the heck changed that ?
Maybe older versions of the server used xxx.xxx.xxx.* for the allowedNetwork and the new one changed format to full CIDR ??
Anyway, if your server on docker is not working properly AND you just updated to the latest version, go on the volume where the config is present, look for the file Preferences.xml and verify that the field allowedNetworks contains a full CIDR URI : xxx.xxx.xxx.0/24
Having the same issue on ASUSTOR with latest release (not Beta). Tried at least a dozen times with new claim codes on the Preferences.xml and full server restarts, aiming to keep time from claim code generation to server attempting to use it to less than 90 seconds. Logs are throwing 401 errors:
╰─ tail -f -n 100 “Plex Media Server.log” ─╯
Sep 09, 2025 20:44:15.658 [140341608958776] INFO - Plex Media Server v1.42.1.10060-4e8b05daf - ASUSTOR AS5304T x86_64 - build: linux-x86_64 asustor - GMT -04:00
Sep 09, 2025 20:44:15.659 [140341608958776] INFO - Linux version: ADM 5.0.1.RKD2, language: en-US
Sep 09, 2025 20:44:15.659 [140341608958776] INFO - Processor: 4-core Intel(R) Celeron(R) J4125 CPU @ 2.00GHz
Sep 09, 2025 20:44:15.659 [140341608958776] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Sep 09, 2025 20:44:15.659 [140341608958776] INFO - /usr/local/AppCentral/plexmediaserver/Plex Media Server
Sep 09, 2025 20:44:15.668 [140341665979024] INFO - SQLITE3:0x80000001, 283, recovered 58 frames from WAL file /volume1/Plex/Library/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal
Sep 09, 2025 20:44:15.768 [140341665979024] INFO - Running migrations. (EPG 0)
Sep 09, 2025 20:44:16.161 [140341665979024] INFO - Running migrations. (EPG 0)
Sep 09, 2025 20:44:16.167 [140341604739896] INFO - Preemptively preparing driver ivd for GPU Intel GeminiLake [UHD Graphics 600]
Sep 09, 2025 20:44:16.167 [140341604739896] INFO - Preemptively preparing driver icr for GPU Intel GeminiLake [UHD Graphics 600]
Sep 09, 2025 20:44:16.177 [140341665979024] INFO - Killing process: Plex Plug-in [com.plexapp.system] (pid: 6600)
Sep 09, 2025 20:44:16.696 [140341554916152] ERROR - MyPlex: Error 401 requesting XML from: https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxxTDnshE
Sep 09, 2025 20:44:16.696 [140341554916152] WARN - MyPlex: Token was invalid, resetting security.
Sep 09, 2025 20:44:17.005 [140341554916152] WARN - [AutoUpdateRequestHandler] Couldn’t get update channels. Trying again soon.
Sep 09, 2025 20:44:17.311 [140341552806712] WARN - MyPlex: Token was invalid, resetting security.
Sep 09, 2025 20:44:17.657 [140341569940280] WARN - Crash: Crash reporting disabled
Sep 09, 2025 20:44:18.921 [140341559184184] INFO - Refreshing paths watched by LibraryUpdateManager
Sep 09, 2025 20:44:19.838 [140341546478392] ERROR - [MediaProviderManager/Response::fetch] failed to complete query (401)
After some time it activated and got my server back again. Wow, this was painful. Nothing I could do via the Preferences.xml worked… and yes, all processes were stopped etc.
