hi all

After update from 7.1.2 to 7.1.3, no more GUI and network connection possible on unraid. Start Docker and have access.

Can someone please help me?

Thanks

Attach Diagnostics ZIP to your NEXT post in this thread.

I just ran into a similar problem today after upgrading to 7.1.3 - Fun thing I noticed was that the VM's I have sharing the primary adapter were working fine, but no ping response or ssh on the servers static IP. I threw the problem at Perplexity and got this response which got me up and running, just had to pull the USB and modify /boot/config/go on another system-

Network Configuration Issues

br0 Interface Instability

The main interface (br0) losing connectivity after a few minutes while VMs remain active aligns with a known issue in Unraid 7.1.3 where the br0-shim interface isn't consistently created. This was partially addressed in the 7.1.3 update but might require manual intervention. Add these commands to your /boot/config/go file for persistence across reboots:

bash

ip link add shim0 link br0 type ipvlan mode l2

ip addr add 192.168.50.11/24 dev shim0 # Match br0 IP

ip link set shim0 up

I upgraded 2 of my 3 servers yesterday. One went fine, the other hung on the reboot and I had to hard power down. It ended up booting fine, just like the other one. Thirty hours or so later and now I can't access the gui on either of them (worked fine as recently as this mornig). Seems the VM and containers are still running, but man this is not good.

I changed it that way without success.

I changed the GO into directory

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp

bash

ip link add shim0 link br0 type ipvlan mode l2

ip addr add 192.168.1.254/24 dev shim0

ip link set shim0 up

tower-diagnostics-20250605-2015.zip

Edited June 6, 20251 yr by Over73

One of these two, the very simple one with a single interface running a single VM and a handful of containers, has a br0 interface. The much more complex one with several interfaces and disks does not. I ended up reverting both back to 7.12. The latter required another hard power off to complete the process.

How did you make downgrade, have the system running for a long time but have been running for a long time. For 3 years I didn't have to downgrade nothing losing I have important data on it. Do you have a link with description thank you

Click Tools - Downgrade OS then you should see the option to downgrade:

Unfortunately I don't have a gui so I can't get there

2 minutes ago, Over73 said:

Unfortunately I don't have a gui so I can't get there

There's a way to overwrite certain files on the flash drive with files from a downloaded and extracted 7.1.2 image, but I'd consider that last resort. Easier would be to reboot your server and on the local keyboard and display of the server itself choose to boot to GUI mode. That should work to make the change.

Next problem if I want to boot gui fashion stays black after the boat. How can I make a downgrade on the USB stick? Thanks

33 minutes ago, Over73 said:

Next problem if I want to boot gui fashion stays black after the boat. How can I make a downgrade on the USB stick? Thanks

https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade

Pay VERY close atttention to the steps, especially these:

• Move (not copy) bz* and changes.txt from the root of the flash drive to the previous directory, overwriting files as needed

• Copy bz* and changes.txt from the unzipped file to the root of the flash drive

I copied too many files over a couple of years back and royally borked my server for a few hours.

Edited June 6, 20251 yr by BurntOC

During my issues one of my troubleshooting steps was to add a USB Ethernet adapter to the system, and configured it's networking options in the network options config file on the USB config/network.cfg (made an educated guess that the next adapter added would be eth4)- I was then able to access the GUI- didn't fix the br0 problem, but did bypass it enough for me to investigate from the GUI.

i also tried the upgrade and lost network connectivity.. spent a few hours trying to get it back online without any luck so im just going to roll back to the previous version i had

I restored unraid 7 using the usb creator and copied the configuration from my backup but I still can't connect for some reason, eth0 doesn't exist which never used to be a problem. I tried restoring a few other backups and the same issue :( any suggestions

@Maximo101

Hi Which files and directory have you copied from the backup to USB? I will also have to do it that way because I don't get over the Gui in any way

I also experienced the same issue: after upgrading from 7.1.2 to 7.1.3 and rebooting, the network connection did not work and the GUI did not appear. When I forced a shutdown and rebooted, the network connection worked normally this time. Will the connection be lost again after some time?

Definitely the most disappointing update quality control in about 2 years. We were on such a good run, too.

I was have issues on 7.1.2. I'd lose gui and also could not ssh in either. Hard shut down and then had to start a parity check. Gui crapped out again during parity check multiple times. Eventually had to safe boot no plugins and was able to complete a successful parity check. I rebooted and immediately updated 7.1.3. Been up for about 36 hours. Knock on wood.

I'm finally back to 7.1.2 I have Gui, for that, Unraid and Docker cannot access it on the Internet, but false bat something with DNS but does not find it. Become warning. I played with it all day today. Referee the click on the update. The landlord still takes days before I get everything in order again.

16 hours ago, Over73 said:

@Maximo101

Hi Which files and directory have you copied from the backup to USB? I will also have to do it that way because I don't get over the Gui in any way

Create a new flash drive using the usb creator, make sure its the same version as your backup. Once that's done copy the entire configuration folder to the usb from your backup.

Mine weirdly still broke my Nic driver which was an annoying issue I had when I upgraded my hardware. I spent hours yesterday with no luck and gonna keep trying to get it back online today.. I wish I had never tried the upgrade and just kept with what was working...

For me the error was in 2 files

ident.cfg

PORT="81" Before update I had PORT="80"

Control the port in ident.cfg

After update 7.1.3 I had

network.cfg

# Generated settings:

IFNAME[0]="eth0"

DHCP_KEEPRESOLV="yes"

DNS_SERVER1="208.67.222.222"

DNS_SERVER2="1.1.1.1"

DNS_SERVER3="8.8.8.8"

DHCP6_KEEPRESOLV="yes"

PROTOCOL[0]="ipv4"

USE_DHCP[0]="no"

IPADDR[0]="192.168.1.254"

NETMASK[0]="255.255.255.0"

GATEWAY[0]="192.168.1.1"

METRIC[0]="3"

USE_DHCP6[0]="no"

IFNAME[1]="eth1"

PROTOCOL[1]="ipv4"

USE_DHCP[1]="no"

IPADDR[1]="192.168.1.252"

NETMASK[1]="255.255.255.0"

VLANS[1]="1"

IFNAME[2]="eth2"

PROTOCOL[2]="ipv4"

USE_DHCP[2]="no"

IPADDR[2]="192.168.1.253"

NETMASK[2]="255.255.255.0"

METRIC[2]="2"

SYSNICS="3"

Now the file looks out now. and everything works network.cfg

# Generated settings:

IFNAME[0]="br0"

DHCP_KEEPRESOLV="yes"

DNS_SERVER1="192.168.1.1"

DHCP6_KEEPRESOLV="no"

BRNAME[0]="br0"

BRNICS[0]="eth0"

BRSTP[0]="no"

BRFD[0]="0"

PROTOCOL[0]="ipv4"

USE_DHCP[0]="no"

IPADDR[0]="192.168.1.254"

NETMASK[0]="255.255.255.0"

GATEWAY[0]="192.168.1.1"

METRIC[0]="1010"

USE_DHCP6[0]="yes"

IFNAME[1]="eth1"

PROTOCOL[1]="ipv4"

USE_DHCP[1]="no"

IPADDR[1]="192.168.1.252"

NETMASK[1]="255.255.255.0"

METRIC[1]="1007"

VLANS[1]="1"

SYSNICS="2"

With this, the 7.1.3 only does not run VM and Docker, but you can then set up in the GUI

network.cfg

# Generated network settings

USE_DHCP="no"

IPADDR="192.168.1.254"

NETMASK="255.255.255.0"

GATEWAY="192.168.1.1"

BONDING="no"

BRIDGING="no"

DNS_SERVER1="192.168.1.1"

I hope it works for others, many thanks for your guys have definitely brought me the important way.

i managed to restore an older backup for mine, had to re black list the r8169 network driver and that allowed the r8125 to work, then restored all my server to the v7.0.0 and im just going to keep it at that.