@jdaviescoates Ah already done. Upvoted then. Thanks

I seem to remember you need to Activate a "Login" plugin, there's normally a notification that says that.

@nebulon hmmm yeah I could see the potential for extra work, but as long as the css for the ldap plugin doesn't change too much I'd imagine it would a "build it once and forget about it" situation. That said, adding the option to disable the ldap UI for non-admins is a no-brainer I'm sure for Nextcloud programmers.

@ctrl Cloudron package uses apache + mod_php. The high CPU load issue is probably because of something else. # apache2ctl -M AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.24. Set the 'ServerName' directive globally to suppress this message Loaded Modules: core_module (static) ... php7_module (shared) ...

That is totally possible, just make sure to transfer the admin status over to another account first.

Yes the main issue is mostly related to Nextcloud addons. Basically with every release something breaks. Ideally it should not bring down Nextcloud as a whole but just disable that addon, but that is not how it is implemented. Things just crash unfortunately.

FWIW, it's in our TODO list for 6.0 to optimize nextcloud and wordpress installations.

I'll mark this as solved. The takeaway is to use the connector nextcloud apps/plugins, then it works.

19.03 is out with the following changes: Fix possible leaking scope in Flow (server#22410) Combine body-login rules in theming and fix twofactor and guest styling on bright colors (server#22427) Show better quota warning for group folders and external storage (server#22442) Add php docs build script (server#22448) Fix clicks on actions menu of non opaque file rows in acceptance tests (server#22503) Fix writing BLOBs to postgres with recent contacts interaction (server#22515) Set the mount id before calling storage wrapper (server#22519) Fix S3 error handling (server#22521) Only disable zip64 if the size is known (server#22537) Change free space calculation (server#22553) Do not keep the part file if the forbidden exception has no retry set (server#22560) Fix app password updating out of bounds (server#22569) Use the correct root to determinate the webroot for the resource (server#22579) Upgrade icewind/smb to 3.2.7 (server#22581) Bump elliptic from 6.4.1 to 6.5.3 (notifications#732) Fixes regression that prevented you from toggling the encryption flag (privacy#489) Match any non-whitespace character in filesystem pattern (serverinfo#229) Catch StorageNotAvailable exceptions (text#1001) Harden read only check on public endpoints (text#1017) Harden check when using token from memcache (text#1020) Sessionid is an int (text#1029) Only overwrite Ctrl-f when text is focussed (text#990) Set the X-Requested-With header on dav requests (viewer#582)

One option here is to create a new empty folder on that external disk, then move a freshly installed Nextcloud instance to that folder. Once that is done, you can move the existing files on the same disk into that folder into the expected subfolder for the Nextcloud user you want to files to be present.

well that was months ago, so they had that problem before that as well

@girish Here you go. No answer yet. https://help.nextcloud.com/t/sending-calendar-invite-from-nextcloud-user-email-addresses-with-character-does-not-work/89220 If I don't get an answer I might post it in the GitHub repo, as I don't think it's something a user can fix.

@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.