Nas Quickconnect the Service Is Busy Now Please Try Again Later

I finally had a couple of seconds to rub together to endeavour out the mixed-environment Synology backup workflow that I've been meaning to get around to, simply needed to do some quick updates to some boxes that I accept not used in a while. Fiddling did I know that I'd have to postpone it, yet over again.

[Update 2017.06.13. For this exercise I'm bold y'all have your Synology connected to a router/switch, not directly attached to a computer. If you adhere the Synology straight to a computer that is non running DHCP you lot will go a 169.254.10.Y accost, it will not connect to the Internet and these instructions won't work, I'1000 afraid.]

When you log into the DSM Control Panel, you'll run into a familiar flag continued to the icon, letting you lot know that there is an update to be made:

You've got updates!

When you click on the update, the command panel will open upward and you can see the little flag bounce at you:

Pick me!

When you click on the Update and Restore icon, what yous should see is this:

Update at will, ensign.

Instead, sometimes you can get this:

Ah, crap. Now what?!

(Eagle-eyed readers will discover that these last two screenshots are from ii different machines. Fear non: it happened with both of them).

Ah, yep. The evil, "Connection failed. Please cheque your Internet Connection" error. This problem has confounded many a poor soul. Rumor has it that the only people to have successfully browbeaten this devilish problem are the Ancient Mayans, who also were able to count to 2012 and start over without panicking about the end of the world.

Now before yous run screaming to the streets or try to wipe your Synology clean, hither are a couple of things you can try.

First, navigate to the control panel if it's not already showing (that's the icon I showed upwardly above). Then you want to observe the icon labeled "Network." It looks like a little house sitting on top of a sewer line (and if you lot know anything nearly networking, you'll realize just how advisable that is):

The screen that pops up volition tell you what your network settings are. Nearly of these should exist filled in for you. There is, however, two lines that you need to look at: The Default Gateway and the IPv6 Default Gateway.

Wait at the pretty circles.

You'll discover a couple of things. First, there is no Default Gateway listed. This is bad. We'll get to what these things hateful in just a moment. For now, let's gear up this.

Default Gateways

Click on the "Edit" button next to the Default Gateway. It should expect something like this:

I meet y'all now!

One time the LAN configuration is populated (i.e., it shows upwards), y'all can click on OK. The Network control panel should at present have this value next to information technology:

Where you been all my life?

Simply what happens if it's not there? Everybody panic!!

Wait, expect. No, that'south not correct. Let's endeavour this instead. Click on the side by side tab over, the "Network Interface" tab. You'll run across at least i connexion listed.

Getting closer…

Go ahead and click on "Edit" with the interface highlighted, as it is in the picture above. Here is where your mileage may vary. If you accept your Synology Diskstation prepare upwardly to get its network configuration from your router, information technology will have "Go network configuration automatically (DHCP) called for you. Personally, I like to have my devices on static IP addresses, so I use the manual configuration option:

Why do it the easy manner? Manual config all the mode!

If you didn't see the default gateway in the previous pace, yous may desire to cheque to brand sure that the checkbox is selected to "set as default gateway."

One word of circumspection: Practice not put in arbitrary numbers hither . These numbers mean something, so if this is all Greek to you then simply keep the "Get network configuration automatically (DHCP)" checked and don't worry about this stuff.

While we're on this screen, however, we need to make some changes to the IPv6 settings too. Fortunately, it's only one tab over. In that location's only one change yous have to make here, and it's an easy ane:

IPv6 is a large bowl of "nope"… for now.

Yup. Only turn IPv6 off.

Then what does this stuff mean? The Synology needs to know where to detect its way out of the network to encounter the world (fly! Be costless, picayune Synology!). The Default Gateway is just that – information technology's the gateway to the world (online, at least), and the "default" part of information technology means that this is where the Synology should expect if it wants to communicate with the outside world. Since nosotros desire to know if Synology has an update that nosotros need, and Synology is in the exterior globe, this Synology does not know where to get.

The second affair you'll run into is that the IPv6 default gateway does have an accost listed. Yes, it'southward the fe80::5a6d:8fff:fef6:a226 gibberish that'southward adjacent to the words "IPv6 default gateway." Nifty how that works, eh?

When you turn information technology off, this default gateway should disappear, and it should await something similar this:

Which way did he go, George?

DNS Servers

So, we figured out how to tell the Synology to notice devices outside of our home network. This is the "if yous don't know where to go, go here" setting. Simply once the Synology goes at that place, then what?

The DNS Server is the place to exercise that. It's a server that keeps rail of what all these strange numbers hateful. They're the devices that you can ask to find out how to turn google.com into an address that the computers understand, and vice versa.

Speaking of Google, Synology recommends using their DNS server address equally the "Preferred DNS Server," then you should brand your organisation look like this:

The Goobles to the rescue!

Now, in this case, you lot want to make sure that the numbers lucifer exactly. The periods (full stops) and all. No spaces. You practise non accept to take an alternative DNS Server, but I put my default gateway equally my culling if, for whatever reason, Google's DNS server doesn't respond.

Here Goes Goose egg

When I updated my two boxes, I had very different reactions from them. They both gave me the "Could not connect" error. What was fifty-fifty stranger was that on i of the boxes, I did not take to remove the IPv6 setting for information technology to work – a simple restart after fixing the default gateway and DNS server gave me complete connectivity. The other one, though, was a true PITA.

I tried using Synology'south QuickConnect, and information technology didn't work either. And then, I had a bit of a minor success. I was able to turn on the NTP server (that's the service that lets the Synology know what time it is, according to the United states of america Government'due south NIST time servers). So, miraculously, QuickConnect worked. However, the DSM update continued to requite me that error.

Then, about 5 minutes later, the DSM update was giving me what I needed to run into:

Success!

My best guess is that the fourth dimension it took for the routing tables to be updated took far longer than either the DSM user interface or my patience expected. I had restarted the box a couple of times in the acting, hoping that information technology would take, but I call back I might have disrupted the population of the tables, and the DiskStation simply restarted the procedure again. I think that patience is far more useful a tool in this case than I outset thought.

Other Options

Update 2018.06.25. Several readers have written in to say that this has helped them effigy out what's going wrong, and others have offered suggestions for what have helped them fix the upshot equally well. I have not attempted these, but I'm leaving them here as a courtesy for the reader to endeavour, should the in a higher place steps fail to resolve the upshot.

1. Change the admin account password. Every Synology has an "admin" account. Some people have had luck irresolute the password. It's not articulate why this is an event; the best I can remember of is that newer versions of DSM are requiring a stronger password for allowing incoming/outgoing traffic, just that's only a guess. In whatever case, try changing the Synology "admin" account countersign.
2. Modify DNS settings. I do non use the Synology's DNS settings, so this was not an result for me. All the same, another reader is using Synology's RT1900ac router, and offered the post-obit advice:For the DHCP server, "forward known DNS server" was disabled. Likewise, IPV6 was setup as Car in STATELESS mode. With these settings DSM update could not connect to the internet.Since the issue seems to exist DNS related, I changed these two settings: a) I enabled "forward known DNS server", and b) I changed my IPV6 setup to be stateless DHCPv6. I'yard not sure which stock-still the problem, but my DSM was immediately able detect and install updates.
3. Bank check your time zone/fourth dimension server (NTP Server). If the date/time setting is out of whack, it tin can create issues.
4. If the Diskstation switches to offline mode afterwards a few seconds, try whitelisting the Synology server in uMatrix. DSM may notice that the browser won't able to open the pages and switch to offline mode. The Synology update server may exist found after that. Try pinging arbitrary addresses to double-check. (Thanks and h/t to Carsten Groß)

