Updating Plex Media Server Plugin from FreeNAS 11.2-RELEASE to 11.3-RELEASE

 Plex failed to update when I upgrade FreeNAS from 11.2-RELEASE to 11.3-RELEASE. After some Web searches, I found the solution given in this post worked. For convenience, I copied the solution to this post in the following,

1. Stop the plex jail
2. Log on to a FreeNAS shell, and renamed the jail
   

   
       iocage rename plex plexmediaserver
       

3. From the FreeNAS shell, go into /mnt/__YOUR_STORAGE__/iocage/jails/plexmediaserver/ and renam plex.json to plexmediaserver.json,
   

   
       mv plex.json plexmediaserver.json
       

4. Open config.json in the same directory and change the plugin name from plex to plexmediaserver
5. Start the jail again. Everything still worked and both jail and plugin now displayed as plexmediaserver
6. Run the following command to upgrade the jail and the plex plugin
   

   
       iocage upgrade plexmediaserver -r 11.3-RELEASE
       

Which ISP's routers support hairpinning (NAT loopback)?

NAT loopback, also known as hairpinning is that two hosts on the LAN behind the NAT gateway can communicate with each other via the NAT gateway's external address. Which ISP's router out of the box supports NAT loopback? Based on experience thus far in October, 2020, my experience is as follows,

• Optimum. Yes
• Verizon Fios. Yes
• Spectrum. No
  

Configuring Windows Dynamic Port Allocation?

Some Windows applications can reserve TCP or UDP ports which may cause some other applications fail to run. These threads provide solutions to this problem,

• Reserving ports in the Windows 10 Dynamic Port Range  on Superuser.com
• Solution for common Docker not starting problem after latest update
• Cannot bind to some ports due to permission denied on StackOverflow.com 

The solution are generally three.

1. Removing/disabling the offending application or Windows feature. For instance, the threads point out Hyper-V is often the culprit because it reserves ports dynamically and unpredictably. We can disable it if we aren't using it,

   
   REM disable Hyper-V
   dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
     

   In PowerShell, do this to remove all Hyper-V adapters,

   
   Get-HNSNetwork | Remove-HNSNetwork
     

2. Reset dynamic port range from which the offending application reserves ports. For instance, for Hyper-V, for instance, we can do this,

   
   dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
   
   netsh int ipv4 add excludedportrange protocol=tcp startport=50051 numberofports=1
   
   dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
       

3. Disable dynamic port allocation, i.e.,

   
   reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f