Cloudron Forum

Thank you @nebulon for solving this issue off-forums.

For future reference: problem was caused by the external storage being unmounted after a reboot. Remounting the storage drive (I use a netcup VPS) and then repairing in the Cloudron dashboard solved the problem. Including the mounting in /etc/fstab solved this issue for following updates/reboots.

@fbartels Indeed! I changed the title accordingly.

@msbt Thank you immensely! I've been trying to get that to work for ages.

@nebulon Could https://git.cloudron.io/cloudron/nextcloud-app/issues/61 be related?

@girish damn, thanks.

I'll add something there too.

I dont see how this can be supported by nextcloud, unless it would scan the authors inbox. Maybe the nextcloud email addon is able to handle this, but you should probably ask nextcloud support about this.

As a first attempt, you could try to restart the box process with systemctl restart box Also maybe look at the system logs, in case there are any hints for errors.

The update to 15 is pushed out now. Please report any issues you encounter if that is the case.

@avatar1024 said in how can I use the Cloudron Groups in Nextcloud?:

are Cloudron groups not LDAP

Yes, Cloudron groups are not in LDAP currently. Currently, if you want to restrict to a group, you can do this already. But if you want groups to sync, that's not implemented. Feel free to open up a feature request to implement this and we can guage the interest.

Have pushed an update that enables this.

You were right. "unbound" was failed. Turns out IPV6 was disabled which was causing "unbound" to fail and in turn causing the issues with resolving domain names in Nextcloud. This is a vanilla install of Ubuntu 16 LTS so I'm not sure what happened. I enabled IPV6 and rebooted and everything started working. Thanks for the tip.

just an update, the syntax for the psql variables has changed, so the conversion script looks like this:

sudo -u www-data php occ db:convert-type \ --password ${CLOUDRON_POSTGRESQL_PASSWORD} \ --clear-schema --all-apps pgsql \ ${CLOUDRON_POSTGRESQL_USERNAME} \ ${CLOUDRON_POSTGRESQL_HOST} \ ${CLOUDRON_POSTGRESQL_DATABASE}

you must run this from within the nextcloud container.

also, I had some dificulties with the mysql migration, the temp mariadb/mysql docker container should match the same type and version as the source. In my case src had mariadb 10.5, so the container from the code sample above (mariadb 10.1) throw some strange errors while importing the sql dump.

Lets further handle this in the opened issue tracker item.

In case, you find this post by search, there is doc on how to set this up here - https://cloudron.io/documentation/apps/nextcloud/#email

In case, you find this post by search, there is doc on how to set this up here - https://cloudron.io/documentation/apps/nextcloud/#email

@yylevas No worries! Glad you found the problem. Breaking stuff is the fastest way to learn!