Nextcloud 32.0.8 update not possible due to write permission (nohup.out)

[fromagecloud]

• Nextcloud Server version:
  • 32.0.6
• Operating system and version:
  • NextcloudPi v1.56.0
• Web server and version:
  • Server version: Apache/2.4.66 (Debian)
• PHP version:
  • PHP 8.4.19
• Is this the first time you’ve seen this error? (Yes / No):
  • yes
• When did this problem seem to first start?
  • yesterday (April 3rd 2026)
• Installation method:
  • NextcloudPi image

Summary of the issue you are facing:

Hello,

I got a message to update my Nextcloud to v32.0.8. As always I tried to do so via web browser. In the updater, the first two steps go well (“Initializing” and “Check for expected files”), but the third step fails (“Check for write permissions”). It says (please see screenshot):

“The following places can not be written to:

• nohup.out”

This error has never happened before. All the updates always went smoothly without error.

In PuTTY there is no issue with nohup. When I use it with some given shell script, e.g. the command cat output.txt works just fine.

I don’t recall changing anything in the installation or in NextcloudPi that could have caused the error.

I’d be glad if you could help Thanks in advance!

I’m happy to provide further information if needed.

Steps to replicate it (hint: details matter!):

1. Go to NC-Dashboard

2. Open Administration settings

3. In Administration > Overview, click Open updater

4. Click Start update

[Siggi0904]

Nextcloud Update (The following extra files have been found: nohup.out)

Nextcloud version : 20.0.4 Operating system and version : NextCloudPi 1.34.7 The issue you are facing: Update current instance to a new Nextcloud version Nextcloud Updater [X] Check for expected files The following extra files have been found: nohup.out Does anyone know a solution to the problem? I am relatively new to the topic Nextcloud

[Paddraigh_O_Sullivan]

The updater checks for files that are not part of the Nextcloud distribution and blocks if it finds any. nohup.out is just a leftover log file from a background process that was started with nohup at some point - it landed in the Nextcloud root directory by accident. SSH into your NextcloudPi box and delete it: sudo rm /var/www/nextcloud/nohup.out (adjust the path if your installation directory is different). Then retry the update from the web browser and it should get past that check. If you want to prevent it happening again, make sure any nohup commands you run from the terminal have their working directory set to somewhere outside the Nextcloud folder first.

[fromagecloud]

Thanks for your kind and quick responses!

@Paddraigh_O_Sullivan: Please note that nohup.out sat in /var/www/nextcloud/config. I do not know how it got there. I had not used nohup ever before.