MyPlex: Couldn't get list of access tokens from myPlex

@ChuckPa Thanks for the quick attention! When I sent the last logs I had removed the config dir and let run for 2 min uninterrupted (checked the docker logs) before stopping the container and taring the Logs dir, I didn’t manually disable the database
OK, so this time I deleted the config dir, and actually did a full image removal and repulled. I started the container detached, but followed the logs and still immediately see the Error starting framework core for /usr/lib/plexmediaser.... If I look in Logs/Plex Media Server.log, I see the error in the topic title. If I go to Logs/PMS Plugin Logs/ and each of the named core services is giving this error when I tail the log

  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 429, in open                  
    response = self._open(req, data)                                                                           
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 447, in _open                 
    '_open', req)                                                                                              
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 407, in _call_chain           
    result = func(*args)                                                                                       
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 1228, in http_open            
    return self.do_open(httplib.HTTPConnection, req)                                                           
  File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 1198, in do_open              
    raise URLError(err)                                                                                        
URLError: <urlopen error [Errno 111] Connection refused>

I can see you’ve personally dealt with this before, and I’m reading through to see if you’ve already solved this - thanks for the help; past and present!

And here are the updated logs from about 10 mins Logs.2.tar.gz (58.0 KB)

For context since I think this is likely network related; I am running container in docker bridge network so it is connected to my reverse proxy (nginx proxy manager)