eafx

Updated fine from 6.8.0-RC3 but the array status in the footer is stuck at the following message But the array has already started, I can access all disks (read/write), docker containers are up & running. It's already over 20mins now and the status still hasn't changed. Main tab shows array has started as well. EDIT: The array status in the footer has changed to 'started' now, after almost an hour. titan-diagnostics-20191024-1021.zip

Here ya go mate: https://github.com/elmerfdz/UnRAIDscripts Let me know if the instructions aren't clear or if you have any issues.

Any containers relying on the VPN container will have to be removed & re-created when the container updates or when it's recreated, it's more of a docker issue than Unraid, as docker expands the value of --net=container:nordvpn to container ID even if you specify the container name, which is really annoying. So I've written a script that runs every 5mins using the 'user scripts' plugin, which checks if the VPN container ID has changed, if the containers are still using the current VPN container ID, adds containers using the VPN network to it's watch list and removes/recreates when required.

Got back into the GUI by linking local addresses, disabled/enabled bonding and added eth0, eth1, eth2, eth3 back in, that seems to have done the trick. Done couple of reboots since, also updated back to 6.8.0-rc3 & done 2 reboots post that and everything is still working fine. Going to leave my logs up, hopefully you can find the root cause.

Any steps on how you managed to resolve this?

Think I'm having the same issue, updated to the latest beta from 6.8.0-rc1 almost 17hrs back and had no issues after the initial reboot, tried rebooting the server few mins back and now can't back into the GUI, not getting a ping back, I can log into the terminal via ipmi but the IPv4 address has changed to 169.254.xxx.xx range, sounds like the exact issue described here. Tried manually copying over the bz files from /boot/previous folder but it's still the same. titan-diagnostics-20191019-0115.zip

I had the same issue, was able to get around that by creating a docker network named container:vpn_container_name On your terminal run the following command docker network create container:nordvpn Doing the above you don't need --net=container:nordvpn in extra parameters, just select the newly created network from the 'network type' dropdown and it will basically run the same parameter as --net=container:nordvpn

Did you find a solution to this issue? I'm seeing the same issue in the last 2 weeks.

Yea looks like, I've rolled back to 1.1.r38.gd52abd2-1-05, the last working version with Cloudflare.

I'm having the exact same issue, since yesterday, it was running fine for over a year now without any issues 😐 Edit 1: Do you use Cloudflare? I just turned off orange cloud on my rutorrent subdomain and it's working now, hmm..

Is your VM name and the vDisk location folder name the same? if not, you either change that to match or switch from auto to manual, if you decide to switch to manual, you'll have to do that every time you do a change.

Think the command text below should be white (black theme).