Cloudron Forum

@jdaviescoates so here is my config which works well and gets around the admin group issue.

In the OIDC NC app config:

Then you create a group folder per NC group, and when you add a user to Cloudron and add to a specific Cloudron group, it gets automatically added to the corresponding MC group and gets access to the group folder associated with that group.

In addition, in order not to confuse users with the NC login form I now disable other login methods using this command: occ config:app:set --value=0 user_oidc allow_multiple_user_backends

and set a custom end point to my Cloudron dashboard when people try to log out of Nextcloud:

Here is what I see when I press the update button manually:

Auto-updates are enabled, yet the app does not auto-update. And this is the case on two different instances. In fact it also does not update automatically from 32.0.0 to 32.0.1.

Yes the update now works directly from version 31.0.9 to 32.0.1. However, FYI, updating to 32.0.1 does not happen automatically and is still marked as a "pre-release and not considered stable yet". If this is intended just ignore me, but thought I'd let you know in case that was oversight (given that was not even the case when 32.0.0 got pushed).

@girish on my instances NC still tries to first update to 32.0.0 despite 32.0.1 having now been pushed.

@james Thanks for explaining how to package how own version, that's really good to know in general!

@shrey Just to say, I don't think the dev doesn't favour stable versions. Most versions are stable on the repo, it's just that there is major update coming (v1.0) and so they've released a few RC before release it stable, but that's pretty standard practice.

@jdaviescoates said in how can I use the Cloudron Groups in Nextcloud?:

Ideally anyone on the Cloudron who is in the west-dorset-commons Cloudron group would automatically also have access to the West Dorset Commons folder within Nextcloud - has anyone found a way to do that yet?

Yes I've got that working. I can't write now but I'll get back to you shortly.

@staff quick question. When Nextcloud 32.0.1 gets released, will it be possible to update directly to it for those instance that are still on NC31, skipping 32.0.0?

Looks good! Is this something that needs to be integrated to Cloudron itself, or as a separate app?

@jdaviescoates said in Should MiroTalk SFU work well for 6-10 people?:

What ports are you using?

I have the same set-up as you, Netcup + Cloudron and MiroTalk works fine. So you're saying this didn't help? If not, then can you describe a bit more what you see? Do you see wheel spinning as if the participant were trying to connect, or you don't see participants trying to enter the room at all?

@jdaviescoates For me it works very well with 3-5 people. I haven't really tried with more than that. Though according to MiroTalk Discord it seems to be showing good performance on a same server as mine, i.e. a Netcup RS2000 (15€/month) with 25 participants!

Right so it's fixed on that broken. It turns out that for some reasons the ownership on many directories inside the NC data directory have been changed from www-data to yellowtent. This included the content of: data/appdata_{instanceid}/appstore/ which looked like:

drwxr-xr-x  3 yellowtent yellowtent 4.0K Oct  2 12:55 .
drwxr-xr-x 19 www-data   www-data   4.0K Oct  2 12:55 ..
-rw-r--r--  1 yellowtent yellowtent  87K Oct  1 11:19 appapi_apps.json
drwxr-xr-x  5 yellowtent yellowtent 4.0K Oct  1 11:19 app-discover-cache
-rw-r--r--  1 yellowtent yellowtent 2.8M Oct  1 11:19 apps.json
-rw-r--r--  1 yellowtent yellowtent 161K Oct  1 11:19 categories.json
-rw-r--r--  1 yellowtent yellowtent 7.2K Oct  1 11:19 discover.json

...and which broke the App Store. Revering the permission to www-data made everything work right away.

But actually many directories are affected inside the appdata_{instanceid} directory as well as users files inside the data directory.

I'm going to do a good backup and put the app in maintenance mode before I change ownership every inside the data because it feels a bit scary.

@staff Any clues on how it happened??

@nebulon Is it somehow possible to reinstall the app with the same version (or rerun the update but without starting from an old backup)?

I do see this show up several times in the log when that nextcloud instance starts:

Healtheck error: Error: connect ECONNREFUSED 172.18.18.24:80

The issue is resolved on most of my instances but on one of them (also updated to NC32), many apps are still running in their older version and the whole app store seems broken. Discover page displays “Nothing to show”, I see no update available and I cannot install any new apps.

If I disable an outdated app and try to re-enable it, it throws an error and then the whole instance breaks (cannot starts any longer). Weirdly though, several of the outdated apps are active and running fine (e.g. calendar).

I have tried to disable all outdated apps, restarted the instance but still the app store seems broken and does not update anything.

