11-11-2018 02:37 PM
Tried a couple of times to update USG to latest. Every time it didn't finish, and had to be re-booted to re-connect with the controller. Happens to a lot of people here.
Tried the online chat, and was told to cache the update first. I didn't think it would work, but it did.
If the firmware process is known to be unstable, and the advice is to cached the update... Why doesn't the controller just cache all updates?
11-11-2018 04:14 PM
11-11-2018 10:23 PM
My understanding is that the device will try to download it directly from UBNT unless your controller offers it, which it can only do if it's cached. The times when I've seen failures to upgrade firmware are when network issues (usually DNS) prevented the device from downloading the firmware from UBNT directly.
11-12-2018 08:23 AM
11-12-2018 08:30 AM
For me it always works perfectly when updating directly, without caching first.
I think they just told you to cache it first to work around the problem that the USG could not resolve the download URL.
11-12-2018 08:35 AM
yes, that seems to be the behavior. But why would they design their updater to force the device into an unresponsive state after failing to resolve the DNS of the firmware? Why not just stop the update and leave the USG in a good state?
That's a good question. I don't recall if the times I've encountered this when it was a network download issue that the USG went unresponsive, it may have just not downloaded and stayed online at the old firmware. Maybe something else is going on to make it unresponsive?