I have an Asustor AS6602T NAS with the Plex Media Server which has worked great for a while with a Nvidia Shield streamer. The other day I upgraded to a faster Asustor AS6804T NAS. I installed Plex Media Server on it and it loaded fine, then spent a few days loading my movies and TV shows into it. However, now the server refuses to load. I uninstalled and reinstalled it but I keep getting the same error. My other NAS can still load Media Server but this new one refuses to. The error says “This site can’t be reached.” It lists the correct IP address and says refused to connect. it says try checking the connection and check the proxy and firewall. The connection is good, I can see the NAS fine from my computer (iMac) and can launch my NAS’s Control Center and can see the Plex Media Server just fine. But when I launch the Media Server I get the same error, even with the firewall disengaged. It makes no sense. Does anyone know what might be wrong?
Seriously, if I can’t resolve this, I’ll return this very expensive Asustor NAS to Amazon.
Hold on, that’s the IP address of my older NAS, the good one, the one where my other Plex Media Server is still running. Let me look again for the correct log files from 192.168.0.15.
I am getting exactly the same thing on my QNAP QTS 5.2.7.3297. It happened a few days ago, without any noticeable (by me) change to server, router, network. I can access Plex but I cannot access PMS (“This site cannot be reached” on 192.168.0.30:32400). Plex cannot see my server. I am “running” PMS 1.42.2. I can access, manage and play all my content via File Station 5 within the QNAP QTS interface. This is doing my head in! it happened a couple of days ago now, long after I upgraded my router many months ago. I have over 12,000 films and I don’t want to all the custom art work and metadata. I back up daily and have rolled back and forward with different versions of PMS via the QNAP AppCenter.
HELP! I am a daily Plex user but cannot for some bizarre reason.
Jonathan
Edit:
PS According to yougetsignal.com, port 32400 is closed (not by me). I have set up port forwarding instructions on my router (never needed to do that before) to no avail. I have very recently started experimenting with Torrenting - could it be that my ISP (Virgin Media in the UK) have closed some/all my ports having detected my recent Torrenting activity? Happy to speak to them if so and get this resolved asap. I’d rather Plex than Torrent!
PPS And I’ve researched the heck out of this for two days now!
@ActorCam take a look at Nov 14, 2025 14:46:12: Failed to initialize logging: Error parsing file at "/volume1/Plex/Library/Plex Media Server/Preferences.xml" Looks like you may have a malformed or if cloning the old server to new hardware, have bad permissions on your Preferences.xml
@jmaas28 Please create a new thread just for your issue, and post a copy of your server logs.
Thanks. I tried that but I still can’t start the Plex Media Server. When I try I also don’t get a new instance of Preferences.xml in that folder.
What if I uninstalled Media Server again, fully deleted the folder and all files, and tried reinstalling again? I never had it fully running on this NAS yet anyway.
I uninstalled the Plex Media Server from my NAS and, to be safe, deleted its folders with the exception of my Movies and TV folders which I have under Plex/Library/Movies and Plex/Library/TV. I re-installed Plex Media Server and when I launched it, I got the same connection error. A moment later I got a new error message window with some HTML text:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
Response code=“503” title=“Maintenance” status=“Plex Media Server is currently running database migrations.”/
Now, every time I try to launch Plex Media Server, all I get is this new error window.
