November 30, 20169 yr I finally took a minute this weekend to upgrade from 6.1.9 to 6.2.4. Overall it went smoothly, however, my network broke. Eventually I stumbled upon the articles that said to delete the old network.cfg files and then just configure things manually in the GUI. So I did. I have dual onboard NIC and a 2 port NIC that I passthrough for pfsense. So, I did the following: eth0: bonding: yes mode: active-backup members: eth0, eth1 bridging: yes IP: static MTU: blank (default) VLANs: no eth1: IP:none it is actually unplugged at the moment. However this was the only way to get network support. Regardless, 90% of everything is up and working, except 2 docker containers using host network type. openvpn-as: container is up, but I cannot access the webUI. plex: I can access plex webUI, but it tells me my connection is indirect to the server. I am of the assumption that something with the new networking is messing things up, but specifically, I do not know what. Other docker containers with a webUI function fine. I have restarted the containers, deleted and put them back etc, but nothing seems to resolve the issue. The only thing I have not done is, disable docker and put it back, rebuilding everything.
November 30, 20169 yr Community Expert At the command prompt (connect up a monitor and keyboard), enter diagnostics and that will save the diagnostics file to your Flash Drive. (It will be either in the root or the logs folder.) Attach that file to your next post.
December 14, 20169 yr Author ended up removing the network bond I had and then everything started to work normally again.
Archived
This topic is now archived and is closed to further replies.