Synology Volume Is Busy Try Again Later

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

[Update 2017.06.13. For this practise I'm assuming you have your Synology connected to a router/switch, not directly attached to a calculator. If yous attach the Synology directly to a computer that is not running DHCP you volition become a 169.254.10.Y accost, it will not connect to the Net and these instructions won't work, I'm afraid.]

When you log into the DSM Control Panel, you lot'll see a familiar flag connected to the icon, letting yous know that in that location is an update to be made:

You've got updates!

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

Option me!

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

Update at will, ensign.

Instead, sometimes y'all can go this:

Ah, crap. Now what?!

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

Ah, yes. The evil, "Connection failed. Delight check your Internet Connection" error. This problem has confounded many a poor soul. Rumor has information technology that the only people to take successfully beaten this devilish problem are the Aboriginal Mayans, who also were able to count to 2012 and start over without panicking about the end of the world.

Now before you run screaming to the streets or attempt to wipe your Synology clean, here are a couple of things you tin can endeavor.

First, navigate to the control panel if it's not already showing (that's the icon I showed upward above). Then yous want to find the icon labeled "Network." It looks similar a little business firm sitting on top of a sewer line (and if you know annihilation most networking, you'll realize just how appropriate that is):

The screen that pops upwards will tell you what your network settings are. Nigh of these should exist filled in for you. In that location is, still, ii lines that you lot demand to expect at: The Default Gateway and the IPv6 Default Gateway.

Wait at the pretty circles.

You'll detect a couple of things. Offset, there is no Default Gateway listed. This is bad. We'll get to what these things hateful in simply a moment. For now, let's ready this.

Default Gateways

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

I see you at present!

Once the LAN configuration is populated (i.e., it shows upward), yous tin click on OK. The Network command console should now accept this value next to it:

Where you been all my life?

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

Expect, wait. No, that's not right. Let's endeavor this instead. Click on the next tab over, the "Network Interface" tab. You lot'll see at least one connectedness listed.

Getting closer…

Go ahead and click on "Edit" with the interface highlighted, equally it is in the motion-picture show in a higher place. Here is where your mileage may vary. If you lot have your Synology Diskstation set to get its network configuration from your router, it will have "Go network configuration automatically (DHCP) chosen for you. Personally, I like to have my devices on static IP addresses, and so I use the manual configuration option:

Why practise it the like shooting fish in a barrel way? Manual config all the way!

If yous didn't encounter the default gateway in the previous pace, you may want to check to make sure that the checkbox is selected to "set as default gateway."

One discussion of circumspection: Do non put in capricious numbers hither . These numbers hateful something, so if this is all Greek to you then simply go along the "Get network configuration automatically (DHCP)" checked and don't worry well-nigh this stuff.

While we're on this screen, nevertheless, nosotros demand to brand some changes to the IPv6 settings as well. Fortunately, it'south simply one tab over. There'southward only one change yous take to make hither, and it's an piece of cake one:

IPv6 is a big basin of "nope"… for now.

Yup. But turn IPv6 off.

So what does this stuff mean? The Synology needs to know where to discover its style out of the network to run into the world (wing! Exist gratuitous, little Synology!). The Default Gateway is but 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 look if it wants to communicate with the outside world. Since we want to know if Synology has an update that we need, and Synology is in the outside world, this Synology does not know where to go.

The 2nd matter you'll meet is that the IPv6 default gateway does have an accost listed. Yep, it's the fe80::5a6d:8fff:fef6:a226 gibberish that'due south next to the words "IPv6 default gateway." Nifty how that works, eh?

When yous turn information technology off, this default gateway should disappear, and it should expect something like this:

Which way did he become, George?

DNS Servers

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

The DNS Server is the place to practice that. It'south a server that keeps track of what all these strange numbers mean. They're the devices that you tin 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 as the "Preferred DNS Server," so you should make your organization await similar this:

The Goobles to the rescue!

Now, in this case, you desire to brand sure that the numbers match exactly. The periods (total stops) and all. No spaces. You do not have to have an alternative DNS Server, simply I put my default gateway equally my culling if, for any reason, Google's DNS server doesn't respond.

Here Goes Nil

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

I tried using Synology's QuickConnect, and information technology didn't work either. Then, I had a bit of a small-scale success. I was able to turn on the NTP server (that's the service that lets the Synology know what time information technology is, co-ordinate to the U.s. Government's NIST time servers). And so, miraculously, QuickConnect worked. Nevertheless, the DSM update continued to give me that error.

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

Success!

My all-time judge is that the time information technology took for the routing tables to exist 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 it would take, but I think I might take disrupted the population of the tables, and the DiskStation only restarted the process over again. I think that patience is far more than useful a tool in this instance than I first thought.

Other Options

Update 2018.06.25. Several readers accept 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 issue as well. I have non attempted these, merely I'm leaving them hither equally a courtesy for the reader to endeavor, should the above steps fail to resolve the outcome.

1. Change the admin account countersign. Every Synology has an "admin" business relationship. Some people have had luck changing the password. It's not articulate why this is an outcome; the best I can remember of is that newer versions of DSM are requiring a stronger countersign for allowing incoming/approachable traffic, but that'southward just a gauge. In any case, effort changing the Synology "admin" account password.
2. Modify DNS settings. I do not employ the Synology'south DNS settings, then this was not an issue for me. However, another reader is using Synology'due south RT1900ac router, and offered the following communication:For the DHCP server, "forward known DNS server" was disabled. Also, IPV6 was setup equally AUTO in STATELESS way. 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 "forwards known DNS server", and b) I changed my IPV6 setup to be stateless DHCPv6. I'thou non sure which fixed the trouble, but my DSM was immediately able find and install updates.
3. Check your time zone/fourth dimension server (NTP Server). If the date/time setting is out of whack, it tin create issues.
4. If the Diskstation switches to offline mode after a few seconds, endeavour whitelisting the Synology server in uMatrix. DSM may observe that the browser won't able to open the pages and switch to offline manner. The Synology update server may be found subsequently that. Try pinging arbitrary addresses to double-check. (Thanks and h/t to Carsten Groß)

