@sponch Yes, good point. I had raised the limit a while ago for different reason. Will update guide though with a hint to this.

@james I haven't used it too much today, but noone else complained either, so I think it's working fine at the moment. I'm not sure if creating the folder was the only thing that was needed, I also killed the cleanup process once and restarted a few times, but most likely the mkdir and chown brought it back

Hello @jdaviescoates Just ignore it for now. Currently working on another Nextcloud update, https://forum.cloudron.io/post/130292 With that released there will be a new update anyway which should fix your issue.

@james Thanks a lot and sorry for not mentioning that the external storage support app was enabled.

This problem was driving me mad. May have discovered a solution for the problem when App not syncing to cloud but could to app work's. I also run Grapheneos and the change that makes notes sync again was grating the application contracts permission. Didn't do deeper testing so far I just started to work again after that change

Viva la LLM: The container is healthy now — 1 running, 0 unresponsive. The Cloudron update worked: - New image: cloudron/com.nextcloud.cloudronapp:202607231345050000 - Nextcloud: 34.0.2 (up from 34.0.1) - user_oidc: 8.10.1 — working! How extensions should be updated in Nextcloud under Cloudron The proper way is: 1. occ app:update — updates from Nextcloud app store to /app/data/apps/ (persistent across restarts) 2. Nextcloud web UI → Apps — same effect 3. Cloudron app package update — what you just did; the vendor bundles newer versions in the image The root issue was that the old image (202606251555380000) bundled user_oidc 8.3.0 which had max-version="33" — incompatible with Nextcloud 34. The startup script's $occ user_oidc:provider command couldn't register. The data volume still had our manually-installed 8.10.1 from earlier. The new image (202607231345050000) likely bundles a compatible version, or my 8.10.1 on the data volume is now taking effect.

Thanks a lot for your support we will discuss in our team how to proceed but with your help, the way look promising.

@sponch said: they have (in Browser). Got it already running on a test VPS Good to know, thanks! That's one of the few limitations of OnlyOffice. It mostly doesn't bother me, but there are occasions where mobile editing would be handy.

Hello @da5nsy Yes as soon the update is validated by us the update will be available for everyone.

https://forum.cloudron.io/post/74532 and https://forum.cloudron.io/post/74973 Too many times it‘s just this browser…

Hello @ntnsndr Best to use the occ to uninstall the app and then try to install it again. If this does not resolve the issue you might have to report this in the nextcloud forum or the GitHub of the polls app directly.

Hey there, since package 5.8.1 the drag'n'drop bug is gone. Thx!

There's many hits for "Could not acquire a shared lock on the config file" on the forum (most of them leading to nothing)

so you are referring to sieve rules support I guess if I read that issue correctly. Have you configured sieve in your nextcloud? Since the nextcloud mail app is acting like a webmail client, you have to configure that by hand I assume.

Marked as solved due to inactivity from the author.

The well-known is usually served up by the main domain (example.com) so for a start if your nextcloud is installed on a subdomain, the well-known needs to be configured outside this nextcloud instance. So make sure to have an app installed at example.com so it gets routed to Cloudron. Then you can configure this via https://docs.cloudron.io/domains#well-known-locations Though not exactly sure if this nextcloud app would expect the same things as mastodon, but you can try to set the well-known mastodon accordingly, maybe that works. Otherwise we may have to add support for whatever this needs.

Hello @firmansi Thanks for the report. Then I have to assume that it is some Nextcloud third party app issue with the latest update.

Thanks for your reply! I guess we'll just keep the existing users on oidc then. Or maybe, if they're willing to, they can migrate manually. Most shares and other tools (collectives, calendars) are shared via groups, not link.

@sponch thanks for the reminder