Can't connect to the Plex NAS server even if the server found is the same I connect to!

Plex Media Server NAS & Devices
1

Ok, this is driving me absolutely nuts!!! I had issues with DB corruption but managed to seemingly solve them. Now, here’s the kicker…

My Plex server name is “PLEX MAISON”. So about once each week or two, I Iog in for the first time of the day (my NAS shuts down each night and wakes up in the morning) and Plex goes into configuration mode as if it’s a new server. I’ve said several times, ok, let’s reconfigure just in case. I give the same Plex name, etc.

When I login, there are TWO servers with the SAME name. One is the old one which it can’t connect to and the other one is the new one with the content accessible.

What the hell is going on??? Plex knows there’s another server named TNAS MAISON that it can’t connect to but a new one name TNAS MAISON works?? Even worse, I’ve had times that the next day, I try to reconnect and now it needs the old server which it couldn’t connect to yesterday and can’t understand the new one I configured the last day.

Before I throw in my logs, some basic info:

  • I don’t use a VPN although I sometimes use one but it’s almost always off when connecting to Plex.
  • Tried in Firefox and Chrome on my PC, same thing
  • No LAN IP change anywhere
  • Secure connections are recommended, not required

Any one else have this? Reconfiguring is easy: the thing that makes me want to hit my head on the wall is reconfiguring every time all Pinned for me and my 2 managed accounts, regiving access to certain librairies for the 2 managed accounts, reconfiguring all my Android devices and TVs (which never goes smoothly btw). Thanks for any help. I’ll try joining my logs from today…

p.s.: is there a way to upload a log file? Can’t seem to find an attach link…

2

I have no experience with Terramaster NAS devices whatsoever, so all I can offer is a hunch:

Apparently, the shutdown might be either performed in a very rude manner (i.e. not notifying any running apps on the NAS at all about the impending shutdown), or at least without giving the apps enough time to shutdown cleanly. This can result in the main Plex server configuration file Preferences.xml getting corrupted.
Upon next bootup, this file will then either be absent, or appear as being completely empty.
If Plex senses this situation, it will assume it hasn’t been configured yet and will start the setup wizard again.

See if the whole messup is avoided if you no longer shutdown the NAS at night anymore.

3

Thanks for the reply! Well, I think you have something there… I had it in the back of my mind too. I used to shutdown from 2 AM to 8 AM each night with maintenance tasks done from 11 PM to 2 AM. That’s when I had DB problems with corruption, Plex not being able to shutdown normally. Since I changed the maintenance tasks to end by 1 AM, I don’t have any DB corruption anymore. So it may effectively be something like that for the preference file.

I used to have tons of [conflicted] DB files before but now I see I have [conflicted] preferences.xml files now… Thanks for the suggestion, I think we might have a solution here. :slight_smile: