Thomas T

RESOLVED settings # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="no" DHCP6_KEEPRESOLV="yes" BRNAME[0]="br0" BRNICS[0]="eth0" BRSTP[0]="0" BRFD[0]="0" DESCRIPTION[0]="Unraid" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" USE_DHCP6[0]="no" IFNAME[1]="eth1" PROTOCOL[1]="ipv4" USE_GW4[1]="on" SYSNICS="2"

Fixed. disabling VFIO allowed me back into my own system -_-. anyways, once that was taken care of i was able to shuffle the network cfgs around enough to get things working properly. One of my main issues is that by default eth0 is a the motherboard network driver and right now that is corrupted on my MB. I have a Nic PCIE card that i use for connecting. Once im able to get that worked out. I'm A-Okay

I did disabled my VM but im wondering if the VFIO is causing issues. i have disabled them by renaming them. i also downloaded the latest boot drive and im using the default network config USE_DHCP="yes" IPADDR= NETMASK= GATEWAY= BONDING="no" BRIDGING="yes"

I pulled my USB out and looked at the /config/network.cfg # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="yes" BRFD[0]="0" DHCP_KEEPRESOLV="no" DHCP6_KEEPRESOLV="no" DESCRIPTION[0]="Unraid" BONDING_MODE[0]="1" BONDNICS[0]="eth0" BRNICS[0]="bond0" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" USE_DHCP6[0]="yes" SYSNICS="1" noting that bonding is what causes this issue in the first place, i decided to remove it all IFNAME[0]="br0" BRNAME[0]="br0" BRNICS[0]="eth0" USE_DHCP[0]="yes" PROTOCOL[0]="ipv4" SYSNICS="1" but i have been unable to get it working. I get through the mount: overlay mounted on /lib _ Then freeze or at least stop displaying. I cannot hit this through ssh or through the GUI

Unraid Service is hooked up to monitor Custom port for unraid access at {{IP}}:8443 When trying to work on my VM i was unable to access the internet. Read an article that said to use bonding. Went to network to switch to bonding on. Now nothing freaking works on this machine. I cannot navigate to the server via IP. Trying to use the UI on the Monitor by selection the Unraid GUI on startup is not working either. im at a loss here on what to do

Setup and information: 1. Using a raspberry pie locally. I have my router pointing to it to resolve dns and local dns records 2. Recently switched from ISP router hardware to TP-LINK. a. Setup VPN on TP-Link using wireguard configurations. In turn, i turned them off on the server. b. I have reason to believe that TP-LINK might be stopping rebinding. I do not see an option to turn it off either c. I went ahead and port forward connections that i needed to my server IP. IE: 81 and 444 are forwarded and handled by Nginx Reverse Proxy d. Ports for unraid connection for FQDN have been forwarded as well. e. Ports for standard, non-FQDN have been forwarded as well. i. Note that i do not use standard ports. 3. I have to turn of strict on management access. Setting it to yes at least allows me to VPN into the router and access the server from there. 4. I just noticed that when turning on Dynamic Remote Access I can no longer turn it off... weird. 5. Lastly, on Unraid Connect, it does seem like I am getting info from my router. I do hope i did this diagnostic stuff right. I pray im not releasing a bunch of info... The guide I followed: https://docs.unraid.net/connect/remote-access/ tower-diagnostics-20250724-2005.zip Update: a partial resolution for fully qualified domain name on land was resembled by reinstalling unraid connect. I found this out by tracking the system logs and seeing that there is an issue with nginx communication. When verifying the validity of nginx, I found that there is a malformation in the config file. Since then I have went ahead and forced nginx to do a update via terminal commands. I have forgotten what terminal commands those are but it has put itself in a state in which it is wrong again and well formed. But at least I have lan fully qualified domain happening so that my certs are good and I don't have navigate to a "unsaved site". Update 2: I learned that unraid connect is adding duplicate records to my nginx. /etc/nginx/conf.d. It is only by deleting those files and reinstalling it does it seem to half fix itself. Once i try connecting from outside WAN. those files are duplicated causing nginx to start throwing errors for duplicate records in the sys log. This seems to potentially be a bug with the app itself. im wondering if reverting a version will resolve this