From 7373bb59604aa96c6e6b3d39e598c55ff75e08f2 Mon Sep 17 00:00:00 2001 From: Simon L Date: Wed, 19 Apr 2023 18:44:43 +0200 Subject: [PATCH] talk about open/forwarded ports Signed-off-by: Simon L --- multiple-instances.md | 2 +- readme.md | 8 ++++---- reverse-proxy.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/multiple-instances.md b/multiple-instances.md index b9f5f804..851b6eb0 100644 --- a/multiple-instances.md +++ b/multiple-instances.md @@ -14,6 +14,6 @@ Below is described more in detail how the the second way works. 1. Next create your Caddyfile with multiple entries and domains for the different instances like described in step 1 of the [reverse proxy documentation](./reverse-proxy.md). Obviously each domain needs to point correctly to the chosen `APACHE_PORT` that you've configured before. Then start Caddy which should automatically get the needed certificates for you if your domains are configured correctly and ports 80 and 443 are forwarded to your server. 1. Now open each of the AIO interfaces by opening `https://ip.address.of.this.server:8080` or e.g. `https://ip.address.of.this.server:8081` or as chosen during step 3 of this documentation. 1. Finally type in the domain that you've configured for each of the instances during step 5 of this documentation and you are done. -1. Please also do not forget to open each chosen `TALK_PORT` UPD and TCP in your firewall/router as otherwise Talk will not work correctly! +1. Please also do not forget to open/forward each chosen `TALK_PORT` UPD and TCP in your firewall/router as otherwise Talk will not work correctly! Now everything should be set up correctly and you should have created multiple working instances of AIO on the same server! diff --git a/readme.md b/readme.md index aa932990..abd2a668 100644 --- a/readme.md +++ b/readme.md @@ -114,7 +114,7 @@ The following instructions are meant for installations without a web server or r 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://ip.address.of.this.server:8080`

-If your firewall/router has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
+If your firewall/router has port 80 and 8443 open/forwarded and you point a domain to your server, you can get a valid certificate automatically 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` in your firewall/router for the Talk container! @@ -138,9 +138,9 @@ Only those (if you access 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://ip.address.of.this.server: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 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 +- `8443/TCP`: Mastercontainer Interface with valid certificate (only works if port 80 and 8443 are open/forwarded 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/forwarded in your firewall/router +- `3478/TCP` and `3478/UDP`: will be used by the Turnserver inside the Talk container and needs to be open/forwarded in your firewall/router ### How to run AIO on macOS? On macOS, there is only one thing different 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/) (and don't forget to [enable ipv6](https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md) if you should need that). Apart from that it should work and behave the same like on Linux. diff --git a/reverse-proxy.md b/reverse-proxy.md index 8dd07dce..999ea3f5 100644 --- a/reverse-proxy.md +++ b/reverse-proxy.md @@ -523,7 +523,7 @@ Simply translate the docker run command into a docker-compose file. You can have Use this envorinmental variable during the initial startup of the mastercontainer to make the apache container only listen on localhost: `--env APACHE_IP_BINDING=127.0.0.1`. **Attention:** This is only recommended to be set if you use `localhost` in your reverse proxy config to connect to your AIO instance. If you use an ip-address instead of localhost, you should set it to `0.0.0.0`. ## 4. Open the AIO interface. -After starting AIO, you should be able to access the AIO Interface via `https://ip.address.of.the.host: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! +After starting AIO, you should be able to access the AIO Interface via `https://ip.address.of.the.host:8080`. Enter your domain that you've entered in the reverse proxy config and you should be done. Please do not forget to open/forward port `3478/TCP` and `3478/UDP` in your firewall/router for the Talk container! ## 5. Optional: get a valid certificate for the AIO interface