Moose808

I'm baaaa-aaaack! I took a look at this doc, and decided my setup really was an invalid configuration. Since I wasn't using bonding to combine the NICs, the 2 NICs on one LAN can cause conflicts. https://www.ni.com/en-us/support/documentation/supplemental/11/best-practices-for-using-multiple-network-interfaces--nics--with.html#section--1358462000 So, I: 1. Shutdown my one VM that was running (VMs) 2. Shutdown the VM manager (Settings) 3. Shutdown the Docker Manager (Settings) 4. Changed the eth1 NIC settings (Settings -> Network Settings) "Downed" the eth1 port in the settings Changed the 10.0.1.216 NIC IPV4 address to 192.168.0.215 to match the eth0 node (.215) Changed the Default Gateway to blank (0.0.0.0) so only one default GW exists on the server using the 10.0.1.x LAN 5. Restarted the VM Manager (Settings) 6. Restarted Docker Manager (Settings) 7. Restarted my VM (VMs) Then I reran the Fix Common Problems Plug-In. The error no longer appears. Hope that helps.

I've been using the same on-board NIC plus an add-on 4-interface NIC for many months on unRaid. I've also been running Fix Common Problems since creating the server. Only today did I start getting the "rarely a valid configuration" message. Only eth0 (on-board) and eth1 (add-on 1st port) NICs are active. Both have been on the same IP LAN for the whole time to provide remote access capability if the primary port dies. My guess is the Fix Common Problems Plug-In changed recently and is now complaining about something it ignored before. I'll be looking for more info. In the meantime, I'll just click "ignore" in the FCP Plug-In. If you server's network interfaces are working fine, I wouldn't make changes. If you do, backup your server's boot USB drive to another USB drive first just in case.