See my list of app below (and see how calendar, groupfolders etc. are out of date):

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
  - comments: 1.22.0
  - contactsinteraction: 1.13.1
  - dav: 1.34.2
  - federatedfilesharing: 1.22.0
  - federation: 1.22.0
  - files: 2.4.0
  - files_downloadlimit: 5.0.0-dev.0
  - files_external: 1.24.0
  - files_pdfviewer: 5.0.0-dev.0
  - files_reminders: 1.5.0
  - files_sharing: 1.24.0
  - files_trashbin: 1.22.0
  - files_versions: 1.25.0
  - firstrunwizard: 5.0.0-dev.0
  - 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
  - oauth2: 1.20.0
  - password_policy: 4.0.0-dev.0
  - privacy: 4.0.0-dev.0
  - profile: 1.1.0
  - provisioning_api: 1.22.0
  - recommendations: 5.0.0-dev.0
  - related_resources: 3.0.0-dev.0
  - serverinfo: 4.0.0-dev.0
  - settings: 1.15.1
  - support: 4.0.0-dev.0
  - survey_client: 4.0.0-dev.0
  - systemtags: 1.22.0
  - text: 6.0.0-dev.0
  - theming: 2.7.0
  - twofactor_backupcodes: 1.21.0
  - updatenotification: 1.22.0
  - user_oidc: 7.4.0
  - user_status: 1.12.0
  - viewer: 5.0.0-dev.0
  - weather_status: 1.12.0
  - webhook_listeners: 1.3.0
  - workflowengine: 2.14.0
Disabled:
  - accessibility: 1.10.0
  - appointments: 2.4.6 (installed 2.4.6)
  - calendar: 5.5.3 (installed 5.5.3)
  - carnet: 0.25.6 (installed 0.25.6)
  - collectives: 3.1.2 (installed 3.1.2)
  - contacts: 7.3.0 (installed 7.3.0)
  - cookbook: 0.11.3 (installed 0.11.3)
  - dashboard: 7.12.0 (installed 7.1.0)
  - deck: 1.15.2 (installed 1.15.2)
  - drawio: 3.1.0 (installed 3.1.0)
  - encryption: 2.20.0 (installed 2.8.1)
  - end_to_end_encryption: 1.17.0 (installed 1.17.0)
  - event_update_notification: 2.6.1 (installed 2.6.1)
  - files_rightclick: 1.6.0 (installed 1.6.0)
  - files_videoplayer: 1.13.0
  - fileslibreofficeedit: 2.0.1 (installed 2.0.1)
  - forms: 5.1.2 (installed 5.1.2)
  - groupfolders: 19.1.3 (installed 19.1.3)
  - integration_whiteboard: 0.0.14 (installed 0.0.14)
  - mail: 5.4.0 (installed 5.4.0)
  - notes: 4.12.3 (installed 4.12.3)
  - notify_push: 1.2.0 (installed 1.2.0)
  - passwords: 2025.7.20 (installed 2025.7.20)
  - photos: 5.0.0-dev.1 (installed 5.0.0-dev.1)
  - polls: 8.4.6 (installed 8.4.6)
  - previewgenerator: 5.10.0 (installed 5.10.0)
  - quicknotes: 0.8.30 (installed 0.8.30)
  - richdocuments: 8.7.4 (installed 8.7.4)
  - richdocumentscode: 25.4.403 (installed 25.4.403)
  - sharebymail: 1.22.0 (installed 1.22.0)
  - suspicious_login: 10.0.0-dev.0 (installed 10.0.0-dev.0)
  - twofactor_nextcloud_notification: 6.0.0-dev.0
  - twofactor_totp: 14.0.0
  - user_ldap: 1.23.0 (installed 1.21.0)

Any help would be greatly appreciated at this stage. I’m ran out of ideas.

@marcusquinn said in Nextcloud update pushed too early?:

Not entirely sure how we ended up getting updates to v32.0.0, when I thought the Cloudron policy was to wait until 0.01 or 0.02 for whole version increment stability confirmation?

Probably just a mistake. But yes, @everyone, definitely be careful with this update. Even with the now functioning app store, I have some instance which have been able to update all apps and are now working fine on NC32, while others don't see any app updates and most apps are broken, and when trying to do play around with it, it broke Nextcloud completely.

Backup and restore to an earlier version works fine to resolve this.

Thought the two issues might be related in that during the update process maybe Nextcloud cannot pull the updated versions of the installed apps is the app store is down. Restoring from previous version of the app should solve this particular issue though. I'm just backing up now and will attempt a restore.

It's a different issue. In that other forum thread people have reported the app store is not available, indeed on Nextcloud side, and while annoying not a deal breaker. What I am reporting here is that an already installed app is dysfunctional, and a pretty major one which cause a loss of access to files.

Hello, servers got updated to NC 32 this morning, but there are a number of app missing, especially "Group folders" which basically means people have lost access to their files. Don't you normally wait for the first point release?