It is installed on FreeNAS jail. Server Version is 1.15.4.919.
It’s very weird, but I think it is something to do with vnet.
Basically, on wireless, on any device on any app/browser, my Plex Server is unreachable no matter what.
But all devices that are connected via ethernet cables can. Of course, both wireless and ethernet have same subnet so that is not a problem.
One thing I noticed is that if I disable vnet and configure the jail to use non-vnet environment, then I can access from wireless devices. Of course, the problem is that plex needs vnet to work properly.
I have no idea to where to start troubleshooting this issue. Any ideas? I see there is a thread back in 2017 with exact same issue, but it simply does not help at all.
I don’t have any experience with FreeNas but are you saying you can’t reach your server settings or can’t play any media while the issue occurs? Do you have static ip and port forwarding set?
Now, I think I omitted some info. I had a fully functional FreeNAS box with Plex, but I later decided to add an Intel NIC because I suspected the motherboard’s non-Intel NIC seemed to wave white flag when it is loaded too much work. And then this whole mess started.
I tried everything, cleaning out iocage to complete reinstallation of FreeNAS but it seems they are not going to play nice.
I did get a connection when I try connect Plex via mobile web browser with secure connection disabled, but the app still refused to connect.
TBH it is too much headache for me so I just removed Intel NIC and went back to onboard gigabit NIC. Now everything is back to normal now.
Something tells me FreeNAS + Plex does not play nice with multiple ethernet ports available due to the nature of vnet and its… well, quite bugginess when things are not going nice.
Given the fact how hard getting an attention to problems from FreeNAS community in general and from my experience, it is not worth to pursue a troubleshooter so I am leaving this problem as is.
But hopefully this info may helps someone else in future.
Yes, thus I edited my router PC’s static mapping with new MAC for Intel NIC. But due to nature of FreeNAS (which is FreeBSD) jail, once set, the ip address of the jail does not change. So even the ip address of FreeNAS changes and loses static mapping, the static mapping of Plex stays same thus obtaining same ip. This is one of the strength of BSD jail system, a bit similar to Docker.
Of course, disadvantage is that it is complex and can be buggy, like my current situation.
It seems certificate file is very sensitive to NIC changes, thus making certain connections unreachable when it is using secure connection.
Nuking certificate files on Plex Media Server/Cache solved this problem completely, forcing the server to recreate the certificate files for new hardware.
