unRAID 7.3.2

Fix common problems is reporting the following issue.

Errors Found	Suggested Fix	
Unable to communicate with GitHub.com	Reset your modem / router or try again later, or set your to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Routers IP address). Additionally, this may also mean that GitHub is currently down. This error means that you may not be able to update your OS or plugins  More Information	
Warnings Found	Suggested Fix	
No Warnings found
Other Comments	Comments	
Could not check for blacklisted plugins	The download of the blacklist failed	
Could not perform unknown plugins installed checks	The download of the application feed failed.

tower-diagnostics-20260928-0243.zip

Edited September 29Sep 29 by OriginalFlavor

The diagnostics show DNS was working until the DNS settings were changed in Network Settings. It stopped a few minutes later, and since then the server can't resolve any names. That is why FCP can't reach GitHub or download the plugin blacklist and app feed.

Before changing anything else, please post the output of:

cat /etc/resolv.conf

ip route

ping -c 3 192.168.1.254

ping -c 3 8.8.8.8

nslookup github.com

Also, which DNS servers were you using before the change?

Then reboot and check whether the FCP error goes away.

Not able to connect remotely via unRaid connect or Tailscale (The plot thickens). Will update this evening when I have local access.

root@Tower:~# cat /etc/resolv.conf
# Generated by rc.inet1
nameserver 208.67.222.222  # eth0:v4
nameserver 208.67.220.220  # eth0:v4
root@Tower:~# ip route
default via 192.168.1.254 dev br0 metric 4 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
172.18.0.0/16 dev br-af6a406d9e6b proto kernel scope link src 172.18.0.1 linkdown 
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.238 metric 1 
root@Tower:~# ping -c 3 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.825 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.352 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.793 ms

--- 192.168.1.254 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2079ms
rtt min/avg/max/mdev = 0.352/0.656/0.825/0.215 ms
root@Tower:~# ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2071ms

root@Tower:~# ping -c 3 208.67.222.222
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.

--- 208.67.222.222 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2026ms

root@Tower:~# nslookup github.com
;; communications error to 208.67.222.222#53: timed out
;; communications error to 208.67.222.222#53: timed out
;; communications error to 208.67.222.222#53: timed out
;; communications error to 208.67.220.220#53: timed out
;; no servers could be reached

DNS Servers

208.67.222.222

208.67.220.220

Rebooting.

---

Rebooting fixed everything.

(Sorry, I thought I had tried rebooting before making my original post.)

Thank you for your help.