March 13, 20251 yr I've recently started getting "no connectivity" errors on plugin update page, even though I can connect to server. Things I've tried so far (without success): 1. Rebooting 2. Upgrading from 7.0 to 7.01 3. Updating DNS IP from my Gateway IP to 8.8.8.8 4. Checking that I do not have Network Tools or Realtek plugins. 5. Pinging google.com and running nslookup google.com from shell window (both works) Any help will be greatly appreciated. Thanks, Maxim htpc-diagnostics-20250313-1601.zip
March 13, 20251 yr Author I can also install new plugins from Community apps tab and can update docker containers for which new update is available, so it seems that host can connect to internet. On other hand, one of VMs (Home Assistant) reports that host has no internet connection, but I can ping google.com from inside that VM too.
April 20, 20251 yr Did you find a solution to your issues? As far as I can tell I'm in a similar situation. No connection to update plugins and no update available in Docker after upgrading to ver. 7.0.1.
April 21, 20251 yr 12 hours ago, Zipocratez said: Did you find a solution to your issues? As far as I can tell I'm in a similar situation. No connection to update plugins and no update available in Docker after upgrading to ver. 7.0.1. But can you install new apps from the Apps tab?
April 21, 20251 yr Author As a troubleshooting step, I've made a bootable flash with a clean installation of 7.01 - even on that clean installation Plugins tab still fails to check for updates (but I can install and update plugins from Apps tab). I am planning to test some older version (6.11) to see if the issue still persists. I've checked my firewall and it is not blocking UDP traffic, but it may be blocking some domains (adblock) and I wonder what domain unraid uses to check for connectivity. I do have similar issue with Home Assistant installation running in Unraid and I think these have something in common.
April 26, 20251 yr Author Solution In my particular case, I was able to see that the issue disappeared once I bypassed the router and connected test Unraid box directly to the modem. I was later able to find a misconfiguration on my router (incorrect port forwarding for DNS queries) which caused the issue. Interestingly enough, Unraid 6.11 and 6.12 did not have same issue even with routing misconfigured.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.