Update reverse-proxy.md

[DaCHack]

Adding prominent hint to Traefik users adding the Traefik container to the aio network to change the server domain during the installation process. The nextcloud-aio-apache container is not in place as indicated in the documentation at this point in time

[szaimen]

Hi, if you read through the documentation mentioned here: https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#adapting-the-sample-web-server-configurations-below, you would have seen that pointing at nextcloud-aio-apache is the solution to your problem

[DaCHack]

It was actually the Root cause of my problem. Apache does not get created at the Point of the domaincheck. Thus, nextcloud-aio-apache cannot be found by Traefik.

[szaimen]

This should not be a problem as the domaincheck container uses an alias:

all-in-one/php/src/Docker/DockerActionManager.php

Lines 945 to 948 in 13e9829

	// Add a secondary alias for domaincheck container, to keep it as similar to actual apache controller as possible.
	// If a reverse-proxy is relying on container name as hostname this allows it to operate as usual and still validate the domain
	// The domaincheck container and apache container are never supposed to be active at the same time because they use the same APACHE_PORT anyway, so this doesn't add any new constraints.
	$alias = ($container->GetIdentifier() === 'nextcloud-aio-domaincheck') ? 'nextcloud-aio-apache' : '';

[DaCHack]

Interesting! Seems this did not work for me. Traefik always reported there is no such host.