@andirahmat yes, block storage is the correct thing to use for app data directory. But even in block storage, some filesystems like CIFS are not suited (since they don't have permissions and symlink support either). Of course, other filesystems like FAT, NTFS etc are totally out of question.
I made sure to remove the queued adhoc tasks before updating to prevent that from happening and users receiving notifications of past events. At least you now know that adhoc tasks are working again in your installation 😆
Thankfully in my case I don't yet actually have any users. I just installed to have a play around (because I do have plans to run some online courses) and haven't even really got around to doing that yet
@rost I think there is a bug in our migration script. If you open /app/data/moodle/config.php, there will be a line $CFG->auth = 'ldap'; . Can you delete that line and try if it works after that? You will have to refresh the browser page.
Also, the LDAP details you see pre-filled are the Cloudron LDAP (172.18.x.x is the internal server/docker network). If you want to disable LDAP, please start afresh. We only support setting the LDAP flag at install time. It cannot be changed post installation (this is a limitation across all apps at this moment).
@martinkbs Ah, I missed it that it's trying to transfer the database. Indeed, postgresql is the internal name. There is no public endpoint. What you have to do is to export the postgresql dump from the old instance and import it into Cloudron by hand. Please see https://docs.cloudron.io/guides/import-postgresql/
@imc67 I've published a new package which sets the getremoteaddrconf now correctly.
Since we only have one reverse proxy, the second setting was not needed in my tests. So this is untouched by default.