Upgrade from 31.0.12 to 32.0.3 - LDAP Problems; Webserver stucks

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

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.12
  • Operating system and version (e.g., Ubuntu 24.04):
    • debian 12
  • Web server and version (e.g, Apache 2.4.25):
    • nginx1.29.4
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • nginx1.29.4
  • PHP version (e.g, 8.3):
    • 8.2.30
  • Is this the first time you’ve seen this error? (Yes / No):
    • no
  • When did this problem seem to first start?
    • some upgrades ago
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • carsten rieger install script / bare metal
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • mod_security

Summary of the issue you are facing:

I want to update, but it looks like the LDAP connection is causing serious problems here, so I can no longer use the server…

Since a few updates, I can no longer configure/edit LDAP, only via occ.

As soon as I deactivate LDAP, I can update and the server is accessible, but when I reactivate it, the server crashes.

I have also tried deleting the configuration and recreating it… but I am unable to do so. The data is not checked, transferred, etc.

I am unable to proceed.

I suspect that I will have to rebuild the server.

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

  1. upgrade from 31.0.12 with my ldap config

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.

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 15:01:11

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 14:34:24

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 14:34:24

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/discovery

09.01.2026, 14:20:24

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/discovery

09.01.2026, 14:20:24

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/capabilities

09.01.2026, 14:20:14

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/capabilities

09.01.2026, 14:20:14

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 14:20:04

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 14:20:04

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 13:34:40

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 13:34:40

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/discovery

09.01.2026, 13:20:21

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/discovery

09.01.2026, 13:20:21

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/capabilities

09.01.2026, 13:20:11

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/capabilities

09.01.2026, 13:20:11

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 13:20:01

Warnung
no app in context
System config option "blacklisted_files" is deprecated and will be removed in Nextcloud 34, use "forbidden_filenames" instead.

09.01.2026, 13:20:01

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/discovery

09.01.2026, 12:15:22

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/discovery

09.01.2026, 12:15:22

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/capabilities

09.01.2026, 12:15:12

Fehler
richdocuments
ConnectException
cURL error 28: Connection timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sub.domain.de/apps/richdocumentscode/proxy.php?req=/hosting/capabilities

09.01.2026, 12:15:12


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

Enabled:

  • activity: 5.0.0-dev.0
  • admin_audit: 1.22.0
  • app_api: 32.0.0
  • bruteforcesettings: 5.0.0-dev.0
  • circles: 32.0.0
  • cloud_federation_api: 1.16.0
  • collectives: 3.4.0
  • comments: 1.22.0
  • contactsinteraction: 1.13.1
  • dashboard: 7.12.0
  • dav: 1.34.2
  • federatedfilesharing: 1.22.0
  • federation: 1.22.0
  • files: 2.4.0
  • files_antivirus: 6.1.0
  • files_downloadlimit: 5.0.0-dev.0
  • files_pdfviewer: 5.0.0-dev.0
  • files_reminders: 1.5.0
  • files_sharing: 1.24.1
  • files_trashbin: 1.22.0
  • files_versions: 1.25.0
  • firstrunwizard: 5.0.0-dev.0
  • groupfolders: 20.1.6
  • integration_ews: 1.0.37
  • logreader: 5.0.0-dev.0
  • lookup_server_connector: 1.20.0
  • nextcloud_announcements: 4.0.0-dev.0
  • notifications: 5.0.0-dev.0
  • notify_push: 1.2.2
  • oauth2: 1.20.0
  • password_policy: 4.0.0-dev.0
  • photos: 5.0.0-dev.1
  • privacy: 4.0.0-dev.0
  • profile: 1.1.0
  • provisioning_api: 1.22.0
  • quota_warning: 1.22.0
  • recommendations: 5.0.0-dev.0
  • related_resources: 3.0.0-dev.0
  • richdocuments: 9.0.2
  • richdocumentscode: 25.4.702
  • serverinfo: 4.0.0-dev.0
  • settings: 1.15.1
  • sharebymail: 1.22.0
  • spreed: 22.0.7
  • support: 4.0.0-dev.0
  • systemtags: 1.22.0
  • tables: 1.0.2
  • text: 6.0.1
  • theming: 2.7.0
  • twofactor_backupcodes: 1.21.0
  • updatenotification: 1.22.0
  • user_ldap: 1.23.0
  • user_status: 1.12.0
  • viewer: 5.0.0-dev.0
  • webhook_listeners: 1.3.0
  • welcome: 1.4.0
  • workflowengine: 2.14.0
    Disabled:
  • calendar: 6.1.4 (installed 6.1.4)
  • contacts: 8.2.0 (installed 8.2.0)
  • encryption: 2.20.0
  • files_external: 1.24.0
  • files_retention: 3.0.0 (installed 3.0.0)
  • files_rightclick: 0.15.1 (installed 1.6.0)
  • survey_client: 4.0.0-dev.0 (installed 1.10.0)
  • suspicious_login: 10.0.0-dev.0
  • twofactor_gateway: 2.0.0 (installed 2.0.0)
  • twofactor_nextcloud_notification: 6.0.0-dev.0
  • twofactor_totp: 14.0.0
  • weather_status: 1.12.0 (installed 1.2.0)

What do you mean precisely by “crashes”?

What happens when you do so?

I note you’re using mod_security. Is that properly disabled for Nextcloud? It’s possible that’s the culprit.

Hello,
Sorry for the late reply… but I don’t work on weekends :slight_smile:

I tried several times, but I always got the message “The website cannot be reached… Error code from browser xxx.” or :Internal Server Error. The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Now I “only” get the message from Nextcloud

I tried it now again several times and get always another end :slight_smile:

LDAP configuration in Nextcloud no longer works. This means that I can no longer see or change any configurations in the WUI.
I can only make adjustments via occ.
In general, it is still possible to retrieve the LDAP data.

Check your nextcloud.log while the problem is occurring (i.e. when the internal server error comes up). The JAERB* request ID in the error message (from your screenshot) is logged so you can see what is going on.

Hi,
I think I will create a new server and will migrate then to the new.
There are some issues like LDAP… I will switch to PHP8.3, the storage will be increased and some other things…
In this case I think it is easier to migrate.
If the migration wont work, I will let you know… because I have to fix the mentioned issues :smiley:

Many thanks for your help!!!