Owncloud not working after fresh install

[tobias-frajka]

Hi everyone, I freshly installed latest UCS server with iso on my server, went ahead and installed owncloud.
Installation went fine, but i cant join it, as its always: ERR 503 Service Unavailable
I went ahead and looked at docker logs, because i couldnt find anything why it shouldnt work and found that the main owncloud container is stuck at restarting and in the logs it says:

/etc/entrypoint.d/05-univention-env.sh: line 33: export 'ldap_server_sasl_oauthbearer_trusted-authorized-party_ucsserver.masdvory.intranet=https:/ /ucsserver.masdvory.intranet/univention/oids/': not a valid identifier

I cant find any help on how to continue further. Any help appreciated.
Thank you

PS: the space in the error was intentionally added for the code block to not take it as a comment

[paulrbarnard]

Following a power outage resulting in a disk failure I’ve reinstalled from scratch and have the same issue. Anyone have any suggestions?

[riasw]

We are facing the same issue. Could you find a solution?
Thank you

[PPChris]

Hello everybody,

I seem to have a similar (the same?) problem. After a fresh installation of UCS 5.0-8 and installing all updates, I installed ownCloud. Unfortunately, it does not start up. Accordung to docker ps -a, the container is stuck in restarting. Browsing to <IP address>/owncloud gives 503 Service unavailable.

There is a version of UCS that comes directly with ownCloud installed (download here). I tried this one, but face the same problem.

Does anyone have an idea how to solve this? As there is hardly anything to be configured during the installation process, I assume that this is rather a bug than a layer 8 problem. Any ideas are highly appreciated.

PPChris

[PPChris]

I should maybe add that the diagnosis shows the following:

The owncloud listener has 4 unprocessed files. (translated to English with DeepL)

Unfortunately, I have no idea what to do with this information.

PPChris