FreeNAS fails to launch plugins during installation.
FreeNAS fails to launch plugins during installation.
Yesterday experienced a short network disruption in my area. After restarting the modem/router, the internet reconnected within 5 to 10 minutes. However, upon rebooting the router, I lost access to my FreeNAS shares via Windows. It seems the issue was likely related to incorrect credentials or settings. To resolve this, I rebooted the FreeNAS machine. There was also a problem where the boot drive wasn’t listed in the BIOS, so I temporarily moved the flash drive to another USB port, which allowed the system to recognize it again. After rebooting, the FreeNAS IP address changed from 192.168.20.6 to 192.168.20.8—this was normal since IP changes after reboots are common. I was able to access the shares through Windows, but now the Plex plugin won’t start. When launching it, it displays an error saying "Some error occurred." I suspect the problem lies with the jail configuration, specifically the Plexmediaserver_1 service, which can no longer connect using the old IP (192.168.20.2). I’m able to ping google.com from the root shell, but failing for other sites inside the jail. The modem’s IP is 192.168.20.1, which serves as the default gateway in FreeNAS settings. Interestingly, the MAC address appears missing from the jail—this might be the cause of the plugin failure. If you’re new to this, consider verifying the jail’s configuration and ensuring the correct IP is assigned to Plexmediaserver_1.
Attempted to simply select IPv4 DHCP and restart; it appears the gateway configuration isn't loading. The MAC address section might be the place to manually enter a static MAC address.
I've attempted DHCP settings but it keeps giving the same IP address and no link exists. After rebooting the whole FreeNAS system, the issue persisted. Once I isolated just the jail, it assigned a new IP (192.168.20.10) and resolved connectivity—pinging Google and Plex worked fine. Thanks for your assistance!