DocumentServerUrl for Onlyoffice should be a subdomain

[Buuuntyyy]

Steps to reproduce

1. Install nextcloud with Onlyoffice enabled
2. Access to your nextcloud instance
3. Configure onlyoffice with the default given domain name (https://your.nc_domain.com/onlyoffice).
4. Check the configuration

Expected behavior

Configuration should be approved.

Actual behavior

Configuration is not approved.

Other information

Host OS

⚠️ I'm under nextcloud-aio-helm-charts version ! ⚠️
Debian 12
I use a reverse proxy (SSL stop at the reverse).
By looking forwards in onlyoffice and nextcloud forum I found that Onlyoffice need to have a dedicated subdomain. Currently, the configuration set the Onlyoffice URL to : https://your.nc_domain.com/onlyoffice that doesn't work.

Output of sudo docker info

Docker run command or docker-compose file that you used

Other valuable info

Line 698-702 of all-in-one/containers.entrypoint.sh
if echo "$ONLYOFFICE_HOST" | grep -q "nextcloud-.*-onlyoffice"; then
ONLYOFFICE_HOST="$NC_DOMAIN/onlyoffice"
export ONLYOFFICE_HOST
fi
php /var/www/html/occ config:app:set onlyoffice DocumentServerUrl --value="https://$ONLYOFFICE_HOST"

In my mind, for exemple, it should be :
if echo "$ONLYOFFICE_HOST" | grep -q "nextcloud-.-onlyoffice"; then
ONLYOFFICE_HOST="office.${NC_DOMAIN#.}"
export ONLYOFFICE_HOST
fi
php /var/www/html/occ config:app:set onlyoffice DocumentServerUrl --value="https://$ONLYOFFICE_HOST"

The thing is that this option only works for 3words FQDN (test.google.com, not for a.test.google.com). But solution exists (concatenates from the end of the nc_domain).

[szaimen]

Hi, actually it is possible to install OnlyOffice in a subpath and a subdomain is not actually required. This is what we are doing here and it works on my test instance. Also see

all-in-one/Containers/apache/Caddyfile

Lines 39 to 46 in eda27a1

	# Onlyoffice
	route /onlyoffice/* {
	uri strip_prefix /onlyoffice
	reverse_proxy {$ONLYOFFICE_HOST}:80 {
	header_up X-Forwarded-Host {http.request.hostport}/onlyoffice
	header_up X-Forwarded-Proto https
	}
	}

[Buuuntyyy]

Hi !
Thanks. However, I faced this issue about 1 month ago. I found on some forum that nextcloud required its own Subdomain (Nextcloud wasn't able to do the healthcheck and download the test file).
Probably it has been changed in a recent release (I'm looking for the forum I found, but it's deep).
But as I said, the issue may be coming from my infra and my reverse proxy especially.