Nextcloud 32.0.1 Update is blocked by /updater/index.php

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Nextcloud 32.0.1
  • Operating system and version (e.g., Ubuntu 24.04):
    • Linux 6.1.0-0.deb11.21-amd64 x86_64
  • Web server and version (e.g, Apache 2.4.25):
    • Apache (Linux h2web368 64-bit #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1~bpo11+1 (2024-05-06))
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • replace me
  • PHP version (e.g, 8.3):
    • 8.4.10
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • when the automatic update is launched
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • replace me
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no

Summary of the issue you are facing:

  1. Warning: The use statement with non-compound name ‘CurlHandle’ has no effect in /home/clients/65af0ce9fb8dd59a3cd2c6055b66b2ae/stockage/updater/index.php on line 30 {“proceed”:true}
    Check for write permissions

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

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

Did you check the permissions?

The “open updater” is doing the same thing for me.

Says “check for write permissions”

Been using the updater for over a year. This is the 1st time it’s complained about permissions.

The permissions are ok

recognize installed?

1 Like

It is installed

Can you check your updater.log for clues?

The use CurlHandle; is actually a mistake in the code (I think), but it should just generate that warning and proceed I believe.

There are files from the Recognize app dated January 1, 2000. Nextcloud didn’t even exist back then.

All files for which there are no write permissions come from the recognize app.

2025-10-27T16:25:24+0000 GDASzFS6JX [info] request to updater
2025-10-27T16:25:24+0000 GDASzFS6JX [info] currentStep()
2025-10-27T16:25:24+0000 GDASzFS6JX [info] POST request for step “1”
2025-10-27T16:25:24+0000 GDASzFS6JX [info] startStep(“1”)
2025-10-27T16:25:24+0000 GDASzFS6JX [info] checkForExpectedFilesAndFolders()
2025-10-27T16:25:24+0000 GDASzFS6JX [info] end of checkForExpectedFilesAndFolders()
2025-10-27T16:25:24+0000 GDASzFS6JX [info] endStep(“1”)
2025-10-27T16:25:24+0000 eZsOuG9B2b [info] request to updater
2025-10-27T16:25:24+0000 eZsOuG9B2b [info] currentStep()
2025-10-27T16:25:24+0000 eZsOuG9B2b [info] Step 1 is in state “end”.
2025-10-27T16:25:24+0000 eZsOuG9B2b [info] POST request for step “2”
2025-10-27T16:25:24+0000 eZsOuG9B2b [info] startStep(“2”)
2025-10-27T16:25:24+0000 eZsOuG9B2b [info] checkWritePermissions()
2025-10-27T16:25:25+0000 eZsOuG9B2b [error] POST request failed with UpdateException
2025-10-27T16:25:25+0000 eZsOuG9B2b [error] Exception: UpdateException
Message:
Code:0
Trace:
#0 /var/www/nextcloud/updater/index.php(1421): Updater->checkWritePermissions()
#1 {main}
File:/var/www/nextcloud/updater/index.php
Line:398
Data:
Array
(
[0] => LICENSE
[1] => tf_status.h
[2] => c_api.h
[3] => c_api_experimental.h
[4] => tf_tstring.h
[5] => tensor_interface.h
[6] => c_api.h
[7] => dlpack.h
[8] => c_api_experimental.h
[9] => tf_attrtype.h
[10] => c_api_macros.h
[11] => tf_file_statistics.h
[12] => tf_tensor.h
[13] => tf_datatype.h
[14] => ctstring_internal.h
[15] => ctstring.h
[16] => THIRD_PARTY_TF_C_LICENSES
[17] => libtensorflow_framework.so.2.9.1
[18] => libtensorflow.so.2.9.1
[19] => libtensorflow_framework.so.2
[20] => libtensorflow_framework.so
[21] => libtensorflow.so.2
[22] => libtensorflow.so
[23] => LICENSE
[24] => trt_convert_api.h
[25] => tf_status.h
[26] => c_api.h
[27] => c_api_experimental.h
[28] => tf_tstring.h
[29] => tensor_interface.h
[30] => c_api.h
[31] => dlpack.h
[32] => c_api_experimental.h
[33] => tf_attrtype.h
[34] => c_api_macros.h
[35] => tf_file_statistics.h
[36] => tf_tensor.h
[37] => tf_datatype.h
[38] => ctstring_internal.h
[39] => ctstring.h
[40] => THIRD_PARTY_TF_C_LICENSES
[41] => libtensorflow_framework.so.2.9.1
[42] => libtensorflow.so.2.9.1
[43] => libtensorflow_framework.so.2
[44] => libtensorflow_framework.so
[45] => libtensorflow.so.2
[46] => libtensorflow.so
)

2025-10-27T16:25:25+0000 eZsOuG9B2b [info] rollbackChanges(“2”)
2025-10-27T16:25:25+0000 eZsOuG9B2b [info] unlink .step
2025-10-27T16:25:25+0000 eZsOuG9B2b [info] end of rollbackChanges()

new version of recognize seems to fix the problem:

Fixed

  • fix(FileListener): Address review comments

  • fix(FileListener): Address review comments

  • fix(FileListener): Listen to user mount events

  • fix(InstallDeps): Set write permissions on node_modules folder

  • fix(Classifier): Check cores against int value

  • fix(FaceDetectionWithTitle): Rename vector column to face_vector

3 Likes

Thank you!

2 posts were split to a new topic: Permission problems with upgrade to NC32 (without recognize app)

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.