Missing nextcloud vhost after package upgrade? (/nextcloud -> not found)

Version: 5.0-1 errata187
Nextcloud-Container: docker.software-univention.de/nextcloud:21.0.7-0
After a linux package update over the univention web interface the subpath /nextcloud isn’t working anymore.
i think the vhost config is gone away.

  • Is it possible to restore the apache vhost / reverse proxy configuration?
  • Is it possible to resolve the problem if i remove the app and install it again? IMPORTANT: Without losing the Nextcloud configuration and db-data?

Thanks for your help.

Tobias

Hey Tobias,

Nextcloud should appear in the file /etc/apache2/sites-enabled/default-ssl.conf like this:

/etc/apache2/sites-enabled/default-ssl.conf:    ProxyPass /nextcloud http://127.0.0.1:40000/nextcloud retry=0
/etc/apache2/sites-enabled/default-ssl.conf:    ProxyPassReverse /nextcloud http://127.0.0.1:40000/nextcloud

Can you try to rebuild the file with ucr commit /etc/apache2/sites-available/default-ssl.conf?
To check which apps should be exposed with this command you can have a look at /etc/univention/templates/files/etc/apache2/sites-available/ssl.d/10univention-appcenter: Inside is a Python script, if you copy the file and remove the @!@ marks you can run the script directly to check what the output would be.

Best regards
Jan-Luca

Hi Jan-Luca,

thanks for your quick reply.

I have checked that. It seems that the reverse proxy is/was correct. But i still get an error 404 on all nextcloud requests. it seems that this has something to do with the docker-container.

in Nextcloud container shell no request a logged in /var/log/apache2/access.log

But than I have detected that if I use the ip the access works:

10.100.10.105 - - [14/Jan/2022:14:31:26 +0100] "GET /nextcloud/status.php HTTP/1.1" 200 1695 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36"

but with the domain not?!

10.100.10.105 - - [14/Jan/2022:14:31:41 +0100] "GET /nextcloud/status.php HTTP/1.1" 404 1055 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36"

We have an alias dns entry for the server that is different to the ucs-hostname
with ucs hostname it works:

https://ucs.opc.local/nextcloud/status.php

but with public hostname it is not working any more:

https://ucs.<external-domain>.org/nextcloud/status.php

certificate (letsencrypt) is generated on external hostname.

I have done a test and config the alias hostname also in /etc/hosts - without success.

Where to look? Thanks for bringing me in the right direction.

Tobias

After some more testing. (try to install another app (wekan)) i got an error message:

24099 docker                           22-01-14 15:58:22 [   DEBUG]: Getting network for 4.4/wekan=5.78
 24099 docker                           22-01-14 15:58:22 [   DEBUG]: Found 172.16.1.0/24
 24099 utils                            22-01-14 15:58:22 [   DEBUG]: Running in /var/lib/univention-appcenter/apps/wekan/compose:
 24099 utils                            22-01-14 15:58:22 [    INFO]: Running command: docker-compose -p wekan up -d --no-build --no-recreate
 24099 utils                            22-01-14 15:58:23 [    INFO]: Creating network "wekan_appcenter_net" with the default driver
 24099 utils                            22-01-14 15:58:23 [    INFO]: Pool overlaps with other one on this address space
 24099 utils                            22-01-14 15:58:23 [   ERROR]: Command docker-compose -p wekan up -d --no-build --no-recreate failed with: Creating network "wekan_appcenter_net" w$
Pool overlaps with other one on this address space (1)

so i checked the docker interfaces…
and there is the problem… I had yesterday removed a (test) install of “zammad” and it seems that the uninstall has broke the system.

root@ucs:/# nano /var/log/univention/appcenter.log
root@ucs:/# docker network ls
NETWORK ID          NAME                   DRIVER              SCOPE
98e19b6991a4        bridge                 bridge              local
9e4ccc0a4224        host                   host                local
7d90d42c6d78        none                   null                local
7054bdaa7333        zammad_appcenter_net   bridge              local
root@ucs:/# docker network rm 7054bdaa7333
7054bdaa7333
root@ucs:/# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
98e19b6991a4        bridge              bridge              local
9e4ccc0a4224        host                host                local
7d90d42c6d78        none                null                local

also, the many docker containers of zammad was still there.

After that nextcloud was accessible again via external hostname.