You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The built-in updater (that is used from the web browser) always fails because of an extra file .rnd that is created directly under the Nextcloud installation directory. I have seen other reports where the "solution" is apparently to remove this file.
However, this is not a solution. I have done this now for every update since 15.0.2. Every time, the file is re-created again. So every time I want to update Nextcloud I have to first log in to the server command line and remove the file before I can run the browser-based updater.
While manually removing the file on a one-off occasion may be a workaround, requiring this for every update somewhat defeats the purpose of the browser-based updater in the first place (specifically, to avoid the need to log in to the server command line). Judging from the various reports of this issue, it seems that this is a recurring issue that has been around for at least a few years yet nothing has been done to fix it.
Although Nextcloud does not create this file itself, it is known to be safe to delete so the Nextcloud updater should either delete or ignore this file. Its presence is not an "integrity error" as it is normal for it to appear in some cases and it should not require a manual workaround for every update.
The text was updated successfully, but these errors were encountered:
The built-in updater (that is used from the web browser) always fails because of an extra file
.rnd
that is created directly under the Nextcloud installation directory. I have seen other reports where the "solution" is apparently to remove this file.However, this is not a solution. I have done this now for every update since 15.0.2. Every time, the file is re-created again. So every time I want to update Nextcloud I have to first log in to the server command line and remove the file before I can run the browser-based updater.
While manually removing the file on a one-off occasion may be a workaround, requiring this for every update somewhat defeats the purpose of the browser-based updater in the first place (specifically, to avoid the need to log in to the server command line). Judging from the various reports of this issue, it seems that this is a recurring issue that has been around for at least a few years yet nothing has been done to fix it.
Although Nextcloud does not create this file itself, it is known to be safe to delete so the Nextcloud updater should either delete or ignore this file. Its presence is not an "integrity error" as it is normal for it to appear in some cases and it should not require a manual workaround for every update.
The text was updated successfully, but these errors were encountered: