Error: This app cannot be enabled because it makes the server unstable

[mhzawadi]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

1. Update to v28.0.2 of nextcloud
2. deisble the Group folders app
3. try to enable Group folders app

Expected behaviour

The app should be enabled

Actual behaviour

An error message is shown, but it looks to be enabled anyway

Server configuration

Operating system:
Debian 11

Web server:
Nginx/PHP-FPM

Database:
10.5.21-MariaDB-0+deb11u1 - Debian 11

PHP version: 8.3

Nextcloud version: (see Nextcloud admin page)
28.0.2

Group folders version:
16.0.3

Updated from an older Nextcloud/ownCloud or fresh install:
Update from 27.1.5

Where did you install Nextcloud from:
nextcloud zip archive

Are you using external storage, if yes which one: local/s3/smb/sftp/...
S3 for some users

Are you using encryption: yes/no
no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/Saml/...
No

Client configuration

Browser:
Opera One(version: 107.0.5045.15) (x86_64)
Operating system:
MacOS 13.6.3 (22G436)

Logs

Web server error log

Web server error log

No logs for group folders

Nextcloud log (data/nextcloud.log)

Nextcloud log

No logs for group folders

Browser log

Browser log

No logs for group folders

[joshtrichards]

No logs for group folders

I can't reproduce this and no one else has reported it. I suspect something else is going on here. Logs are needed to confirm.

The stack trace/log entry may not directly mention groupfolders (other then buried deeper within the trace).

Can you share a couple of the log entries that appear during the time period when you try to enable the app?

[joshtrichards]

I suppose it could be related to whatever is going on in #2796. I tested on v28 not upgrading a v27 instance to v28. Though I'd still expect more reports.

[mhzawadi]

I have set the log level to debug and disabled and re-enabled, I still get the error. But no logs in the nextcloud log at all.

maybe close this as it could be something else in my setup 😞

[quenenni]

Hello,

I have (I think) the same problem since I upgraded a cloud from v27 to v2804.
All my tries to enable an app result in this same error msg.

I did the same cloud upgrade couple days ago on another server and the clouds don't have any problems.

The main difference between the 2 setups is I'm using Haproxy in front of Nginx on the one with the error.

Can't this problem be related to new headers haproxy needs to be passing to Nginx?

I don't know if @mhzawadi is also using a proxy.

I can see the request in the Nginx log file:

x.x.x.x - - [05/Apr/2024:15:25:30 +0200] "POST /settings/apps/enable HTTP/2.0" 200 52 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0" "-" "cloud.yyyyy.be"

But nothing in Nextcloud logs (with loglevel to 0).

In the Firefox console, I have this error everytime I try to enable an app:

Content-Security-Policy : Les paramètres de la page ont empêché le chargement d’une ressource à https://cloud.yyyyy.be:4431/apps/files/ (« connect-src »).

[EDIT]
I forgot to mention that I can without problems enable all the apps with the occ command and they are working fine in the cloud.
It's only about enabling them the problem.

[gjwgit]

I just encountered the same issue on Ubuntu 24.04 (client) and Ubuntu 22.04 (server) with groupfolders 16.0.6, snap install of the nextcloud 28.0.6snap1 server.

Seems like Group Folders got disabled overnight with an upgrade. On one server I was able to re-enable Group Folders through the browser interface. On another server I got the This app cannot be enabled because it makes the server unstable Error and had to sudo nextcloud.occ app:enable groupfolders which worked just fine.

[joshtrichards]

If occ approach works fine and only web app management is impacted: nextcloud/server#44685 maybe?