@robi Looks like non-cloudron users hit the same issue - https://github.com/nextcloud/server/issues/13556#issuecomment-848314122

The root cause is that the nextcloud package is configured to log to the console (stdout / stderr) instead of a file. Nextcloud tries to open the stdout/stderr and this fails. Ideally, nextcloud can show a graceful error message that logs cannot be viewed from inside the app because it is logging to the console. Workaround is to use the cloudron logs viewer to view the logs - which IMO is the correct place to view logs (for all apps and not just nextcloud). After all, if the app is not working, one cannot view the logs within itself.

@murgero Thank you Before seeing this, I decided to be a 'windows user' and reboot the cloudron server. I guess same effect, but will definitely do your more limited kick next time. And yes it is working again. Many thanks

@nebulon Yep, thank you, confirmed it reset itself. Took >24 hours for recalculation but it is sorted

@necrevistonnezr right I was hoping for a --skip-plugins or equivalent but couldn't find one (the WP cli tool has something like that for skipping loading of themes and plugins).

Thanks All! I'll have to dig into this a bit further, but this gives me a good start.

@dylightful this may have to be fixe upstream then. Generally we have seen various issues with the Nextcloud encryption and additional addons together. I would recommend to not use the encryption with Nextcloud, since if anything goes wrong there, it is very hard or impossible to recover the data.

On focal, this seems to libmagickcore-6.q16-6-extra. I have added it for the next nextcloud package update.

@cloudron-n said in Obvious noob questions (apologies): does Cloudron keep NextCloud up to date? This is part of the magic that makes Cloudron such a great platform. Nextcloud is integrated This page describes how it works https://docs.cloudron.io/updates/

On Nextcloud, the data directory is /app/data. In hindsight, this was a mistake and it should ideally be /app/data/datadirectory or something. We tried to fix this long ago, but it was complicated since nextcloud complains if you change the data directory, so we left it as-is. Because of the above quirk, there are two htaccess files. One for the data directory itself (.htaccess) and one for the code directory (htaccess). When we eventually move the data directory to be a subdirectory, the .htaccess will move with it.

@bluxomat When creating an instance check the option as shown in the image below. [image: 1616694174227-755cffb2-90b6-44aa-9ab9-568d51deca0a-image.png] That way, when you log in with the admin user, the user quota option will appear

Did someone saw stable20 LDAP: make actually use of batch read known groups within the changelog? Nextcloud has LDAP group support but we were never able to use Cloudrons user groups. Any chance this could change now? EDIT: Hm okay maybe I'm on the wrong path. I always assumed you can map LDAP groups to groups within Nextcloud (to determine folder/access rights) but this seems not to be the case. Correct me if I'm wrong.

@nebulon The bug has been fixed in the current updated 20.0.8 version of cloudron! Thanks for a delightful experience. Edit: This thread can be marked solved I think.

@girish Yeah, I read that, and it seems to you setup Cron by default with the email settings anyway at: /settings/admin where the Test email button seems to work, so that part seems good. Notifications is a core/default App as I understand at: /settings/apps/installed/notifications This is what I have set here: /settings/user/activity [image: 1614037256003-81f3c895-c03e-4c96-bbe1-ef1431ddfd93-image-resized.png] And the folders are just the default and this extra shared folder: [image: 1614037320510-6e9f270e-3e2e-46bd-874a-4c69a7b0de64-image.png]

@enigma84 Access the htaccess from the File Manager and not directly on the server. It's better/easier that way - https://docs.cloudron.io/apps/#file-manager For nextcloud, you will (confusingly) see two files - htaccess and .htaccess. Do not touch .htaccess since it is for protecting the data directory (/app/data). You can try editing htaccess.

it sounds like they need to have a default feature added that disables plugins that have not been revved compatible with the current version. Keep the cloud running not the 'addons'.

@shai There may also be a plugin that does this too - it's worth trying to search on Nextcloud's own store-front for plugins.

@necrevistonnezr Ah gotcha, I misunderstood your original post.

@girish said in Should the URL of the "Social Nextcloud App" also change when you change the subdomain of "Nextcloud Cloudron app" ?: “cloud_url”: getenv('CLOUDRON_APP_ORIGIN'), “social_url”: getenv('CLOUDRON_APP_ORIGIN') . '/nextcloud/index.php/apps/social/”, I did edit ./config/config.php via de the file manager and add those to line 'cloud_url': getenv('CLOUDRON_APP_ORIGIN'), 'social_url': getenv('CLOUDRON_APP_ORIGIN') . '/nextcloud/index.php/apps/social/', but it didn't work So I dig a little bit more and found the solution here overwrite.cli.url have to be set properly (which Cloudron take care of) than do a reset /occ social:reset sudo -u www-data php occ which result with this "bug" so I'll wait to see