Cloudron Forum

Just for info, another instance auto updated last night from 8.3.2 to 9.0.13 and something weird happened: I got the same error on the backup site (with two failed backup notifications) AND that backup site got duplicated into a new one but for some reasons as a tar archive instead of rsync like the original site. No idea what happened there.

@joseph how come as this been marked as solved? There have been no response and it clearly wasn't as of 9.0.12.

@robi I agree this isn't Ideal, especially when you have lots of notifications.

Same here when upgrading from 8.3.2 to Cloudron 9.0.12. Remounting storage solves it, but still not optimal as a default behaviour.

I agree Zulip would really be a great addition. Best out of all of them.

Oh that is sad...

Is there any follow-up on this by any chance? @jdaviescoates

@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)?