Nextcloud 12.0.3-0 has been installed via UCS Apps
Custom proxying made with external domain
On first login Nextcloud blame that we need to add external domain as trusted
It is working
Today we have updated Nextcloud to 12.0.5-0 and immediately found that:
Altered config.php in directory /var/lib/univention-appcenter/apps/nextcloud/conf/config/ has been overwritten
The Nextcloud still blaming that external domain not trusted
After review we have found that there is an issue - Nextcloud (docker based) itself located in /var/www/html so its actual config is in /var/www/html/config/config.php
The UCS default binds do config and data mappings from/to /var/lib/univention-appcenter/apps/nextcloud/conf and /var/lib/univention-appcenter/apps/nextcloud/data while first should be /var/lib/univention-appcenter/apps/nextcloud/conf/config to /var/www/html/config
Custom entries should be kept, obviously, so this is a bug. I guess we should just do this once on install, and let any further changes be business of the admin. Too error prone. I opened a bug: https://github.com/nextcloud/univention-app/issues/46
But I cannot find /var/www/html/config/config.php to correct the trusted domains.
Entries in /var/lib/univention-appcenter/apps/nextcloud/conf/config/config.php do not work I still get the “not trusted domain” error when I try to access nextcloud from external.
The internal access https://local_IP/nextcloud/ works fine.
But every external access fails.
Where is the config.php to correct the trusted domais?
copy file to external host mount: “cp -p /var/www/html/config/config.php /var/lib/univention-appcenter/apps/nextcloud/conf/actual.conf”
now you may exit container and visit “/var/lib/univention-appcenter/apps/nextcloud/conf” on the host to compare/edit configs, then move it back (while being in container).
There are many ways how to do it, it is just one of them.
these two steps can be simplified. Univention offers the possibility to directly jump into the container by calling univention-app shell appname, so e.g. univention-app shell nextcloud.
If an editor is installed in the app then you could probably edit the file directly in place (but I had to run apt update && apt install vim the last time I had a deeper look at the nextcloud image.