Freenas Plex Jail stops working after upgrade to v1.9.2.4285

The new Plex version 1.9.2.4285 for Freenas was released recently and as usual I upgraded to the latest release. Prior to the upgrade I was running happily and without any problems to multiple clients including android TV’s, smartphones and in my browsers. My Plex server runs in a Freenas Jail and this is the only thing this jail does. After the upgrade completed, I logged in plex via my browser and at first it said the plex server was offline, then it said it found it, but with limited access, meaning no remote access and only on my local network. I have one remote user so I went into the server config for remote settings. I could see an internal port for 32400 and an external port of 18363 that it had previously selected via UPnP. Looking at the router, I can see the UPnP config for that port so it should be working. I set it to manual and retried on a new port, 18400, but that gave me the same problem for a few minutes, until the plex site just lost all connection to my server.

Now the server is gone and have no access to the settings via the browser. Trying to connect to the local IP address and the default port 32400 fails with refused connections. At this time, I seem to only have command line access to the Plex Jail. I my hunt for a clue to what happened, I finally found the logs in a folder /var/db/plexdata/Plex Media Server/Logs. Looking at the “Plex Media Server.#.log” files, I see tons of errors and timeouts, but they don’t seem related to connections to plex.tv system. I’ve hardcoded a port forward of 32400 internal and external into the router and also left the 18400 and 18363 ports pointing to the plex IP. Still no server in the plex.tv connections. After about 2 hours of trying various ports and reading forums, I thought to disconnect the server from plex.tv to allow it to re-discover it, but it’s still trying to find the server. Any idea’s or advice would be appreciated.

UPDATE: I was able to recover by reverting back to a previous snapshot.

I am doing Jails on FreeNAS and have not had any issues.

@chapindad said:
I am doing Jails on FreeNAS and have not had any issues.

If you would have asked me 5 days ago, I would have said the same thing. It doesn’t make much sense and Plex doesn’t seem to have any good command line tools to diagnose when the browser becomes unavailable.

@trdemoss said:

@chapindad said:
I am doing Jails on FreeNAS and have not had any issues.

If you would have asked me 5 days ago, I would have said the same thing. It doesn’t make much sense and Plex doesn’t seem to have any good command line tools to diagnose when the browser becomes unavailable.

Okay. I just ran into the issue. All of sudden my web interface became unavailable locally. I could access remotely but not on the local network and none of my videos would play so something went seriously wrong. I had to delete the Jail and reload from scratch twice to get things back running. So something is very wrong in this release. The only thing I did before it broke was enable remote access to my server. I have to wonder if something was trying to hack my server.

I had a snapshot of my plex jail so I rolled it back, but it still didn’t behave properly in that I could see the metadata in the web browser, but no video’s or music could play. I was able to download the logs and I could see the transcoder crashing after each time I accessed the media. I looked at the mount points to see if they were there and if I could access the media and it was all there and good. I could go directly to the files I tried to play and play them locally from the SMB share. Plex was just broke in all kinds of ways. I do have all the logs if anyone is interested in looking at them.

Bottom line is that I had to delete the plex jail and rebuild it from scratch myself. This time I did not use the plugin and built the jail, then installed plex on top of that. So far everything is working and behaving correctly at the 1.9.2.4285 version.