From b3b8c85acefd1c3fa3164d88592fae87d145941c Mon Sep 17 00:00:00 2001 From: szaimen Date: Fri, 6 May 2022 21:05:53 +0200 Subject: [PATCH] add another debug point Signed-off-by: szaimen --- reverse-proxy.md | 1 + 1 file changed, 1 insertion(+) diff --git a/reverse-proxy.md b/reverse-proxy.md index 999c6fd7..235b9bf2 100644 --- a/reverse-proxy.md +++ b/reverse-proxy.md @@ -196,5 +196,6 @@ Afterwards should the AIO interface be accessible via `https://: If something does not work, follow the steps below: 1. Make sure to exactly follow the whole reverse proxy documentation step-for-step from top to bottom! 1. Find out if you can ping the private ip-address of the host that is running the docker daemon from inside the reverse proxy container (if runing the reverse proxy in a container). **Advice:** the `nextcloud-aio-mastercontainer` is **NOT** running the docker daemon. The host itself is running the docker daemon. +1. Make sure that the mastercontainer is able to spawn other containers. You can do so by checking that the mastercontainer indeed has access to the Docker socket which might not be positioned in one of the suggested directories like `/var/run/docker.sock` but in a different directory, based on your OS and the way how you installed Docker. The mastercontainer logs should help figuring this out. You can have a look at them by running `sudo docker logs nextcloud-aio-mastercontainer` after the container is started the first time. 1. Try to configure everything from scratch if it still does not work! 1. If nothing works and as last resort, you can modify `` to `localhost`. For that to work, the reverse proxy needs to be member of the host network. That means, that when running the reverse proxy inside a container, you need to use the `--network host` option when starting the container.