Networking issue with Apps and Dockers


Go to solution Solved by Squid,

Recommended Posts

Hello!

I've been trying to solve a weird networking issue and hope to find some help with it.
The other day I changed the motherboard in my server due to a PCIE-issue and after the usual tinkering everything seems to work fine now except I'm not able to view the apps list and my docker containers also don't seem to be able to connect to the internet.

 

From the Apps tab I get the following error:

Download of appfeed failed.

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

 

I tested different DNS-servers (OpenDNS, Cloudflare, Google, etc.) but nothing seems to change.

Ping and manual resovling seems to work fine:

root@X:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=20.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=19.5 ms
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 19.503/20.083/20.663/0.580 ms

root@X:~# ping google.com
PING google.com (142.251.36.238) 56(84) bytes of data.
64 bytes from muc11s22-in-f14.1e100.net (142.251.36.238): icmp_seq=1 ttl=118 time=21.4 ms
64 bytes from muc11s22-in-f14.1e100.net (142.251.36.238): icmp_seq=2 ttl=118 time=18.5 ms
64 bytes from muc11s22-in-f14.1e100.net (142.251.36.238): icmp_seq=3 ttl=118 time=18.0 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 17.979/19.300/21.418/1.512 ms

 

So I did a "reset" on my networking config, meaning I deleted the old network.cfg from /flash/config, rebooted and tried again, nothing changed.

 

I assigned a fixed IP chained to the MAC-adress of the new motherboard, didn't help.

 

So I'm stuck, I hope someone can point me in the right direction, I've attached the diagnostics zip below.

 

Thanks in advance!

ncr-diagnostics-20220814-1427.zip

Link to comment
5 minutes ago, Squid said:

Can you ping

 

raw.githubusercontent.com along with s3.amazonaws.com

 

 

Yes, seems to work fine:

 

root@X:~# ping raw.githubusercontent.com
PING raw.githubusercontent.com (185.199.108.133) 56(84) bytes of data.
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=1 ttl=59 time=13.2 ms
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=2 ttl=59 time=14.2 ms
64 bytes from cdn-185-199-108-133.github.com (185.199.108.133): icmp_seq=3 ttl=59 time=14.0 ms
^C
--- raw.githubusercontent.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 13.232/13.826/14.231/0.429 ms

root@X:~# ping s3.amazonaws.com 
PING s3.amazonaws.com (52.216.109.229) 56(84) bytes of data.
64 bytes from s3-1.amazonaws.com (52.216.109.229): icmp_seq=1 ttl=235 time=102 ms
64 bytes from s3-1.amazonaws.com (52.216.109.229): icmp_seq=2 ttl=235 time=96.7 ms
64 bytes from s3-1.amazonaws.com (52.216.109.229): icmp_seq=3 ttl=235 time=97.0 ms
^C
--- s3.amazonaws.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 96.693/98.615/102.192/2.531 ms

 

Link to comment
5 minutes ago, Squid said:

I'll need to see CA's diagnostics

 

  • Apps, then Settings
  • Enable Debugging and apply
  • Back within CA after the message reappears click the Debugging link at the very bottom

 

Doubt it'll say anything other than it was unable to download the feed, but you never know.

 

Thanks for helping me this far!

 

See the diagnostics output attached. One interesting thing I found while flying over it is that the date seems to be off, also Unraid shows a 3-year plus system uptime which is nowhere near possible.

CA-Logging-20220814-1547.zip

Link to comment
  • Solution
15 minutes ago, BrokenHalo said:

One interesting thing I found while flying over it is that the date seems to be off,

Yeah, that is going to be your entire problem.  Both the logs and CA's diagnostics show that the date is March 15, 2019 and SSL fails if the date is significantly out for security reasons.

 

Settings - Date & Time. set the correct date & time and also give the system a couple of ntp servers

 

image.png

Link to comment
2 minutes ago, Squid said:

Yeah, that is going to be your entire problem.  Both the logs and CA's diagnostics show that the date is March 15, 2019 and SSL fails if the date is significantly out for security reasons.

 

Settings - Date & Time. set the correct date & time and also give the system a couple of ntp servers

 

image.png

 

That seems do have done the trick! That was not what I expected it to be :D

 

Thanks a lot!

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.