I recently had to repair the file system on my unRAID cache drive where I run PMS as a docker after Plex became unavailable. After repair (confirmed by unRAID logs and support), copying Plex appdata back to the cache drive, and getting the docker running again, it was still showing Plex as unavailable though. So thinking that there was maybe a handshake issue w/the security certificate, I removed the server via the Plex web app and then changed my Plex password and added a pin, figuring that once I signed in again with the new password and pin, Plex would show an unclaimed server on the network and allow me to claim it to re-establish the connection. No dice. Now according to the web app the server isn’t just unavailable, it doesn’t even exist anymore, even though clearly it does.
The computer running Plex has no browser. unRAID is a linux based server OS which is meant to be run headless and controlled through a web UI via any other computer on the network. Usually I have 2 ways to access the Plex server from the control computer (a Win10 computestick): either via the Plex web app, or from the docker page in unRAID I can click the web UI which opens Plex via the local IP = http://192.168.1.23:32400/web/index.html. Now though the local IP page comes back “This site can’t be reached” (same for the public IP as well), and as I said from the Plex web app I can login just fine but there’s no server and therefore no way to access Server settings.
If I need to be asking about this on the unRAID forum instead, let me know. I was just hoping there was some route I to access the server settings via the computestick other than the ones I’ve already tried. Thanks.
@ElJimador40 said:
If I need to be asking about this on the unRAID forum instead, let me know. I was just hoping there was some route I to access the server settings via the computestick other than the ones I’ve already tried. Thanks.
Yeah, this is really beyond the scope of most people here and not really a Plex issue
