Hello

 

I've been using unRAID with the same configuration for years without this problem.

 

I've had a strange problem for a few days now. It seems to have appeared without any change on my part, either on the server side or on my modem.

When I try to access the APP tab, I get an error message at some point:

 

Community Applications requires your server to have internet access. The most common cause of this failure is a failure to resolve DNS addresses. You can try and reset your modem and router to fix this issue, or set static DNS addresses (Settings - Network Settings) of 208.67.222.222 and 208.67.220.220 and try again.

Alternatively, there is also a chance that the server handling the application feed is temporarily down. See also this post for more information

Last JSON error Recorded: Syntax error

 

Same thing, I can't update my containers either, it ends in timeout, check plugins update, Plex is no longer accessible from the outside either, etc.

 

The solution I've found is disconnecting and reconnecting my modem. Everything works again for about 10 minutes, then everything becomes inaccessible again.

 

I was in version 6.12.13, I tried to upgrade to 6.12.14, same result. In Settings > Network Settings, I put 9.9.9.9 in IPv4 DNS server 2 and 149.112.112.112 IPv4 DNS server 3 but that doesn't change anything (before I had nothing in these fields).

 

I see network activity on the dashboard even when the server is inaccessible :

 

I don't know if this helps, but I'm not having any other problems on my network, UnRAID is inaccessible, but I do have internet on my PC, my phone, etc. I'm not sure if that's a problem. Everything works except the unRAID server.

 

I don't really know what to do, it's out of my hands. I've attached a diagnostic file.

 

Thank you very much for your help

 

Edited December 16, 20241 yr by Alex.b

What kind of modem is it?  

Is your server connected directly to a modem port?

What are you using as a router?

Are there switches in between?

 

-It's a modem from my ISP (Livebox 5 from Orange Telecom)

-No I'm using a switch,

-Yes my modem is my router

- I have a small switch between my modem and my server because I have only one ethernet port in my living room and I need to connect my server and my AppleTV

 

I tried to connect the server directly to the modem with another ethernet cable. I have the same behaviour.

Edited December 15, 20241 yr by Alex.b

This definitely stinks of DNS trouble and I think there are two ways to go about this.

 

1. Modem/Router setting:  Configure your Livebox 5 DNS.  Go in there and add two DNS IP addresses.  I like 9's (9.9.9.9) as well as OpenDNS (208.67.222.222).  There are many others out there of course.  Cloudflare and Google are very reliable too.

This setting combined with your server using modem/router IP of 192.168.1.1 for DNS should get you there.

 

2. Server setting:  Bypass your modem/router DNS completely and remove the 192.168.1.1 as your server DNS IP.

You mentioned already setting your server DNS to "I put 9.9.9.9 in IPv4 DNS server 2 and 149.112.112.112".  My trouble is that in the logs

-url.txt I see DNS 1:       192.168.1.1 only.

-network.cfg I see DNS_SERVER1="192.168.1.1"
DNS_SERVER2="9.XXX.XXX.9"
DNS_SERVER3="149.XXX.XXX.112"

Maybe those are obfuscated by the log so I don't know for sure if it is correct.

So, go back and check that the DNS IP addresses added in there like you intended.

 

Unfortunately it's not possible to change the DNS servers on the Orange Livebox 5 (yes, it's a heresy).

 

I checked, It was been 9.9.9.9 and 149.112.112.112 on server 2 and 3, those were probably obfuscated by the log.

 

I will try with 9.9.9.9 instead of 192.168.1.9.

 

 

Thanks for your help, I'll get back to you soon.

 

As a last resort, I'd reset the modem to factory settings, I'm not happy about it but it could be a solution.

Edited December 15, 20241 yr by Alex.b

It's now been 30 minutes since I restarted my modem and my server with the DNS server 9.9.9.9 instead of 192.168.1.1 in the network settings.

 

When I restarted the server 30 mins ago, I didn't even start the array to minimise the risk of further problems (whether from docker or a VM), I just open the terminal every 2-3 minutes to ping 8.8.8.8 and so far it's working.

 

Several questions come to mind, why has it been working like this for 2 years and now it's not? I checked my modem's firmware beforehand and the last update was more than 2 months ago. Could it be that my ISP has arbitrarily decided to change something on their end? (Sorry, my knowledge of networks and DNS is pretty poor).

Edited December 15, 20241 yr by Alex.b

13 minutes ago, Alex.b said:

Several questions come to mind, why has it been working like this for 2 years and now it's not? I checked my modem's firmware beforehand and the last update was more than 2 months ago. Could it be that my ISP has arbitrarily decided to change something on their end? (Sorry, my knowledge of networks and DNS is pretty poor).

Very reasonable questions to which I have no real answer.  DNS is always at the top of  good tech/engineer's list of things to check when things go sideways for no apparent reason. 

  Hope it remains solid for you. 

Annnnnnnd it's gone !

 

Did it fail when I launched the array (with docker ? ... maybe).

 

Tomorrow is another day, with probably some new ideas lol

A reboot of the switch may be in order.  Also, happen to have a spare network cable you can swap from server to switch?  Change port too if possible. 

And as you mentioned earlier, resetting and defaulting the modem is a good idea too.

17 hours ago, Veah said:

A reboot of the switch may be in order.  Also, happen to have a spare network cable you can swap from server to switch?  Change port too if possible. 

And as you mentioned earlier, resetting and defaulting the modem is a good idea too.

 

I'll get back to you, I reset the modem about ten hours ago and it's been working ever since! I have to admit I don't really understand why it works now and not yesterday (my router only had a few basic settings like WiFi and I have 2 port forwardings).

 

I hope the problem has been solved! Thanks again for all your help.

 

Tomorrow I'll have to test putting the switch back between the modem and the server (the server is still connected directly to the box with an ethernet cable that runs throughout the house) 🤣

Edited December 15, 20241 yr by Alex.b