Trying to upgrade 14.03 to 14.04 - I get: The following extra files have been found * .rnd

ℹ️ Support
, ,
2

Same here. Please for help.

1 Like
3

This gives a good explanation of what this .rnd file is: https://askubuntu.com/questions/379943/what-is-the-rnd-binary-in-my-folder
It has to do with OpenSSL and it should be safe to delete it.

I also ran into this problem and after deleting it, the updater could continue normally. It’s in the directory where you unpacked Nextcloud, so something like /var/www/nextcloud/.rnd (depends on your setup though).

I’m not sure why this .rnd file showed up in the Nextcloud site directory specifically, maybe someone else can explain what recent developments might have led to this.

1 Like
4

I found that file showed up after I used the Audio Player app. But that might have been a coincidence.

5

Terminal: sudo -i nautilus (be very careful) browsed to nextcloud installation,
view: show hidden files, selected .rnd and moved to trash
update now installs just fine.

6

Today I updated to 14.0.4. I hoped the issues would have been solved. Unfortunately I also got the “The following extra files have been found * .rnd”. I deleted the .md file in de /var/www/nextcloud directory and restarted the update. Now the updated installed okay.

Now I get the warning " De “Referrer-Policy” HTTP header is niet ingesteld op “no-referrer”, “no-referrer-when-downgrade”, “strict-origin”, “strict-origin-when-cross-origin” of “same-origin”. Hierdoor kan verwijzingsinformatie uitlekken. Zie de W3C aanbeveling :arrow_upper_right:." again. This also happened when updating to 14.0.3. I already edited the “/etc/apache2/sites-available/nextcloud-le-ssl.conf” to have the extra lines as follows:

<IfModule mod_headers.c>
Header always set Strict-Transport-Security "max-age=15552000; includeSubDo$
Header always set Referrer-Policy no-referrer
</IfModule>

I am wondering what to change now.

In the overview, logged in as administrator I now see that the update is done but still requires update:

NextCloud: 14.0.4
Er is een nieuwe versie beschikbaar: Nextcloud 14.0.4
Alle apps hebben een update voor deze versie beschikbaar

I have updated my Ubuntu 18.04.01 LTS installation on my home server and reboot ofcourse. There is no extra software on the server, I only run Samba on it. This is the first time I have issues with updating. Is it possible to get some help with this?
Thanks, Cees

I am not sure what to do now.

7

Issues solved:
Login logout updated the version indocator
With 14.0.3 the last sebtence was as mentioned. The correct sentence now for referrer:
Header set Referrer-Policy “no-referrer”

8

Hello,
AP does not use any random number creation. I would not know how the .rnd should be created by AP in this case

9

Even though this is a small issue, it prevents ability to update Nextcloud via web interface. Each time I have to make VPN connection, connect thru SSH, delete the .rnd file and then continue installation, which is a bit annoying, can’t setup script delete that file?

10

The file is usually being created in that directory, because you’ve set it as the home directory of the web user who is used to run the web server. If you change the home directory of the web user, which shouldn’t have any effect on Nextcloud, the file will be outside the Nextcloud root and the message won’t pop-up again.

1 Like
11

Thank you @j-ed I’ll try that.

12

My Nextcloud 15 to 16 was blocked by this too.
rm .rnd in the /var/www/nextcloud folder solved it for me. Thanks all.

1 Like
13

Unfortunately this isn’t the case for me. My nextCloud instance runs on apache (on Ubuntu), apache runs under www-data, and that www-data user has its home at /var/www (according to /etc/passwd), while my nextCloud files reside under /usr/share/webapps/cloud.

There must be some other way for the .rnd file to be created specifically in the nextCloud directory, I have to delete for each update…

14

I’ve had the same issue (.rnd found, prevents upgrade) with minor release upgrades to nextcloud 16. Like other reporters, nc is running on a debian based machine under apache2 (so the web service user is “www-data” and their home dir is /var/www) and served from /srv/nextcloud.

Interestingly, the .rnd file was created during the initial steps of the upgrade process - perhaps when the upgrade file was downloaded - which was performed via the web upgrader.

15

Same here:
NC 16 on Ubuntu 18.04.3 LTS, home dir of www-data is /var/www, nextcloud is running in /var/www/nextcloud. The .rnd file has also been recreated when I started the updater (I deleted the file, started the updater and had to delete it once again before clicking on “retry update”).

16

it looks like that this file issue is a bit ongoing a while ago.

17

Here is a more detailed explanation about these files. Starting with Nextcloud 17 these files are ignored from integrity check and updater.

3 Likes
18

Finally :slightly_smiling_face: , these integrity check issues are already reported for years.

19

So many writers, but nobody tells me what to do

20

If you are able to write postings in english language you should be able to read the information provided how to handle extra files and search the forum to find further information too, shouldn’t you? Delete the file - that’s it :wink:

21 
 find /path/to/nextcloud -type f -name '.rnd' -exec rm {} +

But it should not be required for these particular files from Nextcloud 17 on. In every other case (other extra files), it should be still safe to remove the files, as long as you’re not sure what they are, else move them to another place as backup.