Hey folks,

I’ve been trying to get AdGuard running on my server, and in the process, I started tweaking Docker and network settings—mostly around DNS. Unfortunately, I seem to have broken something critical, and now I can't connect to my server via its old local IP.

After hours of troubleshooting, I'm still stuck and not sure which change caused the issue. The server no longer appears in my router’s list of connected devices, and during boot it reports: “IPv4 Address is Not Set.” I've tried deleting the network.cfg file and rebooting, it generates a new cfg but doesn't seem to solve the problem.

Here’s my current network.cfg (copied from the boot USB):

# Generated settings:

IFNAME[0]="br0"

DHCP_KEEPRESOLV="no"

DHCP6_KEEPRESOLV="yes"

BONDNAME[0]="bond0"

BONDNICS[0]="eth0 eth1 eth2 eth3"

BONDING_MODE[0]="1"

BONDING_MIIMON[0]="100"

BRNAME[0]="br0"

BRNICS[0]="bond0"

BRSTP[0]="no"

BRFD[0]="0"

PROTOCOL[0]="ipv4"

USE_DHCP[0]="yes"

USE_DHCP6[0]=""

SYSNICS="1"

Any ideas on what might be causing the IPv4 issue or how to restore connectivity? I'm open to resetting things if needed—just want to get back up and running.

Thanks in advance!

Let me know if you want to add system specs, Docker container details, or router model—those might help others troubleshoot more effectively.

10 hours ago, PaulArmstrong said:

“IPv4 Address is Not Set.”

The config look like noraml, pls ensure Ethernet link was up ( check the LED ) or boot in safe mode and provide the diagnostic.