@dfldadm Something to try might be to disable any plugins you have installed and see if it helps. Does reverting to the previous backup sort out the issue? If so, what you can do is something like this: make a backup of the app in it's current state. revert to nc 18, so you have it all working again disable automatic updates for the app create a clone from nc from the backup of step 0 to another location. use this to experiment with plugins and various commands to figure out what the issue is.

@Bortseb Yeah, best way to get familiar eh! Always worth making up your own mind, I just added in case you were a disappointed once you did get connected and to be aware what I think at least is worth your time on setups, as I know from years of System Admin for a team of about 50, they can often only be as quick or organised as the tools we give them.

@girish said in Nextcloud 19: sudo -u www-data php -f /app/code/occ db:add-missing-columns Perfect, that did the trick! No more warnings in Nextcloud Settings.

Just leaving a note for myself, but it's unclear why the issue got fixed after the update. After an app update, the container is recreated and the collectd config is regenerated. Maybe the collectd restart did the trick.

This is resolved in https://git.cloudron.io/cloudron/nextcloud-app/-/issues/80 we are still not very sure about pushing the latest version due to db migration issues.

@seeker Sorry - Maybe we are using too new a nextcloud ver? Some nextcloud apps only work with certain versions.

Thanks. I'm mostly happy just using Nextcloud Text, but may well have a look at playing with Notes + QownNoted too...

@girish said in Should I chown the new path of my data ?: @JOduMonT said in Should I chown the new path of my data ?: may I delete the old empty directory /home/yellowtent/appsdata/7dd8e169-9efb-485c-9cee-7053e0312360/ ? You should not delete this. This directory is used to storing the database dumps when taking app backup. OK good I didn't deleted it @nebulon said in Should I chown the new path of my data ?: That error looks a lot more like a database constraint error. In this case it appears you already have an app configured on that dataDir? yes but than, when I went into my. cloudron the path disappear and when I look a via the console, a new set of data was inside /home/yellowtent/appsdata/7dd8e169-9efb-485c-9cee-7053e0312360/ while my mount point /mnt/nextcloud/data was accessible between the configuration and the error message I had the reboot the server because of ubuntu security update has cloudron asked me.

@nebulon said in Does anybody use the plugin LDAP write in Nextcloud ?: That is correct, our ldap server does not allow any modification or writes to the user directory. that is smart, because it is so easy to mess with LDAP

@rcdncn Thanks. I have pushed your notes to our docs at https://cloudron.io/documentation/apps/nextcloud/#skeleton-directory

Good that it works now. For clarification, an app restart will reset all Cloudron specific settings, in case they were misconfigured or more importantly in case the information has changed on the Cloudron side (like a password, port or secret)

@jdaviescoates said in nextcloud-hub: As I understand it "Nextcloud Hub" is really just Nextcloud + Nextcloud apps + OnlyOffice This is my understanding as well.

All iPhones and Macs at our end.

My problem seems to stem from incorrectly thinking Nextcloud calendars and contacts use Push, but they use Fetch and the default schedule on Macs and iOS devices is 15 minutes.

@christiaan Yes, it's mostly harmless. https://github.com/nextcloud/server/issues/13556 is the bug upstream. Looks like they will fix it soonish (there is some recent activity).

We've pushed a package update just now to fix this.

Thanks nebulon. For anybody following this, I did have to install the apps to get sync up and running properly. The automated configuration file didn't work for some reason. At the very least I had to follow these instructions precisely (including making device-specific passwords): https://docs.nextcloud.com/server/18/user_manual/pim/sync_osx.html

@girish The update for Cloudron was installed now, then the location in the Nextcloud app was saved again. Now it is error-free. Thanks for your personal support!

Hi, I am interested in using Object Storage for Nextcloud primary storage as well. Currently, an object storage provider can only be added as external storage. It would be great to be able to configure some s3-compatible Object Storage, which costs much less and can be more durable than Volume, as the primary storage. As I understand it, this is not yet possible in Cloudron. Would it be possible to enable this option?