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

**URL:** <https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217>\
**Category:** ℹ️ Support\
**Tags:** update\_problems, nc14, integrity-check\
**Created:** [November 28, 2018, 10:34pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217 "2018-11-28T22:34:45Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![LYeoman](https://help.nextcloud.com/letter_avatar/lyeoman/32/6_22734026db12803ebb3e059622ac3534.png) [@LYeoman](https://help.nextcloud.com/u/LYeoman)\
**Post date:** [November 28, 2018, 10:34pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/1 "2018-11-28T22:34:46Z")

</div>

trying to upgrade 14.0.3 to 14.0.4 - I get: The following extra files have been found \* .rnd

can’t do the upgrade. How do I fix this - need detailed steps please  
it is great - just delete it. what commands do I use to delete such a file

---

<div class="post-metadata">

**Author:** ![martinii](https://help.nextcloud.com/letter_avatar/martinii/32/6_22734026db12803ebb3e059622ac3534.png) [@martinii](https://help.nextcloud.com/u/martinii)\
**Post date:** [November 29, 2018, 9:27pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/2 "2018-11-29T21:27:16Z")

</div>

Same here. Please for help.

---

<div class="post-metadata">

**Author:** ![arucard](https://help.nextcloud.com/letter_avatar/arucard/32/6_22734026db12803ebb3e059622ac3534.png) [@arucard](https://help.nextcloud.com/u/arucard)\
**Post date:** [December 1, 2018, 10:12am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/3 "2018-12-01T10:12:15Z")

</div>

This gives a good explanation of what this .rnd file is: [https://askubuntu.com/questions/379943/what-is-the-rnd-binary-in-my-folder](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.

---

<div class="post-metadata">

**Author:** ![jimbolaya](https://help.nextcloud.com/letter_avatar/jimbolaya/32/6_22734026db12803ebb3e059622ac3534.png) [@jimbolaya](https://help.nextcloud.com/u/jimbolaya)\
**Post date:** [December 3, 2018, 4:36pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/4 "2018-12-03T16:36:56Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![LYeoman](https://help.nextcloud.com/letter_avatar/lyeoman/32/6_22734026db12803ebb3e059622ac3534.png) [@LYeoman](https://help.nextcloud.com/u/LYeoman)\
**Post date:** [December 4, 2018, 10:00pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/5 "2018-12-04T22:00:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![NextCees](https://help.nextcloud.com/user_avatar/help.nextcloud.com/nextcees/32/37795_2.png) [@NextCees](https://help.nextcloud.com/u/NextCees)\
**Post date:** [December 8, 2018, 4:49pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/6 "2018-12-08T16:49:24Z")

</div>

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 ↗](https://www.w3.org/TR/referrer-policy/)." 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:](https://nextcloud.com) 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.

---

<div class="post-metadata">

**Author:** ![NextCees](https://help.nextcloud.com/user_avatar/help.nextcloud.com/nextcees/32/37795_2.png) [@NextCees](https://help.nextcloud.com/u/NextCees)\
**Post date:** [December 11, 2018, 2:08pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/7 "2018-12-11T14:08:20Z")

</div>

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”

---

<div class="post-metadata">

**Author:** ![Rello](https://help.nextcloud.com/user_avatar/help.nextcloud.com/rello/32/166_2.png) [@Rello](https://help.nextcloud.com/u/Rello)\
**Post date:** [December 11, 2018, 2:13pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/8 "2018-12-11T14:13:19Z")

</div>

> [@jimbolaya](#):
>
> I found that file showed up after I used the Audio Player app. But that might have been a coincidence.

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

---

<div class="post-metadata">

**Author:** ![endo64](https://help.nextcloud.com/user_avatar/help.nextcloud.com/endo64/32/3027_2.png) [@endo64](https://help.nextcloud.com/u/endo64)\
**Post date:** [March 2, 2019, 12:04pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/9 "2019-03-02T12:04:09Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![j-ed](https://help.nextcloud.com/user_avatar/help.nextcloud.com/j-ed/32/7281_2.png) [@j-ed](https://help.nextcloud.com/u/j-ed)\
**Post date:** [March 2, 2019, 12:21pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/10 "2019-03-02T12:21:13Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![endo64](https://help.nextcloud.com/user_avatar/help.nextcloud.com/endo64/32/3027_2.png) [@endo64](https://help.nextcloud.com/u/endo64)\
**Post date:** [March 2, 2019, 1:35pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/11 "2019-03-02T13:35:34Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![slattoz](https://help.nextcloud.com/user_avatar/help.nextcloud.com/slattoz/32/14756_2.png) [@slattoz](https://help.nextcloud.com/u/slattoz)\
**Post date:** [July 5, 2019, 8:12am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/12 "2019-07-05T08:12:04Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![codeling](https://help.nextcloud.com/user_avatar/help.nextcloud.com/codeling/32/39922_2.png) [@codeling](https://help.nextcloud.com/u/codeling)\
**Post date:** [August 16, 2019, 7:31am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/13 "2019-08-16T07:31:05Z")

</div>

> [@j-ed](#):
>
> 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.

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…

---

<div class="post-metadata">

**Author:** ![boite](https://help.nextcloud.com/user_avatar/help.nextcloud.com/boite/32/17341_2.png) [@boite](https://help.nextcloud.com/u/boite)\
**Post date:** [August 16, 2019, 9:31am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/14 "2019-08-16T09:31:26Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Morgoth](https://help.nextcloud.com/letter_avatar/morgoth/32/6_22734026db12803ebb3e059622ac3534.png) [@Morgoth](https://help.nextcloud.com/u/Morgoth)\
**Post date:** [August 16, 2019, 10:17am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/15 "2019-08-16T10:17:25Z")

</div>

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”).

---

<div class="post-metadata">

**Author:** ![dev0](https://help.nextcloud.com/letter_avatar/dev0/32/6_22734026db12803ebb3e059622ac3534.png) [@dev0](https://help.nextcloud.com/u/dev0)\
**Post date:** [August 16, 2019, 10:48am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/16 "2019-08-16T10:48:51Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kesselb](https://help.nextcloud.com/user_avatar/help.nextcloud.com/kesselb/32/74519_2.png) [@kesselb](https://help.nextcloud.com/u/kesselb)\
**Post date:** [August 16, 2019, 5:51pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/17 "2019-08-16T17:51:56Z")

</div>

> [@Integrity check failed core -\> extra file -\> .rnd](https://help.nextcloud.com/t/integrity-check-failed-core-extra-file-rnd/41958/9):
>
> It is a “feature” of OpenSSL to collect entropy/randomness if required for cryptography tasks, so for any certificate or key generation, encrypted network connection and such. However I never found one on my systems, no sure in which case these are used. Actually there are kernel files that provide entropy /dev/random and /dev/urandom. Probably OpenSSL (or the software that use its libs) create those files if the regular entropy pool is empty or if they don’t have permissions to access, not sure…

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

> <https://github.com/nextcloud/server/pull/16492>
>
> These files are created sometimes by openssl.

> <https://github.com/nextcloud/updater/pull/236>

---

<div class="post-metadata">

**Author:** ![MichaIng](https://help.nextcloud.com/user_avatar/help.nextcloud.com/michaing/32/2125_2.png) [@MichaIng](https://help.nextcloud.com/u/MichaIng)\
**Post date:** [August 16, 2019, 6:16pm UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/18 "2019-08-16T18:16:15Z")

</div>

> [@kesselb](#):
>
> Starting with Nextcloud 17 these files are ignored from integrity check and updater.

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

---

<div class="post-metadata">

**Author:** ![oliverabraham](https://help.nextcloud.com/user_avatar/help.nextcloud.com/oliverabraham/32/28033_2.png) [@oliverabraham](https://help.nextcloud.com/u/oliverabraham)\
**Post date:** [December 23, 2020, 8:04am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/19 "2020-12-23T08:04:44Z")

</div>

So many writers, but nobody tells me what to do

---

<div class="post-metadata">

**Author:** ![j-ed](https://help.nextcloud.com/user_avatar/help.nextcloud.com/j-ed/32/7281_2.png) [@j-ed](https://help.nextcloud.com/u/j-ed)\
**Post date:** [December 23, 2020, 8:23am UTC](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217/20 "2020-12-23T08:23:11Z")

</div>

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 😉

[Next page](https://help.nextcloud.com/t/trying-to-upgrade-14-03-to-14-04-i-get-the-following-extra-files-have-been-found-rnd/42217.md?page=2)
