DS 220+ "Connection failed. Please check your internet connection"

[Lifek]

Hi, I'm new here. I've got a new DS220+ NAS which I unfortunately can't connect it to the internet.


# Problem: I get the message "Connection failed. Please check your internet connection" in various flavors.

Control Panel > Update & Restore > DSM Update > Status: "Connection failed. Please check your internet connection"

Control Panel > Synology Account >Popup: "Unable to perform this operation, possibly because the network connection is unstable..."

Package Center > Popup: "Connection failed. Please check your network and time settings..."

Regional Options > Time Settings > Synchronise with NTP server > Status: "Normal" (!!!)


# What I want

I want to a) be able to update my NAS and b) download some packages for a self-hosted setup (docker, git, paperless, ...)



# Things I tried

• Manually updating the DS to the latest version
• Every combination of DNS servers (in the router and in the NAS).
  • I tried all variants of 8.8.8.8, 8.8.4.4, 1.1.1.1 and 9.9.9.9.
  • I also tried the internet provider recommended one
• The steps on
  • Why can't I connect to Package Center? - Synology Knowledge Center,
  • Problems connection to NAS Control Panel via ethernet,
  • I encountered the "connection failed" message. What can I do? - Synology Knowledge Center and
  • Handling the Dreaded Synology DSM 'Cannot Connect To The Internet' Error
• Random steps I found on the internet or in the forum. Unfortunately I lost track of what I tried..
  • For examples things from Problems connection to NAS Control Panel via ethernet
• Logging into my NAS via SSH and ping'ing all the addresses listed on What websites does my Synology NAS connect to when running services or updating software? - Synology Knowledge Center
• Restarting
• I also tried using the web GUI from different browsers and PCs
• I also I ran all the commands on a PC that is connected via ethernet to the router. Didn't notice any problems

Finally, as I can update the date/time, I believe this to be a DNS problem. I ran some random commands, but I have no idea what I am doing here..

$ nslookup download.synology.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: download.synology.com
Address: 203.74.127.91

$ ifconfig -v
eth0 Link encap:Ethernet HWaddr 90:090:2B:C4:C1
inet addr:192.168.178.30 Bcast:192.168.178.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15275 errors:0 dropped:0 overruns:0 frame:0
TX packets:8879 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3302201 (3.1 MiB) TX bytes:4764704 (4.5 MiB)
Interrupt:84 base 0xe000

eth1 Link encap:Ethernet HWaddr 90:090:2B:C4:C2
inet addr:192.168.178.31 Bcast:192.168.178.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7129 errors:0 dropped:0 overruns:0 frame:0
TX packets:257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:739914 (722.5 KiB) TX bytes:46551 (45.4 KiB)
Interrupt:85 base 0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:13242 errors:0 dropped:0 overruns:0 frame:0
TX packets:13242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1874907 (1.7 MiB) TX bytes:1874907 (1.7 MiB)

$ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.178.1 0.0.0.0 UG 0 0 0 eth0
192.168.178.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.178.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1

it appears as if pinging to the Synology servers via CLI works. But in the GUI I still get the errors.







# System Information

## Router (Fritz!Box 7530 AX)

## Info Center

## Network

### Interfaces

## Error messages

 

[Deleted member 5784]

It's not a DNS problem; NSLOOKUP is resolving download.synology.com from 8.8.8.8 and your pings were being resolved

• Simplify things: remove ethernet cable from LAN2. Focus on getting a connection on LAN1 working correctly.
• Remove 'Set as default gateway' from IPv4 LAN1 settings. You almost certainly want your router out to the internet to be the default gateway, not your NAS.

 

[EAZ1964]

I would reset (short 3s) the nas to reset network settings to default, pick it up from the synology assistant and follow the instruction from fortran. Do not mess with all these settings, no need. this should work right out of the box.

 

[Lifek]

Resetting did it! I have no idea how and why, I'm simply happy -- thank you both very much!

 

[Yaneek]

Hi, I have exactly the same problem with my DS220+ running DSM 7.2-64570 Update 2.

I.e.

• time synchronization works OK
• package centre works OK (ie loads packages)
• settings backup to Synology account works OK
• however, the "Update & Restore" gives me "Connection failed. Please check your Internet connection".

I've already tried rebooting or resetting network settings (holding reset button until a beep), however, no success.

Does anyone have any other idea what to do?

 

[leriak]

I just noticed that I'm having the same issue...

Does not work:

• DSM update -> Connection failed... blah blah blah
• Package center -> Connection failed... blah blah blah

Does work:

• Config backup to synology account
• NTP to pool.ntp.org
• Backup to synology C2 -> I had an error that it failed during the night, when I woke up I ran the task manually and it worked
• nslookup from terminal to various domains, including synology.com

I haven't changed anything for a while, my first guess is that this may be a problem on synology's end.

I'll give it a few hours or a day and if it still does not work I'll open a support ticket.

 

[Jheroen]

I had this also when i checked the nasses this morning, what i did (i use QC) is disable QC > save, enable QC > save
Et voila, all working again

 

[HomersAss]

Me too. Can't update or browse packages...

 

[Yaneek]

I had this also when i checked the nasses this morning, what i did (i use QC) is disable QC > save, enable QC > save
Et voila, all working again

Lucky you. I did the same with no result.

 

[leriak]

I had this also when i checked the nasses this morning, what i did (i use QC) is disable QC > save, enable QC > save
Et voila, all working again

I've never used QC, but I've enabled it just to try this, no effect.

 

[Rusty]

Looks like https://update7.synology.com/autoupdate has some 500 code errors. This is on Syno side (or by extension on AWS where this is being hosted).

 

[leriak]

Looks like https://update7.synology.com/autoupdate has some 500 code errors. This is on Syno side (or by extension on AWS where this is being hosted).

Thanks for the info @Rusty

 

[Telos]

Synology Community

Hi! Come and join us at Synology Community. A place to answer all your Synology questions. Ask a question or start a discussion now.

community.synology.com

 

[Rusty]

Called it

 

[Jheroen]

I still had troubles with the packagecenter, i followed this article which solved that problem

 

[fidoedidoe]

I also have the same issue, NTP time sync + other network-related items (cloud backup, nslookup from terminal session, etc ) all working. I'm assuming (as @Rusty wrote) this is an upstream issue. other troubleshooting steps are related to DNS etc etc which I've confirmed to be "fine" from CLI.

 

[Rusty]

AWS issue is still ongoing as far as I can tell.

 

[Telos]

AWS issue

Synology is quick to blame others for their screw-ups.Odd that this "AWS issue " seems only to have affected Synology (rare too that an AWS issue would extend beyond 24 hours). Just sayin...

 

[Rusty]

Synology is quick to blame others for their screw-ups.Odd that this "AWS issue " seems only to have affected Synology (rare too that an AWS issue would extend beyond 24 hours). Just sayin...

I agree. But with no info on this it's hard to point fingers. Syno should be more transparent on this for sure

 

[leriak]

I have "recovered" the package center functionality after manually installing the synology photos 1.5 package .spk. I have no idea why...

DSM update still reports "connection error check your internet" which is funny considering the problem is on the server end:

I find really annoying when error messages blame the user for something that may or may not be the user problem. In this case synology is not telling categorically that the internet connection is the source of the error, but as they are only telling you to check the internet they are heavily implying that it's the only possible cause.

I've actually filed formal complaints with my local mass transit provider due to some access machines telling that the user travel card has no magnetic band, and then the machine next to it accepting the card without issue. If the machine cannot tell if itself is in perfect working order it cannot assume that the travel card is defective.