Can't Check Updates

[TheRedHerring]

I've been running 6.12.6 since shortly after it's release, and made a change to my network configuration to try and get link aggregation working with 802.11ad. The containers, storage, all of that continued operating as normal, but I lost my ability to check for updates to Unraid as a whole, plugins, and the containers I'm running, along with Unraid Connect giving the following error: 

NETWORK: getaddrinfo ENOTFOUND mothership.unraid.netCLOUD: Socket closed

 

My configuration has been reverted back to it's original configuration of single NIC, as I was wondering whether that was part of the issue, but the problem has continued to persist. 

 

Would love some help or even just a point in the right direction to help resolve this, as it's probably been a month at this point and I'd like to at least know whether my stuff is up to date or not. 

[JorgeB]

Diagnostics may help, but I would start by going back to default network settings, you can do that by deleting or renaming /boot/config/network*.* and rebooting.

 

If you have some firewall or similar it would also be good to remove that from the equation, connect the server directly to the router and retest with the default network settings.

[TheRedHerring]

miniserver-diagnostics-20240109-2050.zip

Here's the diagnostics as of the time of posting this. It's changed slightly, as I've done the deleting of boot/config/network etc and rebooted since then, but that didn't resolve it. 

 

I do run PFsense as my router, but have no firewall rules in place, and the config of that hasn't changed since the beginning of the year (barring a firewall rule regarding DNS that only became an issue after following some troubleshooting suggestions that broke things further, which got removed when it was an issue). The only change at the time or close to the break was the above mentioned change for adding link aggregation, which was undone both in the server and the switch. It was also not resolved rebooting after clearing the aforementioned files. 

[TheRedHerring]

miniserver-diagnostics-20240111-2139.zipUpdated version of the diagnostic, since I had a chance to grab it before going to bed. 

[JorgeB]

If I understand correctly using default LAN settings didn't work? If yes that suggests to me a network issue, pfSense may not be the problem but it would be good to rule out for sure, because if that is the problem, and in my experience it's not that uncommon, no way we can fix it in the Unraid side.

 

I would recommend connecting the server directly to the router using the default network settings, if it doesn't work then grab the diagnostics to see if it's not getting an IP, and if it's easier for testing, you can use a new flash drive with a stock Unraid v6.12.6 install, no key needed, and boot with that one just to test, then go back to your current one.

[TheRedHerring]

Default LAN settings work for everything except Unraid Connect and checking for updates on anything; my shares are all accessible and my containers are running without issues, and the only thing changed right now is removing the bond to allow the full speed of the connection I'm using. 

 

Configuring DNS manually to OpenDNS did cause the entire thing to lose connection though, as at that point it failed to grab an IP after rebooting (still attempted to get DHCP, but it didn't set; this is the only device on my network which does this, my main Windows machines and Linux machine have all survived manual DNS and still grabbed IP from DHCP). I'll try a sanity check with a different router (non-firewall) when I have a day off, as after my 12 hour shifts I just want to stop and chill until I pass out; give me a few days to finish out the week and I'll mess with my network on the weekend and report back.

 

As an additional note, in case it helps, it has run on two different PFsense setups in the time this issue has been happening, and it occurred on both. The only thing configured on either PFsense is DHCP, which sets the IP range to 10.0.0.x/8 and DNS to 10.0.0.2, which is a container on the Unraid server (again, same on both; configs only have that changed from default). 

[MrGrey]

18 hours ago, TheRedHerring said:

I do run PFsense as my router, but have no firewall rules in place,

I found this thread searching for pfSense, but it doesn't seem to be about pfSense (on its own)?

 

On 1/5/2024 at 11:29 PM, TheRedHerring said:

I've been running 6.12.6

Of what?... pfSense CE is 2.7...? and you're not running netgate hardware. are you?

 

17 hours ago, TheRedHerring said:

it has run on two different PFsense setups

My bad... Excuse me.

 

Search and destroy. 🤣

 

If it does have something to do with pfSense, there was a recent (ongoing) problem with UEFI boot partition.

 

MrGrey.

[TheRedHerring]

Nope, the thread isn't about pfSense at all; that only came up because it's a firewall and I'm using it as my router

6.12.6 of Unraid (current version, from what I can tell), which is what I'm having a problem with. As for the hardware I run pfSense on, one network I use it on runs Netgate hardware, the other is the same version running the (no longer free) home/lab license of pfSense+ on a super old workstation system

 

I use the Unraid system both at home and a LAN party I help run, hence the two different networks, as it runs a LANCache server that comes in handy when the download speed at the location is 50Mb/s 😂😭

 

Nah, I'm pretty sure the issue is unrelated, as that didn't change either side of the issue I'm having 😉 Though that does possibly explain why I keep having issues with updates for pfSense... 😅

[MrGrey]

I get it (maybe... probably not... I'm slow). If you find pfSense causing problems, we might cross paths again. I wouldn't mind that.

 

MrGrey.

 

[TheRedHerring]

Ironically, I did have to switch routers because I broke a firmware update in pfSense, so I'm currently on OpenWRT (my backup/travel router) and while it didn't work on either of the pfSense routers, it's working. So there's something between pfSense default settings (with only DNS and IP range changed) that apparently Unraid doesn't like...but it had no issue with it before changing the configuration for LACP/802.11ad or whatever, so...very confused.