Every bit I said, I have not attempted these fixes myself (hence no screenshots), but readers were kind enough to offer additional suggestions and if information technology helps you in your hr of need, please let me know. YMMV.

Synology's Take

I contacted Synology's tech back up to observe out why this might be happening, since in that location were no reports in the logs about what had happened during the update process. Here'due south what I got, verbatim:

Upon farther investigation I see at that place were some bugs in the past with a disappearing gateway, primarily if the connections were bonded during the upgrade. Information technology was a bug that should exist resolved at present and should non typically happen.

Now, it is truthful that ane of the Synology DiskStations I was updating had bonded network interfaces, simply that was as well the ane that stock-still itself faster. True, I was updating to DSM half dozen.0 so possibly the fix was already being applied at that point too. The device that I have been using as an example, however, only had one network interface then at that place was no link assemblage (or "bonding") going on.

Fifty-fifty so, after I run the backup tests in a mixed DSM five.2/6.0 environment, I'll exist needing to update this box to 6.0, so I'm fully expecting to need to refer dorsum to this blog again if/when I lose network connectivity!

Conclusion

I did read some additional messages in the user forums that permissions bug could exist to blame for this effect, simply it was not so in my instance. My gut tells me that is a different result – the problem here is connecting to the Synology servers in club to determine whether in that location is an update, and if and then which ane. Permissions issues would probable only result once information technology has been determined that an update exists and then bug would arise when trying to save information technology to a local directory on the Synology. That's my gut accept on it, withal, and certainly not something I'd defend to the death.

In any example, I hope that this is somewhat helpful to people (including myself). If this works – or if it doesn't work – please feel free to exit a comment and permit me know. Annihilation I missed? Delight feel free to offer another solution to help out. 🙂

moorethistility.blogspot.com

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

Share this post