From 89633d0bf19aaa8edae92db8508953f75d32cf4e Mon Sep 17 00:00:00 2001 From: YvesCesar Date: Fri, 13 Nov 2026 15:22:47 -0400 Subject: [PATCH] docs: describe which services PROXY_IP_BIND exposes Signed-off-by: YvesCesar --- docs/advanced-setup.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/advanced-setup.md b/docs/advanced-setup.md index 2a7aac2..406811b 100644 --- a/docs/advanced-setup.md +++ b/docs/advanced-setup.md @@ -177,12 +177,14 @@ If the directory name creates a long local hostname, use a shorter Compose proje COMPOSE_PROJECT_NAME=dev docker compose up ``` -The shared proxy owns host ports `80` and `443` and binds to `127.0.0.1` by default. To expose only the proxy on other network interfaces, set: +The shared proxy owns host ports `80` and `443` and binds to `127.0.0.1` by default. To expose the proxy on other network interfaces, set: ```bash PROXY_IP_BIND=0.0.0.0 docker compose up ``` +The proxy routes requests by the `Host` header, so this exposes every routed service of every active environment, not only Nextcloud: the environment dashboard at `localhost`, Mailpit with all captured email, and the Euro-Office, Playwright and Signal gateway services when their profiles are enabled. Mailpit, Playwright and the Signal gateway have no authentication, Euro-Office uses a default `JWT_SECRET`, and the Nextcloud admin password defaults to `admin` unless `NEXTCLOUD_ADMIN_PASSWORD` is set. Forwarding the proxy port on a remote platform has the same effect. + MySQL and PostgreSQL use independent bind settings and also default to `127.0.0.1`: ```bash