As I said, I have not attempted these fixes myself (hence no screenshots), just readers were kind enough to offer additional suggestions and if it helps yous in your 60 minutes of demand, delight let me know. YMMV.

Synology's Accept

I contacted Synology's tech support to observe out why this might be happening, since there were no reports in the logs almost what had happened during the update process. Hither'due south what I got, verbatim:

Upon further investigation I see there were some bugs in the past with a disappearing gateway, primarily if the connections were bonded during the upgrade. It was a bug that should be resolved now and should not typically happen.

Now, it is true that one of the Synology DiskStations I was updating had bonded network interfaces, simply that was also the one that fixed itself faster. True, I was updating to DSM six.0 so perhaps the fix was already existence applied at that betoken too. The device that I take been using as an case, yet, only had one network interface and then there was no link aggregation (or "bonding") going on.

Nevertheless, after I run the backup tests in a mixed DSM 5.ii/vi.0 environment, I'll be needing to update this box to 6.0, and then I'm fully expecting to need to refer back to this blog once again if/when I lose network connectivity!

Determination

I did read some additional messages in the user forums that permissions problems could be to blame for this effect, but it was not so in my instance. My gut tells me that is a different issue – the problem here is connecting to the Synology servers in order to determine whether there is an update, and if then which one. Permissions issues would likely only result once it has been adamant that an update exists and then issues would arise when trying to save information technology to a local directory on the Synology. That'south my gut take on it, nonetheless, and certainly non something I'd defend to the death.

In any case, I hope that this is somewhat helpful to people (including myself). If this works – or if it doesn't work – delight feel free to leave a annotate and let me know. Anything I missed? Please feel free to offer another solution to help out. 🙂

shapirosanclaus1973.blogspot.com

Source: https://jmetz.com/2016/09/handling-the-dreaded-synology-dsm-cannot-connect-to-the-internet-error/

Share this post