NAS326 web gui stuck in NFS package update loop after fw update to 5.21

@AlexSA On a NAS326 you don't need ffp for ssh access. The NAS supports ssh and telnet out of the box. You only have to enable it in the webinterface (which is for you, currently, of course a problem).

The CloudAgent indeed is automagically installed. The package 'Tweaks' has an option to block that.

About the browser console, it might be that the error is caused by the ffp package. At the place of the error the script tries to provide a link or button for the webinterface of an installed package, and errors out because it doesn't check if such an interface actually exists. Ffp doesn't have a webinterface, so it could trigger this error. I doubt if that causes your error, as more people have ffp installed, and it was never a (blocking) error.

@ariek MetaRepository did install the packages from the ZyXEL server, until half a year ago, when ZyXEL cleaned up their server, and removed the packages (and firmware, docs, ...) for all NSA boxes, and the NAS520. The latter was a mistake, I suppose, but it was never reverted.

With MR installed, the package manager queries the internal server for the packages, and MR forwards that to one or more external servers. If the URL of the external server as provided to MR has a '+', that is exchanged by the path of the requested file. This way MR can access the right directory on the ZyXEL server without having to know the NAS type and firmware version, as that is provided by the package manager.

You created a local repository, which is fine. You could also have exchanged the ftp://ftp2.zyxel.com/+ url by ftp://ftp2.zyxel.com/NAS540/5.21/zypkgs/ (or whatever the exact path is)

I don't know. It's some flag in a settings file, but ZyXEL uses several settings files in different formats.

If you never enabled it, it is not enabled. The firmware sshd cannot run simultaneously with the ffp one, at least not on the same port. So you can't simply look if it's running.

It erases a partition on flash, containing all user settings (including the 'enabled' flags of all packages), and deletes one or two cache files on the data partition.

As far as I know (by reading this forum and some other) webinterface problems are always cured by a factory reset. But of course your problem could be different. If you have moved all your packages from .PKG, and performed a factory reset, the box is basically virginal. If the webinterface doesn't come up then, you have either a hardware problem, or a bug in the firmware. The latter is unlikely, as others don't have this problem. And a hardware problem, well, it's hard to think of a problem with this symptoms. But not impossible.

You could try to boot the box without disks. If the webinterface still doesn't work, it's not your packages.