I use Jumbo Frames on my LACP LAG's of the FreeNAS server and elsewhere in my network. What I was finally able to narrow it down to was this. In the Verbose logging I could see the UPnP NAT trying to register with the firewall and it would seem to register, but the return traffic from Plex to check and make sure it's working would fail and I'd have a half working session. "exception handled: boost: mutex unlock failed in pthread_mutex_unlock: operation not permitted"ĭuring my troubleshooting and looking at the Plex logs I noticed the NAT service seemed to keep getting hung in these weird states where the only fix was to stop all the services and restart them. "error issuing curl_easy_perform(handle): 52" "myplex: published mapping state response was -52" The firewall rules themselves were actually misleading because I was seeing destination networks that actually don't exist in my home network. I enabled UPnP NAT services and those wouldn't work either. I was perplexed because NAT and Firewall rules are concepts I'm very comfortable with and other NAT rules I created were working perfectly fine. After that change I was no longer able to access my Plex server properly from outside my home network. I recently changed my gateway router from an Apple Airport Extreme to instead using a pfSense virtual firewall. I have been running Plex as a plugin on my FreeNAS server for months now without any problems. This is more of a description after the fact, rather than a question.
0 Comments
Leave a Reply. |