From 87e018b55f3823db439700b2288333b14cda4a8a Mon Sep 17 00:00:00 2001 From: szaimen Date: Sat, 19 Mar 2022 07:42:03 +0100 Subject: [PATCH] improve the open port documentation Signed-off-by: szaimen --- readme.md | 12 ++++++------ reverse-proxy.md | 2 +- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/readme.md b/readme.md index 56cd5c45..2cb131fe 100644 --- a/readme.md +++ b/readme.md @@ -54,9 +54,9 @@ The following instructions are especially meant for Linux. For macOS see [this]( 3. After the initial startup, you should be able to open the Nextcloud AIO Interface now on port 8080 of this server.
E.g. `https://internal.ip.of.this.server:8080`
-If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatially by opening the Nextcloud AIO Interface via:
+If your firewall/router has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatially by opening the Nextcloud AIO Interface via:
`https://your-domain-that-points-to-this-server.tld:8443` -4. Please do not forget to open port `3478/TCP` and `3478/UDP` for the Talk container! +4. Please do not forget to open port `3478/TCP` and `3478/UDP` in your firewall/router for the Talk container! ## FAQ ### How does it work? @@ -65,7 +65,7 @@ Nextcloud AIO is inspired by projects like Portainer that allow to manage the do ### Are reverse proxies supported? Yes. Please refer to the following documentation on this: [reverse-proxy.md](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md) -### Which ports are mandatory to be open? +### Which ports are mandatory to be open in your firewall/router? Only those (if you acces the Mastercontainer Interface internally via port 8080): - `443/TCP` for the Apache container - `3478/TCP` and `3478/UDP` for the Talk container @@ -73,9 +73,9 @@ Only those (if you acces the Mastercontainer Interface internally via port 8080) ### Explanation of used ports: - `8080/TCP`: Mastercontainer Interface with self-signed certificate (works always, also if only access via IP-address is possible, e.g. `https://internal.ip.address:8080/`) - `80/TCP`: redirects to Nextcloud (is used for getting the certificate via ACME http-challenge for the Mastercontainer) -- `8443/TCP`: Mastercontainer Interface with valid certificate (only works if port 80 and 8443 are open and you point a domain to your server. It generates a valid certificate then automatically and access via e.g. `https://public.domain.com:8443/` is possible.) -- `443/TCP`: will be used by the Apache container later on and needs to be open -- `3478/TCP` and `3478/UDP`: will be used by the Turnserver inside the Talk container and needs to be open +- `8443/TCP`: Mastercontainer Interface with valid certificate (only works if port 80 and 8443 are open in your firewall/router and you point a domain to your server. It generates a valid certificate then automatically and access via e.g. `https://public.domain.com:8443/` is possible.) +- `443/TCP`: will be used by the Apache container later on and needs to be open in your firewall/router +- `3478/TCP` and `3478/UDP`: will be used by the Turnserver inside the Talk container and needs to be open in your firewall/router ### How to run it on macOS? On macOS, there is one specialty in comparison to Linux: instead of using `--volume /var/run/docker.sock:/var/run/docker.sock:ro`, you need to use `--volume /var/run/docker.sock.raw:/var/run/docker.sock:ro` to run it after you installed [Docker Desktop](https://www.docker.com/products/docker-desktop/). Apart from that it should work and behave the same like on Linux. diff --git a/reverse-proxy.md b/reverse-proxy.md index 0f2b51f8..6f3e9ccb 100644 --- a/reverse-proxy.md +++ b/reverse-proxy.md @@ -68,7 +68,7 @@ nextcloud/all-in-one:latest -After doing so, you should be able to access the AIO Interface via `https://internal.ip.of.this.server:8080`. Enter your domain that you've entered in the reverse proxy config and you should be done. Please do not forget to open port `3478/TCP` and `3478/UDP` for the Talk container! +After doing so, you should be able to access the AIO Interface via `https://internal.ip.of.this.server:8080`. Enter your domain that you've entered in the reverse proxy config and you should be done. Please do not forget to open port `3478/TCP` and `3478/UDP` in your firewall/router for the Talk container! ### Optional